Having some problem with start apache 2.2.8 from webmin’s “Apache Webserver” Interface.
If I click on the "start apache" link at the top right corner, I will always get an error message stating
"Failed to start apache : Apache does not appear to be running :
Starting web server: apache2"
This does not happen if I log in via ssh and restart my apache using /etc/init.d/apache2 restart or
/etc/init.d/apache2 start or
/etc/init.d/apache2 stop
Yes, there is no such configuration directive as "k_dir". It should be link_dir
But I’m not sure that would prevent things from working. Are the configuration paths actually correct? Is the Apache pid file in the normal location for Debian?
Something to note is that it was the webmin "Start Apache" and "Restart Apache" links were working perfectly fine before I upgraded Apache to 2.2.8. It was working well when I was running Apache 2.2.6.
Could that be an indicator of some issue with webmin running Apache 2.2.8?
Anyone? Any idea on what could be preventing webmin from reading Apache 2.2.8’s status while on the other hand, when I manually run /etc/init.d/apache2 restart or start or force-reload or stop commands, everything works perfectly at command line?
It’s gotta be the pid file. That’s how Webmin knows whether Apache is running or not. Make sure it points to the right place. Presumably it moved in the more recent version of Apache.
Holy crap, you’re running the Ubuntu Abomination! Run for the hills! (Putting invalid syntax into a configuration file for the convenience of a couple of lazy developers is a great wrongness in the force, and shame and scorn be upon them for their evil ways.)
Upgrade to Webmin 1.411, which knows how to deal with this abomination. (Because they were too damned lazy to parse the Apache configuration file, every other administrative tool that knows how to parse the Apache file has to be updated to deal with the garbage they’re putting in the file.)
So, the Debian folks have adopted the same horrible practice. Makes a fellow unhappy to know it…as this was one of the reasons I like Debian better than Ubuntu for servers–it’s a really bad direction to go in, and if they do it for all of their services, it will become a wholly unusable mess.
Maybe it’s not debian’s fault… I could have accidentally chown on the wrong directory, preventing webmin from running the /etc/init.d/apache2 start/restart/stop/force-reload commands.
Is there anyway I can check that the file or folder permissions are correct? If so, which folder should I look into?
No, it’s definitely not Webmin’s fault–this is evil committed by the Debian and Ubuntu folks.
But you’ll still need to upgrade to 1.411 if you’re going to use that configuration file. No version before 1.411 knows about those variables (which are post-processed by the rc scripts that start Apache).
And it’s not your fault, either, in case I wasn’t clear. These variables in an Apache configuration file are not normal or valid httpd.conf syntax, but they are a default part of the Ubuntu Apache package (and apparently now the Debian package).
No. I said 1.411. 1.410 does not support these variables. 1.411 is a development version.
Older versions of Virtualmin will be fine…but you really should be running the latest version at all times. We don’t build new versions for our healt. We build them because they’re better–fewer bugs, more features, better usability, etc.
