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/25 15:34] bmullan [REASON for the failure & change of behavior from previous/older versions of Ubuntu.] |
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 / |
</ | </ | ||
- | ===== Customizing Debug Messages ===== | + | ==== Debugging X2Go Session Broker |
- | 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: | + | The '' |
- | ==== Logging in X2Go Perl Scripts ==== | + | < |
+ | root@broker: | ||
+ | </ | ||
- | Whereever you want to write a line to syslog from an X2Go Perl script, place this command: | + | The log files normally get written |
- | <code> | + | You can also run |
- | syslog(' | + | <file> |
- | </code> | + | root@broker: |
+ | </file> | ||
- | + | as user '' | |
- | ==== Logging in X2go Shell/Bash Scripts ==== | + | ==== Python X2Go / PyHoca Debugging ==== |
- | + | ||
- | Whereever | + | |
- | + | ||
- | < | + | |
- | $X2GO_LIB_PATH/ | + | |
- | </ | + | |
- | + | ||
- | ====== Python X2Go / PyHoca Debugging | + | |
The PyHoca clients both have a '' | The PyHoca clients both have a '' | ||
- | ====== How To fix error - " | + | ===== Customizing Debug Messages |
- | Sometime in the past year or two of Ubuntu & Debian operating system updates something changed which caused the normal x2goclient session profile that requires the UserID -and- Password | + | 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.\ |
- | ** | + | |
- | Access denied. Authentication that can continue: publickey, | + | |
- | Here' | + | Here is a little howto that explains |
- | Start a terminal session with your x2goserver and edit / | + | ==== Logging in X2Go Server' |
- | < | + | Whereever |
- | sudo nano / | + | |
- | </ | + | |
- | + | ||
- | in / | + | |
< | < | ||
- | # Change | + | syslog(' |
- | # some PAM modules and threads) | + | |
- | ChallengeResponseAuthentication yes | + | |
- | + | ||
- | # Change to no to disable tunnelled clear text passwords | + | |
- | PasswordAuthentication no | + | |
</ | </ | ||
- | ==== HOW TO FIX THIS ==== | ||
- | |||
- | CHANGE **PasswordAuthentication** to " | ||
- | then restart ssh | + | ==== Logging in X2Go Server' |
- | sudo /etc/ | + | Whereever you want to write a line to syslog from an X2Go Shell/Bash script, place this command: |
- | === REASON for the failure & change of behavior from previous/ | ||
- | |||
- | I installed several older versions of Ubuntu going back to Ubuntu 9.10 and found that the installations of the Ubuntu Server changed the content of the / | ||
- | |||
- | In older systems the entry for PasswordAuthentication either said: | ||
< | < | ||
- | # Change | + | $X2GO_LIB_PATH/ |
- | # PasswordAuthentication no | + | |
</ | </ | ||
- | where the PasswordAuthentication line was commented out ... which then defaulted it to " | ||
- | -or- | ||
- | the Password Authentication line was actually uncommented BUT set to " | + | ==== Logging in X2Go Session Broker' |
- | < | + | |
- | # Change to no to disable tunnelled clear text passwords | + | |
- | PasswordAuthentication yes | + | |
- | </ | + | |
- | So those older OS versions and x2go __would work__ using login ID's and Passwords. | + | Whereever you want to write a line to ''/ |
- | Sometime during one of the Ubuntu 11.x releases the PasswordAuthentication entry was actually changed to " | ||
< | < | ||
- | # Change to no to disable tunnelled clear text passwords | + | # at the top of the module file: |
- | PasswordAuthentication no | + | from x2gobroker.loggers import logger_broker |
+ | # [...] then further below, wherever needed: | ||
+ | logger_broker.debug('< | ||
</ | </ | ||
- | That is what caused the failure of x2go logins using passwords and would present the user with that error message: | ||
- | **Access denied. Authentication that can continue: publickey, | ||
- | ** | ||