Opened 5 years ago

Closed 5 years ago

#633 closed Bug (fixed)

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

Reported by: matt Owned by:
Priority: major Milestone: RobotRock
Component: Core Keywords:
Cc: Sensitive:

Description

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.

Change History (1)

comment:1 Changed 5 years ago by matt (mattab)

  • Resolution set to fixed
  • Status changed from new to closed

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

Note: See TracTickets for help on using tickets.