14:30:35 : -----------------------------------------------------------------
0m 0.0s : Pike version: Pike v7.4 release 340
: Product version: Roxen CMS 4.0.425-release5
: Operating system: Linux 2.6.12-10-amd64-k8 (x86_64)
: Starting MySQL ... Done 4.0.18-standard [672.3ms]
:
14:30:36 : mysql: Warning: One can only use the --user switch if running as root
0m 0.7s : mysql: 060127 14:30:35 InnoDB: Started
: mysql: bin/roxen_mysql: ready for connections.
: mysql: Version: '4.0.18-standard' socket: '/usr/local/roxen/configurations/_mysql/socket' port: 0
|
Beginning of debug log
The debug log is available as roxen/logs/debug/default.1. The
debug log contains essentially the same information as the event log, but
in a text only format. It is sent either to a file or to syslog on a unix
system. This is controlled by the Logging / Debug log method variable
under the Globals tab.
The debug log is important when the server starts, since it writes
messages before the administration interface becomes available. If the
server did not restart properly the debug log will show why.
The debug log also contains the process id of the Roxen process and the
start script process. This information is important if you want to restart the server
without using the admin interface, for instance by using the kill command instead.
