Question

3

Where can I find messages related to Apache start up?

rated 0 times [ 3] [ 0] / answers: 1 / hits: 37098 / 3 Years ago, sun, june 6, 2021, 2:54:11

Apache didn't start up automatically like it usually does. I'd like to try to find out why. It looks like it never started up today, so nothing in /var/log/apache2/error.log since it never ran. As I understand it, the apache script is /etc/init.d/apache2 so I'd like to find some messages somewhere regarding this script. However, I can't find anything in /var/log/messages or the syslog.

Is there anywhere in the system where it says "Yep, I'm starting up /etc/init.d/apache2 now; it worked" or especially "It didn't work and here's why!" ?

I am using Ubuntu Release 10.04 (lucid), Kernel Linux 2.6.32-38, and GNOME 2.30.2 .

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

panshow

Add To Favorites

Follow

Total Points: 454

Total Questions: 98

Total Answers: 122

Location: Philippines

Member since Sat, Jul 11, 2020

4 Years ago

panshow questions

1 How do you efficiently/correctly extract data from a tarball into a new Ubuntu distribution?

Thu, Dec 16, 21, 17:23, 2 Years ago

1 Why does Ubuntu not clean out old kernel module files (in /lib/modules) when old kernels are removed?

Sun, Jun 20, 21, 16:00, 3 Years ago

1 Why is my sound extremely distorted in Ubuntu Studio 21.10?

Thu, Mar 17, 22, 12:23, 2 Years ago

1 qt5-default not in Ubuntu 21.04

Mon, Jan 31, 22, 14:07, 2 Years ago

1 How to skip the "Is ready" notification and directly open apps in Ubuntu 20.4?

Sat, Mar 25, 23, 02:02, 1 Year ago

View All

answered 3 Years ago leadprogres · Accepted Answer

You could go to a terminal and type in "sudo /etc/init.d/apache2 restart" in a terminal, and see what kind of error message you get. One common reason, I believe, is because of some module that was either added, changed, or had a change made to a corresponding config file (such as php.ini). If all else fails, go to the directory /etc/apache2/mods-enabled, and move module links out into a temporary directory, and if apache starts, you can put them back one by one.

Be aware, though, that the error message may be misleading. It may get an error loading a module not because the module is bad, but because it's configuration file is bad.