From unknown Sat Apr 04 21:18:58 2026
X-Loop: owner@bugs.x2go.org
Subject: Bug#708: [X2Go-Dev] Bug#708: x2gosqlitewrapper.pl reports "unable to open database" on session-resume, while the database is there.
Reply-To: "Zuck, Daniel" <Daniel.Zuck@six-group.com>, 708@bugs.x2go.org
Resent-From: "Zuck, Daniel" <Daniel.Zuck@six-group.com>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Fri, 19 Dec 2014 17:15:01 +0000
Resent-Message-ID: <handler.708.B708.141900908510986@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 708
X-X2Go-PR-Package: x2goserver
X-X2Go-PR-Keywords: 
Received: via spool by 708-submit@bugs.x2go.org id=B708.141900908510986
          (code B ref 708); Fri, 19 Dec 2014 17:15:01 +0000
Received: (at 708) by bugs.x2go.org; 19 Dec 2014 17:11:25 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	URIBL_BLOCKED autolearn=ham version=3.3.2
X-Greylist: delayed 302 seconds by postgrey-1.34 at ymir.das-netzwerkteam.de; Fri, 19 Dec 2014 18:11:23 CET
Received: from mail1.telekurs.com (mail1.telekurs.com [153.46.252.105])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id EA0575DB26
	for <708@bugs.x2go.org>; Fri, 19 Dec 2014 18:11:23 +0100 (CET)
Received: from mpslwcasht04.base.dom (Not Verified[10.22.145.153]) by mail1.telekurs.com (using TLS: SSLv23)
	id <B54945b0d0001>; Fri, 19 Dec 2014 18:06:21 +0100
Received: from MPZHWMBX15.base.dom ([fe80::656e:e4bd:cdcf:2423]) by
 mpslwcasht04.base.dom ([::1]) with mapi id 14.03.0195.001; Fri, 19 Dec 2014
 18:06:19 +0100
From: "Zuck, Daniel" <Daniel.Zuck@six-group.com>
To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, "708@bugs.x2go.org"
	<708@bugs.x2go.org>
CC: "Talvacchia, Claudio" <Claudio.Talvacchia@six-group.com>
Thread-Topic: [X2Go-Dev] Bug#708: x2gosqlitewrapper.pl reports "unable to
 open database" on session-resume, while the database is there.
Thread-Index: AdAbcna5yjlC/yhRRmuJQBlLoPDh5gAEfa8AAAWXaJA=
Date: Fri, 19 Dec 2014 17:06:18 +0000
Message-ID: <B62526E3DA9E30409AE8B69A0AC2F588A32334A1@mpzhwmbx15.base.dom>
References: <B62526E3DA9E30409AE8B69A0AC2F588A32332AE@mpzhwmbx15.base.dom>
 <13739125.23926.1418993547875.JavaMail.totemomail@apzhtotemo11.telekurs.com>
In-Reply-To: <13739125.23926.1418993547875.JavaMail.totemomail@apzhtotemo11.telekurs.com>
Accept-Language: de-CH, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.22.12.42]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hello Mike

Thanks for your quick feedback.

In a nutshell: I was as well assuming, that a hard fix would be at the en=
d "x2godbadmin --createdb" - however, it would be good to trace the reaso=
n why it came to there. Related the Perl modules on SLES, I am not 100% s=
ure, as I am not a "Perl guy", and resolved dependencies if they have bee=
n specifically raised via " "make_path" is not exported by the File::Path=
=20module" (see http://wiki.x2go.org/doku.php/doc:installation:x2goserver=
), which was causing me to lift the version of this module (the SLES prov=
ided version was too old, so this issue was sorted after the upgrade; sam=
e for the RHEL install as described on the Wiki).

In more details:

>First thing: please note that shortly the X2Go upstream team will provid=
e a new source for SLES packages. The x2goserver version you are using is=
=20a >little outdated already.

The version is "backported" from OpenSuSE RPM spec's, satisfying the depe=
ndencies on SLES. Notably dependencies included to upgrade some of the SL=
ES-provided Perl modules.

>I am not sure what perl-Syslog package version is shipped with SLES 11.3=
, but it seems it cannot handle the "error" logging facility. This is wei=
rd in >the first place and maybe you can investigate your system a bit mo=
re on this. (What version of perl-Syslog is installed, etc.)

The version of Perl is 5.10.0-64.67.52, and there is no specific syslog i=
nstalled besides the OS-Perl-package (there is a separate perl-Unix-Syslo=
g from SuSE, where I do not know its specific use); it must be a subseque=
nt fault of something else, because syslog and its facilities should be w=
ell known since a couple of "decades"...

As we have likely a corrupted DB-file, I would try to lift the version of=
=20Perl-DBI (maybe the SLES-version is a bit older and has some errors).

>Next question is: what file permissions are set on
>   /var/lib/x2go/x2go_sessions
>   /usr/<lib>/x2go/x2gosqlitewrapper

ls -la /var/lib/x2go/x2go_sessions /usr/lib/x2go/x2gosqlitewrapper
-rwxr-sr-x 1 root x2gouser 11978 Nov  4 17:53 /usr/lib/x2go/x2gosqlitewra=
pper
-rw-rw---- 1 root x2gouser 25600 Dec 19 10:35 /var/lib/x2go/x2go_sessions=


>Next question:
>   getent passwd x2gouser
>   getent group x2gouser

getent passwd x2gouser
x2gouser:x:404:405:x2go server/user:/var/lib/x2go:/bin/false
getent group x2gouser
x2gouser:!:405:

After removing the DB-file and recreating a new one, I can connect withou=
t any error. As expected my "old" session was stale.
Note: This is the behavior where the system was working since a couple of=
=20weeks; the error was raised on two systems at a time. What made me a b=
it perplex is, that it was visible on two systems, since about the same t=
ime.

Regards
Daniel

The content of this e-mail is intended only for the confidential use of t=
he person addressed.=20
If you are not the intended recipient, please notify the sender and delet=
e this email immediately.
Thank you.
