Apache 'start' failed. How to solve the apache starting and no listening sockets available, shutting down, issue?

-
If your apache fail to start and shows the following error
apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2)
   Active: active (exited) since Mon 2016-04-04 09:53:19 BTT; 6min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 17233 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
  Process: 12489 ExecReload=/etc/init.d/apache2 reload (code=exited, status=1/FAILURE)
  Process: 17275 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)

Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: [Mon Apr 04 09:53:19.068063 2016] [alias:warn] [pid 17288] AH00671: The Alias directive in /etc/phpmyadmin/a...er Alias.
Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:8080
Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:8080
Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: no listening sockets available, shutting down
Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: AH00015: Unable to open logs
Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: Action 'start' failed.
Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: The Apache error log may have more information.
Apr 04 09:53:19 vle.xxx.edu.bt apache2[17275]: *
Apr 04 09:53:19 vle.xxx.edu.bt systemd[1]: Started LSB: Apache2 web server.
Apr 04 09:59:55 vle.xxx.edu.bt systemd[1]: Started LSB: Apache2 web server.
Hint: Some lines were ellipsized, use -l to show in full.


Then  try the following, first check which processes is using the port used by you apache

Kill the process with the kill:

  Then restart the apache again:

Your apache should start and your problem is solved.

 



Comments

Post a Comment

Popular posts from this blog

ACTION_FAILED:OU_INVALID: Solution for GoogleApps bulk user upload issue, username@domainname.com:ACTION_FAILED:OU_INVALID. This error is because you have not specified the Org Unit Path properly.

-
To upload bulk users to GoogleApps, you will require a following required fileds, other fields are optional:-               First Name               Last Name               Email Address               Password               Org Unit Path What is 'Org Unit Path'? This field was not their earlier. This is the path to place users in an organizational unit. For example if your domain has different organization unit like , staff, students, guest etc.. then the Org Unit Path would be just :  /
Read more

Solution to Moodle Error: Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write.

-
Image
Did you ever come across the following error when you try to access Moodle, "Coding error detected, it must be fixed by a programmer: Failed to unserialise data from file. Either failed to read, or failed to write." This usually happens when cache files are corrupted, one probable cause can be improper shutdown of Moodle system. Here is the solution to fix the issue. 1. Go to Moodle root directory     #cd /var/www/html/moodle   2. Run the command      #php admin/cli/purge_caches.php 3. Go to moodledata/cache directory   #cd /var/moodledata/cache    4. Remove the cache store directory, DO NOT remove of change the core_component.php file    # rm -rf cachestore_file/ 5. Refresh the Moodle Page. Its should work.
Read more

Email Notification in Koha! How to configure Email Notification in Koha 20.11 with postfix?

-
Image
Here is the steps to configuring Koha 20.11 & postfix for sending notices/slips through email. 1. First install postfix             #sudo apt-get update             #sudo apt-get install postfix          Click on OK.    Tab and select No configuration. 2.  Copy the configuration file     #  cp /usr/share/postfix/main.cf.debian /etc/postfix/main.cf 3. Install the other required packages.     #apt-get install libsasl2-2     #apt-get install libsasl2-modules     #apt-get install ca-certificates 4.  Open the following file and add few lines.     # vim /etc/postfix/main.cf and add the following lines at the bottom of the page and save the file.     relayhost = [smtp.gmail.com]:587     smtp_sasl_auth_enable = yes     smtp_sasl_password_...
Read more