Happened on two of my machines tonight, either a new debian update or something has caused this. Machine 1 (Linux Debian etch): Running a suPHP setup. When a user deletes a site and doesnt clear his thrashbin the apache server refuses to reload with "bad group" error. Apache fails to start. Another machine complained about (Linux Debian Lenny): Unable to open logs (2)No such file or directory: apache2: could not open error log file /var/www/web91/log/error.log. when someone manually moved a log/ folder to the wrong place. Anyone know why apache has become overzealous of all settings and fail to start for such "minor" things?
Please take a look in the ispconfig.log if any errors have been reported there. It seems as ispconfig was not able to restart apache after the configuration was changed.
No error in ispconfig.log But apache refused to restart on the apache2ctl script or the /etc/init.d upstart script. It was pretty much overzealous of group and log path being there. Is there a way to make apache not care too much about such minor issues and still start?
No, as this is a major issue for apache. ISPconfg checks for these problems before apache is restarted normally if you did not disable these checks in config.inc.php.
Nope, did not change any of these checks. What is so odd is that two different issues happened on two different machines starting at the same time in the morning. All related to conf issue caused by ispconfig . Odd
Maybe the configuration process was interrupted or so. I have not seen it on another system befoe so I can only guess what might have been the cause.
