This is an old revision of the document!
If you want to track down problems with the x2goserver
or the cups-x2go
code, it is possible to enable output of debug information into the systems syslog facility (normally /var/log/syslog).
The default log levels for x2goserver
and cups-x2go
are set to notice
. Available log levels are: emerg, crit, alert, err, warning, notice, info, debug.
The x2goserver
log level can be set by editing:
root@x2goserver:~$ editor /etc/x2go/x2goserver.conf
For debugging cups-x2go there are two files to look at:
/var/log/cups/error_log
- in case cups-x2go
code has a bug (e.g. a syntax error) or fails otherhow/var/log/syslog
- in case anything goes wrong while cups-x2go
is processing a print job
For setting the log level of your CUPS server, please investigate the cupsd.conf
man page:
$ man cupsd.conf
The cups-x2go
log level can be set by editing:
root@x2goserver:~$ editor /etc/cups/cups-x2go
All X2go server scripts are ready for syslogging, though not all of them actually do log to syslog. If you want to add your own syslog messages for debugging purposes, please take a look at the code of files that already do report to syslog. Here is a little howto that explains how to add extra log output to X2go server scripts:
Whereever you want to write a line to syslog from an X2go Perl script, place this command
syslog('debug', '<My message to syslog...>');
Whereever you want to write a line to syslog from an X2go Shell/Bash script, place this command
$X2GO_LIB_PATH/x2gosyslog "$0" "debug" "<My message to syslog...>"