Hi Ted,
On Do 31 Okt 2013 12:48:52 CET, Ted Barnes wrote:
Hi Mike:
How are you? Another update...hope am making progress, but not
there yet. Let me know if it would help to send over copies of
x2gobroker.conf and the other configs?Is it the case I am using the wrong backend, and don't know how to
set it to backend inifile? Thanks for the help(!)
- Rebuilt server (using Squeeze) and incorporated nightly x2go builds
apt-get install -y x2goserver x2goserver-xsession apt-get install -y x2gobroker-wsgi apt-get install -y apache2 (apache fails until instill libapache2-mod-wsgi) apt-get install -y libapache2-mod-wsgi apt-get install -y x2gobroker-authservice
Checked versions x2gobroker-wsgi: 0.0.3.0-0~x2go1+squeeze~heuler~20131002~558~build1 x2goserver: 4.1.0.0-0~x2go1+squeeze~heuler~20130731~779~build1 x2gobroker-authservice: 0.0.3.0-0~x2go1+squeeze~heuler~20131002~558~build1
Set backend to inifile In x2gobroker.conf: [inifile] enable = false session-profiles = /etc/x2go/broker/x2gobroker-sessionprofiles.conf
If you want to use the inifile backend, you have to set enable = true
(not false).
- have made various tweaks to x2gobroker-sessionprofiles.conf,
x2gobroker.conf, and x2gobroker-wsgi.apache.conf - have not touched
x2gobroker-wsgi.apache.vhost without noticeable difference in outcome.
- When try to connect: Not sure this matters, but on client get: x2go-INFO-1> "Starting x2goclient..." x2go-WARNING-1> "Can't load translator: :/x2goclient_en_us" x2go-WARNING-2> "Can't load translator: :/qt_en_US"
And...
SSH - says inifile not enabled....(when try to connect first time,
does ask if I want to trust key and creates known hosts file)x2goclient
--broker-url="ssh://user@xxx.xxx.xxx.xxx/usr/bin/x2gobroker
--backend=inifile"2013-10-31 07:00:32,777 - broker - INFO - X2Go Session Broker (0.0.3.0), 2013-10-31 07:00:32,786 - broker - INFO - written by Mike Gabriel
(X2Go Project) <mike.gabriel@das-netzwerkteam.de> 2013-10-31 07:00:32,789 - broker - INFO - Setting up the broker's
environment... 2013-10-31 07:00:32,790 - broker - INFO - X2GOBROKER_DEBUG: True 2013-10-31 07:00:32,790 - broker - INFO - X2GOBROKER_CONFIG:
/etc/x2go/x2gobroker.conf 2013-10-31 07:00:32,790 - broker - INFO - X2GOBROKER_AGENT_CMD:
/usr/lib/x2go/x2gobroker-agent 2013-10-31 07:00:32,790 - broker - INFO -
X2GOBROKER_AUTHSERVICE_SOCKET:
/run/x2gobroker/x2gobroker-authservice.socket 2013-10-31 07:00:32,790 - broker - INFO -
X2GOBROKER_DEFAULT_BACKEND: zeroconf 2013-10-31 07:00:32,790 - broker - INFO - X2GOBROKER_SSL_CERTFILE: 2013-10-31 07:00:32,791 - broker - INFO - X2GOBROKER_SSL_KEYFILE: 2013-10-31 07:00:33,039 - broker - ERROR - broker backend
,,inifile'' is disabled on this systemWhen try HTTP, get "Error Login failed! Please try again"
Well then, how about enabling it in x2gobroker.conf (see above)?
I am not sure about the AssertionErrors. I will look at those. They
should not occur. Instead, you should just see the 404 Not Found
errors. However, if you enable the inifile backend, I guess those
errors will go away, too.
Greets, Mike
PS: please receive non-digest mails from x2go-user ML as long as we
lead this discussion...
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...