Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

when specifying logging messages/errors/exceptions to a file in piwik config, the archiving breaks as path is invalid #633

Closed
mattab opened this issue Mar 26, 2009 · 1 comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Mar 26, 2009

I configured the logging to be sent to files
instead of the screen. But the archiving process could’nt handle this. It
came up with with this error, another piwik user already had:

http://lists.piwik.org/pipermail/piwik-hackers/2008-August/000336.html

The underlying problem is not to chmod tmp/logs/logger_message and other
log-files to 777 or something; The logging script seems to use a wrong
relative path to the log-files at all; Cause it is called by a cronjob or by
hand from a position anywhere in the filesystem, supposable the logger script
trys to open a tmp/logs-path and file relativ to this position in the
filesystem and not relativ to the piwik base path.

The fastest and simplest workaround for me was it to just change the [path]
log variable in the global.ini to an absolute path.

@mattab
Copy link
Member Author

mattab commented Mar 26, 2009

(In 1032) – fixes #633 When specifying logging messages/errors/exceptions to a file in piwik config, the archiving breaks as path is invalid

@mattab mattab added this to the RobotRock milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Development

No branches or pull requests

1 participant