From unknown Thu Mar 28 11:36:26 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#1063: CreateDB fails with error `DBI connect('dbname=/var/lib/x2go/x2go_sessions', '', ...) failed` Reply-To: Sivachidambaram Somu , 1063@bugs.x2go.org Resent-From: Sivachidambaram Somu Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Tue, 30 Aug 2016 16:10:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1063 X-X2Go-PR-Package: x2goserver X-X2Go-PR-Keywords: moreinfo Received: via spool by 1063-submit@bugs.x2go.org id=B1063.147257316032314 (code B ref 1063); Tue, 30 Aug 2016 16:10:01 +0000 Received: (at 1063) by bugs.x2go.org; 30 Aug 2016 16:06:00 +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=0.7 required=3.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id BD09E5DEFC for <1063@bugs.x2go.org>; Tue, 30 Aug 2016 18:05:58 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2QpATAeYewq for <1063@bugs.x2go.org>; Tue, 30 Aug 2016 18:05:52 +0200 (CEST) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id BF4185DEFB for <1063@bugs.x2go.org>; Tue, 30 Aug 2016 18:05:51 +0200 (CEST) Received: by mail-qk0-f181.google.com with SMTP id l2so23251243qkf.3 for <1063@bugs.x2go.org>; Tue, 30 Aug 2016 09:05:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IN29IHfa+CPRS0ykH7J1RAAiAGYMEwHW3JJSVl9vfr8=; b=TAghGUMGM6Ev2PmYcTLkZgACykaBALvn9peiP7spIsEWUdSERA9MgwJ90qJKtQYEcX GKyxqd83GbU4+VPZB+8Uw2+mkGxcJf64ZOXd1kjMzP0YDnGDAC6p5aYN7V9S8L94VGOk 3vVV0AarP4PshyenL9y4f5vUIBTeovulBTWJbX/GI7HJc8EQtacCegPlVLVFJEuOyZC7 2zms7YX/tD7BS+aqNCkMOw+hRaB65KZTApOcyXkP+y12FjKVLRscRaG/jvYIf4Skibdh 62I/XP4k+7du7ph3VX1wTWbs+1+FtCmBHgeo4rlZE6JwC1zaDmOqF2Welb2MG1nAXj75 7XdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=IN29IHfa+CPRS0ykH7J1RAAiAGYMEwHW3JJSVl9vfr8=; b=L8tCaxmoPkzs5n2o0Bzqhswdn6d45c4KuFXbaqG2zHI6jvhxMtjtLWmc4IT75103km Iz9GysslaCoPs6eMO30Kc50gOhVVA72NMeF3S5fG76UkIkNXN1kft3S6PT28A6woZ9xC LmEeuNlDGgWVgfM0CeEgEH8BR3oK4JdZ0EJZEG12BVNqQBt5r2mZXKX036Ev+vV4U57z fYgQSk2R1uaNtY+T5lezwMNO4AADd9jzXCw8ny2ZZCz1J7mP8PnEuQsAa3WzTiSnLt8s 2bzSAeTTwdAWYqxRGd1hpzpS2YQZOxPmvAP6zQ9QnGdmybzJv0pXynV/BNmftHGg+aOx epUQ== X-Gm-Message-State: AE9vXwNtM50duU2+pebT7aB6tcVJv2GDq8WpvfZIQRN7O98jPWt5ou3wnbLc46RaOwidJB85H+pMbMIYyXbn7Q== X-Received: by 10.55.184.198 with SMTP id i189mr4909990qkf.96.1472573150437; Tue, 30 Aug 2016 09:05:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.175.197 with HTTP; Tue, 30 Aug 2016 09:05:49 -0700 (PDT) In-Reply-To: <6fffe69a-2581-66a2-755f-93b84067e2be@ionic.de> References: <6b41f5b6-82ff-273c-ff64-390c17a44dea@ionic.de> <406759e0-2a96-8582-cc8e-46cd28a2779b@ionic.de> <6fffe69a-2581-66a2-755f-93b84067e2be@ionic.de> From: Sivachidambaram Somu Date: Tue, 30 Aug 2016 21:35:49 +0530 Message-ID: To: Mihai Moldovan Cc: 1063@bugs.x2go.org Content-Type: multipart/alternative; boundary=94eb2c07926089b1a2053b4c2704 --94eb2c07926089b1a2053b4c2704 Content-Type: text/plain; charset=UTF-8 I'm afraid the command was working as expected. % sudo chmod g+s $(which id) % id -g 0 % sudo chmod g-s $(which id) % id -g 100 Regards, Siva Chidambaram Somu On Tue, Aug 30, 2016 at 9:03 AM, Mihai Moldovan wrote: > On 29.08.2016 11:33 AM, Sivachidambaram Somu wrote: > > My bad. I have given below the output of the mount command on my machine. > > > > %mount > > > > /dev/xvda1 on / type auto (rw,noatime) > > > > proc on /proc type proc (rw) > > > > sysfs on /sys type sysfs (rw) > > > > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > > > > tmpfs on /dev/shm type tmpfs (rw) > > > > /dev/mapper/ephemeralVG-ephemeral on /local type ext4 (rw) > > > > none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) > > > > fusectl on /sys/fs/fuse/connections type fusectl (rw) > > Okay, no "nosuid" option in there, so that's also ruled out. > > > As a test, set the setgid bit on the id binary like this: > > sudo chmod g+s $(which id) > > then, as a non-root user(!) run: > > id -g > > Make sure to disable the setgit bit again with: > > sudo chmod g-s $(which id) > > > If the previous id -g call returned an effective group ID of 0, that means > that > setgid functionality should be working on your system. If it's not 0, the > reason > for your problems are likely that setgid on files is not working correctly > on > your system. > > > > Mihai > > --94eb2c07926089b1a2053b4c2704 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm afraid the command was working as expected.

% sudo chmod g+s $(which id) =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0

% id -g

0


% sudo chmod g-s $(which id)

% id -g=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0

100


Regards,
Siva Chidambaram Somu

On Tue, Aug 30, 2016 at 9:03 AM, Mihai Moldo= van <ionic@ionic.de> wrote:
<= span class=3D"">On 29.08.2016 11:33 AM, Sivachidambaram Somu wrote:
> My bad. I have given below the output of the mount command on my machi= ne.
>
> %mount
>
> /dev/xvda1 on / type auto (rw,noatime)
>
> proc on /proc type proc (rw)
>
> sysfs on /sys type sysfs (rw)
>
> devpts on /dev/pts type devpts (rw,gid=3D5,mode=3D620)
>
> tmpfs on /dev/shm type tmpfs (rw)
>
> /dev/mapper/ephemeralVG-ephemeral on /local type ext4 (rw)
>
> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
>
> fusectl on /sys/fs/fuse/connections type fusectl (rw)

Okay, no "nosuid" option in there, so that's also rule= d out.


As a test, set the setgid bit on the id binary like this:

sudo chmod g+s $(which id)

then, as a non-root user(!) run:

id -g

Make sure to disable the setgit bit again with:

sudo chmod g-s $(which id)


If the previous id -g call returned an effective group ID of 0, that means = that
setgid functionality should be working on your system. If it's not 0, t= he reason
for your problems are likely that setgid on files is not working correctly = on
your system.



Mihai


--94eb2c07926089b1a2053b4c2704--