You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.
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:
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.
The text was updated successfully, but these errors were encountered:
BugFor errors / faults / flaws / inconsistencies etc.MajorIndicates the severity or impact or benefit of an issue is much higher than normal but not critical.
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.
The text was updated successfully, but these errors were encountered: