Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 191979 - Apache 2.2.6 need a symlink to /var/log/apache2
Summary: Apache 2.2.6 need a symlink to /var/log/apache2
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Apache Team - Bugzilla Reports
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-10 13:29 UTC by Aurélien Requiem
Modified: 2007-09-19 16:29 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aurélien Requiem 2007-09-10 13:29:44 UTC
Hello

In the new apache 2.2.6, a symlink is probably missing.
/usr/lib/apache2/logs --> /var/log/apache2

after installation, if logs files are specified in relative path (ErrorLog logs/foo.error.log) this will cause an error because apache try to write log file in /usr/lib/apache2/logs/foo.error.log

This problem didn't occured in apache 2.0.x

Please note, std log files (access_log and error_log) are correctly stored in /var/log/apache2

Reproducible: Always

Steps to Reproduce:
1. installa apache 2.2.6
2. make a vhost and add a relative logfile path (ErrorLog logs/foo.error.log)
3. and [re]start apache2
4. check error_log.

Actual Results:  
apache refuse to start as long as the symlik doesn't exists.


Expected Results:  
apache should start

It could be interesting to spécify a default log directory instead of a symlink. You can check "configure" options...
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-09-10 13:33:55 UTC
Not really, please make sure you've updated your configuration correctly and that it doesn't contain references to non-existant paths.
Comment 2 Lasse Bigum 2007-09-18 22:33:07 UTC
I had the same error, and I ran etc-update as required, and re-emerged php to make it work.

The missing symlink caused me some problems as well. I'm not saying this is not an error on our part, just that it is not immediately obvious to me how it should be.

Also, I'm battling at the moment with the very restrictive default Directory Options, which gives me a 403 on all VHOST's. All in all much fun.
Comment 3 Aurélien Requiem 2007-09-18 22:45:26 UTC
I've also tried to understand what could happened to this... And i have no good explanations...

I maintain at least 20 gentoo serveurs. Some has the bugs, and others not.
Maybe the bug come from another version of the ebuild and an incomplete update... Don't really know.

Probably in the ebuild, if the symlink is missins, can portage add it ?

thank you

Aurélien
Comment 4 Benedikt Böhm (RETIRED) gentoo-dev 2007-09-19 15:34:36 UTC
no, the symlink won't be added, don't use relative paths in the apache config, it' a Bad Thing (tm)
Comment 5 Lasse Bigum 2007-09-19 16:29:38 UTC
(In reply to comment #4)
> no, the symlink won't be added, don't use relative paths in the apache config,
> it' a Bad Thing (tm)

This I can "understand", or at least take as an answer, contrary to Jacub Moc's.

Was this announced via an ewarn? I did not get any messages from ELOG or anything similar.