Hello Mathias, thanks for your reply. I have some further detail to add. Yes, it started to happen after an upgrade, but I don't think this could be the cause of this behaviour (if however you need more info about this I can provide them).
Rather, I discovered that the way I started Apache (using apache2ctl instead of init script) was wrong, and generates the problem (can you confirm this, trying to start Apache using apache2ctl and see if the error.log contains the above cited error lines?). Infact, /etc/init.d/apache2 contains a line of code that takes care to create the directory /var/run/apache2 if it doesn't exist: [ -d /var/run/apache2 ] || mkdir -p /var/run/apache2 while apache2ctl, which is used by /etc/init.d/apache2, doesn't. For this reason, I think it'd be nice to prevent the user to call apache2ctl directly. Thanks. -- apache2.2-common: mod_cgid fills error.log with [error] lines https://bugs.launchpad.net/bugs/131632 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
