How to fix “Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName” on Ubuntu Linux

apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.0.1 for ServerName
The easier way to fix it is by typing this command:

What it does it created the files called ‘fqdn’ fully qualified domain name and this will fix this error 🙂

root@amios:/# touch /etc/apache2/conf.d/fqdn | echo “ServerName localhost” >> /etc/apache2/conf.d/fqdn

If you want to fix more problems with your apache this is where you can find the logs.

In this way you can find apache logs files. Where they are ? Here 🙂

# grep ErrorLog /usr/local/etc/apache22/httpd.conf
# grep ErrorLog /etc/apache2/apache2.conf
# grep ErrorLog /etc/httpd/conf/httpd.conf

grep: /etc/httpd/conf/httpd.conf: No such file or directory

grep: /usr/local/etc/apache22/httpd.conf: No such file or directory

grep ErrorLog /etc/apache2/apache2.conf
# ErrorLog: The location of the error log file.

For Ubuntu 14+ to the below.

Use a text editor such as “sudo nano” at the command line or “gksudo gedit” on the desktop to create a new file,

$ sudo nano /etc/apache2/conf-available/fqdn.conf

or

$ gksu “gedit /etc/apache2/conf-available/fqdn.conf”

then add

ServerName localhost

to the file, save it, and enable your new configuration file by running the command below.

sudo a2enconf fqdn

This can all be done in a single command with the following:

$ echo “ServerName localhost” | sudo tee /etc/apache2/conf-available/fqdn.conf && sudo a2enconf fqdn

Advertisements

Transaction Check Error: file /usr/lib64/audit from install of glibc-2.16-30.fc18.x86_64 conflicts with file from package audit-2.2.1-2.fc18.x86_64

Transaction Check Error:
file /usr/lib64/audit from install of glibc-2.16-30.fc18.x86_64 conflicts with file from package audit-2.2.1-2.fc18.x86_64

This may come up during the RVM install on fresh Fedora 18 once you check your rvm requirements

The solution is simple to this problem 🙂

run the following command

yum update audit

then go back to installing rmv requirements

Have FUn!

Other things to try:

Thanks for lettings us know mathlasse

I did ‘yum remove audit’ and then ‘yum update’ worked again.

My recommendation for the best book for Linux Beginners

A Practical Guide to Linux Commands, Editors, and Shell Programming (3rd Edition)