[warn] _default_ VirtualHost overlap on port 80, the first has precedence

This warning  occurred while restarting Apache server and two or more virtuelHost (VH) are listening on the same port, to avoid it just change listening port of  VH in http.conf file, here is an example
<VirtualHost *:8080>

NB: If you are setting ServerName for each VH you may not face this Warning.

Categories: apache warning, fix apache warning, VirtualHost overlap on port 80

Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName

This how to fix

apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

In order  to solve this problem You need set the ServerName in httpd.conf file, for example in my case I used "ubuntu" as a server name

• first goto httpd.conf

#vim /etc/apache2/httpd.conf/

•  set ServerName attribute to ubuntu

ServerName ubuntu

• Restart apache2

#service apche2 restart

That's All!

Categories: apache2 error, fix apache2 error

Wlan1 error while getting interface flags no such device

Usually Networks crafters are front of this kind of errors; there are two reasons behind this error.

1-        Operating system can't recognize the plugged device due to miss of driver (I will not discuss this problem here…)

2-       Network card is correctly recognized but can't get IP address.

first thing to do in order to solve this problem is to make sure that the network card correctly  plugged and recognized on the system using  lspci or lsub command depending of the type of NC (Network Card), in my case I'm using an usb Wi-Fi adapter.

 So the network card is known for the system, else it's a type 1 problem …

Secondly we have to find which alias is used to identify the adapter, the simple way is to iterate possible combination (if you have a simpler manner to find the match alias please share it with us)

Wlan1 is my Wifi usb adapter alias ... we have then to edit /etc/network/interfaces as bellow

Restart network service and it's resolved!

NB: In your case Wlan1 may be eth0, eth1 ..etc.

Categories: Wlan1 error while getting interface flags no such device

139883256969032:error:02001002:system library:fopen:No such file or directory:bss_file.c:355:fopen('/etc/pki/CA/index.txt','r')

This error is frequently appeared when we try to sign a certificate using openssl, the procedure to resolve this error is:

Create the index.txt file.
# touch /etc/pki/CA/index.txt

Create a serial file to label the CA and all subsequent certificates.
# echo '1000' > /etc/pki/CA/serial

NB: You have to do this just the first time you set-up the SSL certificate.

Categories: openssl error, SSL error

500 OOPS: could not read chroot() list file:/etc/vsftpd/chroot_list

It's common to get this error while using vsftp (very secure FTP) and trying to connect to ftp server through a client, the reason behind is that ftp daemon can not read/find chroot_list,  to resolve this problem just create the specified file using the following command:

#touch /etc/vsftpd/chroot_list

if doesn't work for you just give me a hint

Categories: could not read chroot() list file:/etc/vsftpd/chroot_list