If Ubuntu server is installed anew, users tend to have a dilemma as to the steps involved in gaining access to the root account.
Root account exists but the password is not empty though.
The user should log in with the account he/she creates during the installation process.
(more…)
Possible causes:
Check how many network cards are installed in your system and if you are configuring the correct NIC card
Check the interfaces configuration settings
$ cat /etc/network/interfaces
Do not forget to restart the networking daemon after each change
$ sudo /etc/init.d/networking restart
(more…)
After base Ubuntu installation, you have to configure the network interface file to get the network settings via DHCP/static IP address (if you haven’t configured during the initial installation). For this you need to edit /etc/network/interfaces file
$ vi /etc/network/interfaces
(more…)
A quick note on the links related where to find the ubuntu releases and how to do a checksum to ensure that the downloaded copy
If you are downloading Ubuntu from the official site, MD5/SHA1 checksum (ubuntu hashes) for latest releases may not be listed there.
If it is not there, you can visit the site http://releases.ubuntu.com/. This site lists a comprehensive list of ubuntu releases and their checksums. Checksums ensure that the download is complete without corruption and is 100% accurate. So, it is always advisable to do a checksum after each download.
(more…)
There are times when you would like to do some changes in your web server configuration file which might necessitate the server to be restarted in order for the changes to take effect.
Issuing a apache restart command will forcefully close all the connections made to the web server which will end any user related activity on the server.
If you would want to avoid such scenarios then issue the following command
$ sudo /etc/init.d/apache2 graceful (in ubuntu)
Linux: History command
Each bash sessions stores the history of commands executed in .bash_history file which in turn in stored under each user’s home directory
usr100@dev01:/tmp/user$ ls
07-14.txt a.txt b.txt d.txt
usr100@dev01:/tmp/user$ cat ~/.bash_history
clear
su root
rm -i d.txt
ls -ltr
touch c.txt
Troubleshooting the above warning message in Nagios:
i) If you can specify the IP address of the host with its port number try specifying it that way instead of the host name
ii) Check the the time that is set for the http check parameter and based on it try setting the -w (warning message) parameter (sample setting: command_line /usr/lib/nagios/plugins/check_http -H mywebsite.com -t 60 -w 55)
Copyright ©2008 - 2012. Kurinchilion Inc.
