Hello,
I am trying to use PyHoca-GUI to connect from my Windows 7 machine to my Linux machine. Whenever I try to do so, I get the following message:
"The remote user's home directory does not exist"
I am able to connect using the standard X2Go client and ssh without any issues. Any ideas what could be causing this?
Here are the versions I'm using:
PyHoca-GUI: 0.5.0.4 X2go: 4.0.5.0
Server: 4.0.1.15-0x2go1+git20140615.847+wheezy.main.1
Best Regards,
Matt
Hi Matt.
On Di 20 Okt 2015 17:18:36 CEST, Matt Fornero wrote:
Hello,
I am trying to use PyHoca-GUI to connect from my Windows 7 machine to my Linux machine. Whenever I try to do so, I get the following message:
"The remote user's home directory does not exist"
I am able to connect using the standard X2Go client and ssh without any issues. Any ideas what could be causing this?
Here are the versions I'm using:
PyHoca-GUI: 0.5.0.4 X2go: 4.0.5.0
Server: 4.0.1.15-0x2go1+git20140615.847+wheezy.main.1
The code that checks your home [1] is this:
"""
def home_exists(self):
"""
Test if the remote home directory exists.
@return: C{True} if the home directory exists, C{False} otherwise
@rtype: C{bool}
"""
(_stdin, _stdout, _stderr) = self._x2go_exec_command('stat
-tL "%s"' % self._x2go_remote_home, loglevel=log.loglevel_DEBUG) if _stdout.read(): return True return False
"""
What does 'stat -tL $HOME' result in when executed on the X2Go Server
under the remote user account that cannot log in via PyHoca-GUI?
Mike
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/mailxchange/kronolith/fb.php?u=m.gabriel%40...
Hi Mike,
Thanks for the response. I did take a look at the code, but couldn't find anything obvious
The code that checks your home [1] is this:
""" def home_exists(self): """
Test if the remote home directory exists.@return: C{True} if the home directory exists, C{False} otherwise @rtype: C{bool} """ (_stdin, _stdout, _stderr) = self._x2go_exec_command('stat -tL
"%s"' % self._x2go_remote_home, loglevel=log.loglevel_DEBUG) if _stdout.read(): return True return False
"""
What does 'stat -tL $HOME' result in when executed on the X2Go Server under the remote user account that cannot log in via PyHoca-GUI?
I get the following response:
% stat -tL $HOME /home/mfornero 24576 56 41c0 9281 101 25 5490934 73 0 0 1380167700 1445526133 1445526133 0 65536
I see this either logging in the standard x2go client or via a ssh session.
-Matt
Hi Matt,
On Do 22 Okt 2015 17:12:35 CEST, Matt Fornero wrote:
Hi Mike,
Thanks for the response. I did take a look at the code, but couldn't find anything obvious
The code that checks your home [1] is this:
""" def home_exists(self): """
Test if the remote home directory exists.@return: C{True} if the home directory exists, C{False} otherwise @rtype: C{bool} """ (_stdin, _stdout, _stderr) = self._x2go_exec_command('stat -tL
"%s"' % self._x2go_remote_home, loglevel=log.loglevel_DEBUG) if _stdout.read(): return True return False
"""
What does 'stat -tL $HOME' result in when executed on the X2Go Server under the remote user account that cannot log in via PyHoca-GUI?
I get the following response:
% stat -tL $HOME /home/mfornero 24576 56 41c0 9281 101 25 5490934 73 0 0 1380167700
1445526133 1445526133 0 65536I see this either logging in the standard x2go client or via a ssh session.
Please also check the actual content/value of self._x2go_remote_home
at runtime.
This can be done by adding a
print "DEBUG::: %s" % self._x2go_remote_home
to the above code. Then run pyhoca-gui from the command line and watch
for the line starting with "DEBUG:::"...
Mike
--
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/mailxchange/kronolith/fb.php?u=m.gabriel%40...
Hi Mike,
Please also check the actual content/value of self._x2go_remote_home at runtime.
This can be done by adding a
print "DEBUG::: %s" % self._x2go_remote_home
to the above code. Then run pyhoca-gui from the command line and watch for the line starting with "DEBUG:::"...
I am currently running via the win32 installer-- is there an easier way to instrument the code other than following the steps at [1] to get the full build environment?
[1] http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:pyhoca-gui
-Matt
Hi Matt,
On Do 22 Okt 2015 21:32:39 CEST, Matt Fornero wrote:
Hi Mike,
Please also check the actual content/value of self._x2go_remote_home at runtime.
This can be done by adding a
print "DEBUG::: %s" % self._x2go_remote_home
to the above code. Then run pyhoca-gui from the command line and watch for the line starting with "DEBUG:::"...
I am currently running via the win32 installer-- is there an easier
way to instrument the code other than following the steps at [1] to get the full build
environment?
You could simply try the Linux version of PyHoca-GUI. That is easier
to debug and the error is probably client-side platform independent.
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/mailxchange/kronolith/fb.php?u=m.gabriel%40...