This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wiki:development:debugging [2012/04/29 15:14] bmullan [Log-in error - Access denied. Authentication that can continue: publickey,keyboard-interactive] |
wiki:development:debugging [2014/11/12 13:59] sunweaver [Log File Watching] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== Debugging |
- | If you want to track down problems with the '' | + | ===== Log File Watching ===== |
- | The default log levels for '' | + | If you want to track down problems with the server-side components of X2Go, it is possible |
- | ===== Log File Watching ===== | + | The default log levels for '' |
- | While testing your X2Go server, you can open another terminal on the server and watch the '' | + | While testing |
< | < | ||
Line 13: | Line 13: | ||
</ | </ | ||
- | ===== Debugging x2goserver | + | Other logging locations apart from the system' |
+ | |||
+ | * X2Go Server: / | ||
+ | * X2Go Client: stderr (use --debug) | ||
+ | * PyHoca-GUI: stderr (use --libdebug --debug) | ||
+ | * Xsession itself: $HOME/ | ||
+ | * NX (server-side): | ||
+ | * NX (client-side): | ||
+ | |||
+ | ===== Enable Debug Output | ||
+ | |||
+ | ==== Debugging X2Go Server | ||
The '' | The '' | ||
Line 21: | Line 32: | ||
</ | </ | ||
- | ===== Debugging cups-x2go | + | ==== Debugging cups-x2go ==== |
For debugging cups-x2go there are two files to look at: | For debugging cups-x2go there are two files to look at: | ||
Line 37: | Line 48: | ||
< | < | ||
- | root@x2goserver:~$ editor / | + | root@printserver:~$ editor / |
</ | </ | ||
+ | |||
+ | ==== Debugging X2Go Session Broker ==== | ||
+ | |||
+ | The '' | ||
+ | |||
+ | < | ||
+ | root@broker: | ||
+ | </ | ||
+ | |||
+ | The log files normally get written to ''/ | ||
+ | |||
+ | You can also run | ||
+ | < | ||
+ | root@broker: | ||
+ | </ | ||
+ | |||
+ | as user '' | ||
+ | ==== Python X2Go / PyHoca Debugging ==== | ||
+ | |||
+ | The PyHoca clients both have a '' | ||
===== Customizing Debug Messages ===== | ===== Customizing Debug Messages ===== | ||
- | 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: | + | 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: | ||
- | ==== Logging in X2Go Perl Scripts ==== | + | ==== Logging in X2Go Server' |
- | Whereever you want to write a line to syslog from an X2Go Perl script, place this command: | + | Whereever you want to write a line to syslog from an X2Go Server' |
< | < | ||
Line 53: | Line 86: | ||
- | ==== Logging in X2go Shell/Bash Scripts ==== | + | ==== Logging in X2Go Server' |
Whereever you want to write a line to syslog from an X2Go Shell/Bash script, place this command: | Whereever you want to write a line to syslog from an X2Go Shell/Bash script, place this command: | ||
Line 61: | Line 94: | ||
</ | </ | ||
- | ====== Python X2Go / PyHoca Debugging ====== | ||
- | The PyHoca clients both have a '' | + | ==== Logging in X2Go Session Broker's Python Module ==== |
+ | Whereever you want to write a line to ''/ | ||
+ | |||
+ | < | ||
+ | # at the top of the module file: | ||
+ | from x2gobroker.loggers import logger_broker | ||
+ | # [...] then further below, wherever needed: | ||
+ | logger_broker.debug('< | ||
+ | </ | ||