...
Oct 11 18:20:39 Updated: webmin-1.660-1.noarch
Oct 11 18:21:03 Updated: usermin-1.570-1.noarch
I have not been able to /stop or restart Apache on one of my VPS.
When I reboot the server, Apache is running and all my sites are online. When I try to restart the daemon through a terminal though, this is what I get (consistently):
$ sudo service httpd graceful
httpd not running, trying to start
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
After this, Webmin’s System Information page indicates that the Apache Webserver service has stopped but it is not really because my sites are still responding.
Well, that’s not likely related to the Webmin or Usermin version, as the issue you’re seeing is within Apache… however, were any Apache modules enabled recently? That’s one possible cause.
I am glad that this issue is unrelated to the Webmin upgrade. I typically restart Apache at least once a day but noticed this error for the first time only after this last (Webmin) upgrade, so I surmised that it was related.
“Apache modules enabled recently?”
No , no Apache modules were enabled or disabled recently - at least I cannot recall doing anything out of the ordinary these past few days (I have more than one server to manage).
There doesn’t seem to be anything out of the ordinary there.
In case you’re wondering about the contents of bad_pattern_in_ua.conf file, it is just a file with a few lines of BrowserMatch and BrowserMatchNoCase patterns and setting some environment variables when a match is found.
I was curious if you were running into any resource issues… maybe an Apache process was being killed off due to RAM constraints, for example.
We see quite a few issues relating to OpenVZ and resource problems… however, it doesn’t appear that you’re seeing that. If you were hitting resource issues, they would show up in the “failcnt” field.