Critical errors should be marked by time and level. Right now only the error message is printed with no other necessary informations. [Thu Sep 03 10:15:08 2009] [notice] Graceful restart requested, doing restart [Thu Sep 03 10:15:17 2009] [warn] VirtualHost ... :443 overlaps with VirtualHost ..:443, the first has precedence, perhaps you need a NameVirtualHost directive (2)No such file or directory: apache2: could not open error log file /home/hosting/grenade.cz/web/unionpoint/logs/error.log. Unable to open logs I propose this: [Thu Sep 03 10:15:08 2009] [notice] Graceful restart requested, doing restart [Thu Sep 03 10:15:17 2009] [warn] VirtualHost ... :443 overlaps with VirtualHost ..:443, the first has precedence, perhaps you need a NameVirtualHost directive [Thu Sep 03 10:15:17 2009] [error] (2)No such file or directory: apache2: could not open error log file [Thu Sep 03 10:15:17 2009] [error] /home/hosting/grenade.cz/web/unionpoint/logs/error.log.
It looks like you could change this around line 593 of server/log.c (in trunk), by getting rid of the two if-statements and just adding the time and level unconditionally. That code was added in r84134 and it's not clear to me whether there was a need to not add the timestamp and log level for startup messages, or existing behavior was just being preserved in that change. Maybe someone else can comment. Or you could just try it and see if any problems show up.
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.