Upon starting/restarting Apache, I get the folowing message-
- Failed to start service:
-
Starting web server: apache2.
...with no Apache error message.
Previously I received an error that Apache could not determine my hostname from my IP address, which I worked out using ServerName.
The odd thing is that Apache actually DOES start, but the status in "System Information" shows that it is not started.
Also, Apache will not restart when a new virtual server is created. I have to do it manually. That is the main thing that bothers me.
When starting/restarting from cli using apachectl or /etc/init.d/apache2, everything goes fine, with no error message.
Any ideas?
Howdy,
What distro are you using? And how did you install Virtualmin, did you do that with the install.sh script?
Also, are you seeing any errors or warnings in the Apache logfiles? That would be either /var/log/httpd/error_log, or /var/log/apache2/error_log, depending on your distro.
Thanks,
-Eric
I'm running Debian Squeeze right now, which was an upgrade (through apt) from Lenny 5.04. I'm using the Lenny Virtualmin repositories.
And, I'm pretty sure I installed through apt/dpkg, but I know I've used install.sh before, so maybe on this installation.
Either way, everything worked fine after I first installed long ago, but sometime recently I've noticed these issues. Possibly after the upgrade to Squeeze? I'm not sure when it started.
This is my /var/log/apache2/error.log output after starting the server through Virtualmin:
[Mon May 24 11:42:23 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec) [Mon May 24 11:42:23 2010] [notice] Digest: generating secret for digest authentication ... [Mon May 24 11:42:23 2010] [notice] Digest: done [Mon May 24 11:42:23 2010] [warn] mod_wsgi: Compiled for Python/2.5.2. [Mon May 24 11:42:23 2010] [warn] mod_wsgi: Runtime using Python/2.5.5. [Mon May 24 11:42:23 2010] [warn] mod_wsgi: Python module path '/usr/lib/python2.5/:/usr/lib/python2.5/plat-linux2:/usr/lib/python2.5/lib-tk:/usr/lib/python2.5/lib-dynload'. [Mon May 24 11:42:23 2010] [notice] Apache/2.2.15 (Debian) DAV/2 SVN/1.5.1 mod_fcgid/2.3.5 PHP/5.3.2-1 with Suhosin-Patch mod_ruby/1.2.6 Ruby/1.8.7(2010-01-10) mod_ssl/2.2.15 OpenSSL/0.9.8n mod_wsgi/2.5 Python/2.5.5 configured -- resuming normal operations
Perhaps something with having just set up mod_wsgi for django/python? I'll turn of mod_wsgi and post back up here in a couple minutes to let you know if I have the same issue..
Ok, mod_wsgi is not the problem. This is the error.log output with mod_wsgi no longer enabled:
[Mon May 24 11:47:20 2010] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec) [Mon May 24 11:47:20 2010] [notice] Digest: generating secret for digest authentication ... [Mon May 24 11:47:20 2010] [notice] Digest: done [Mon May 24 11:47:21 2010] [notice] Apache/2.2.15 (Debian) DAV/2 SVN/1.5.1 mod_fcgid/2.3.5 PHP/5.3.2-1 with Suhosin-Patch mod_ruby/1.2.6 Ruby/1.8.7(2010-01-10) mod_ssl/2.2.15 OpenSSL/0.9.8n configured -- resuming normal operations
Same issue starting the server.
Yeah, Virtualmin hasn't yet been tested with Debian Squeeze yet since it hasn't been released as a stable distro, so there could be incompatibilities you're running into.
They'll be fixed once it's released, but it's not possible to keep up with a not-yet-released distro :-)
However, you may want to go into Webmin -> Servers -> Apache Webserver -> Module Config, and double-check that all the options listed in there are correct for your distro, as they'd be setup to work with Lenny.
You'll especially want to verify the "Configurable Options" and "System Configuration" screens.
One thought is that "Path to Apache PID file" is set to "Determine automatically" by default -- you might consider setting that explicitly to where your Apache PID file is located.
-Eric
Ah, kind of what I figured. I'll just hold on until Squeeze is stable and everything is compatible. No biggie.
I really appreciate the help.
PS. Sorry about the garbled, unformatted log messages. I just noticed them.
Hi,
I had the same issue, debian etch upgrade to lenny. Added the /var/run/apache2.pid to the system configuration setting for the module Path to Apache PID file and all good. The error goes away.
thanks for your coments