X2Go Bug report logs - #471
ATTENTION @Mike#1 - serious bug in x2goserver upgrade script (debian wheezy+squeeze)

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#471: [X2Go-Dev] Bug#471: Bug#471: ATTENTION @Mike#1 - serious bug in x2goserver upgrade script (debian wheezy+squeeze)
Reply-To: Stefan Baur <newsgroups.mail2@stefanbaur.de>, 471@bugs.x2go.org
Resent-From: Stefan Baur <newsgroups.mail2@stefanbaur.de>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: owner@bugs.x2go.org
Resent-Date: Thu, 03 Apr 2014 08:15:02 +0000
Resent-Message-ID: <handler.471.B471.139651279517179@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 471
X-X2Go-PR-Package: x2goserver
X-X2Go-PR-Keywords: 
Received: via spool by 471-submit@bugs.x2go.org id=B471.139651279517179
          (code B ref 471); Thu, 03 Apr 2014 08:15:02 +0000
Received: (at 471) by bugs.x2go.org; 3 Apr 2014 08:13:15 +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=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS,
	URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187])
	by ymir (Postfix) with ESMTP id 2A7625DB16
	for <471@bugs.x2go.org>; Thu,  3 Apr 2014 10:13:14 +0200 (CEST)
Received: from [192.168.0.3] (dslb-188-099-193-217.pools.arcor-ip.net [188.99.193.217])
	by mrelayeu.kundenserver.de (node=mreue003) with ESMTP (Nemesis)
	id 0M9LBa-1WK6j02u1W-00CgIw; Thu, 03 Apr 2014 10:13:05 +0200
Message-ID: <533D182A.4000207@stefanbaur.de>
Date: Thu, 03 Apr 2014 10:13:30 +0200
From: Stefan Baur <newsgroups.mail2@stefanbaur.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "x2go-dev@lists.berlios.de" <x2go-dev@lists.berlios.de>, 
 471@bugs.x2go.org, Mike Gabriel <mike.gabriel@das-netzwerkteam.de>, 
 panayotis@panayotis.com, 
 "x2go-user@lists.berlios.de" <x2go-user@lists.berlios.de>
References: <533D12B1.50501@stefanbaur.de> <533D135A.9090902@stefanbaur.de>
In-Reply-To: <533D135A.9090902@stefanbaur.de>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Provags-ID: V02:K0:iDaAGLWlIAVKj694z4k0RssbUahBnJT/a6aR679+rbp
 hsdKzv1yU7VNWEZAVKQaOzREPjP79ORB0DH+0C2tZhoz5/YOWZ
 BLrUG9UiOYAbLArPLBo0tnk9chZW+dvhrqO1R73g/LDR1o6mgl
 IySy3fcABBEUgxbVrl96Uyd3Zi5IcRLpl/HGm0eRjXa/lEukVa
 RvD/YPLa6Jc8v9byrKGfdQKGorYZMMOlvFr2wgVs3hnP8Sbcuf
 J+x8DZQrpgmY2/u9BtRg7G9+pTX2EtBcRNeuxmdh5+5vSKyPPh
 Tsag+xtlzbNDD5t8c6Dsf9LeWPyuuV256MqRZqvYTLewNxVHI8
 6za7dz9ebQY7JyKDo+6UTFsXj1RFv01dtXj5DbZ0Y

Further Info:

1) I'm guessing it's a race condition, with two instances of
x2gocleansessions running simpultaneously and locking each other up:

e.g. sample output:

ps ax|grep clean
 1995 ?        S      0:36 /usr/bin/perl /usr/sbin/x2gocleansessions
16142 pts/0    S+     0:05 /usr/bin/perl /usr/sbin/x2gocleansessions

2) The kill command given below in my previous e-mail doesn't work.
What worked was this:

ps ax | grep x2gocleansessions | grep perl \
| awk ' { print $1 }' | xargs -n 1 kill

(the backslash is so it can be broken up in two lines)
You have to run this in a second terminal session (as root) while the
apt-get upgrade process is stuck in the first.

It will then continue without reporting an error.

-Stefan


Am 03.04.2014 09:52, schrieb Stefan Baur:
> Gah. E_NOTENOUGHCAFFEINE. This was supposed to go to the list and
> bugtracker as well.
> 
> 
> -------- Original-Nachricht --------
> Betreff: Re: [X2Go-Dev] Bug#471: ATTENTION @Mike#1 - serious bug in
> x2goserver upgrade script (debian wheezy+squeeze)
> Datum: Thu, 03 Apr 2014 09:50:09 +0200
> Von: Stefan Baur <newsgroups.mail2@stefanbaur.de>
> Antwort an: Stefan Baur <newsgroups.mail2@stefanbaur.de>,
> 471@bugs.x2go.org, x2go-dev@lists.berlios.de
> An: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
> 
> Addendum:
> 
> This is part of the "ps ax" output on one of the affected machines:
> 
>  2563 pts/2    S+     0:00 apt-get upgrade -y
>  4958 pts/1    S+     0:00 /usr/bin/perl -w /usr/share/debconf/frontend
> /var/lib/dpkg/info/x2goserver.postinst configure 4.0.1.13-0x2go1+
>  4962 pts/1    Z+     0:00 [x2goserver.post] <defunct>
>  5004 pts/1    S+     0:00 /usr/bin/perl /usr/sbin/x2gocleansessions
> 
> manually killing x2gocleansessions (" kill $(pidof x2gocleansessions)")
> seems to be a workaround, but still, we need a real fix in the form of
> an updated package.
> 
> -Stefan
> 
> Am 03.04.2014 08:47, schrieb Stefan Baur:
>> Package: x2goserver
>> Severity: grave
>> Version: 4.0.1.14
>>
>> Hi Mike,
>>
>> this is happening on
>>
>> x2goserver (4.0.1.14-0x2go1+git20140402.842+squeeze.main.1)
>>
>> as well.
>>
>> Please help! All my machines are stuck in the upgrade process! This is
>> not good!
>>
>> -Stefan
>>
>>
>> -------- Original-Nachricht --------
>> Betreff: [X2Go-User] Unable to upgrade
>> Datum: Wed, 2 Apr 2014 19:14:53 +0300
>> Von: Panayotis Katsaloulis <panayotis@panayotis.com>
>> An: x2go-user@lists.berlios.de
>>
>> Hello all!
>>
>> I have installed x2go, I can connect - everything is fine.
>> In the past I think there was a problem when I tried to launch a client
>> (as xterm session), and which I was unable to properly close, so I
>> forced close it.
>>
>> The problem is that I am unable to upgrade through apt-get upgrade though.
>>
>> Now when I try to upgrade I get this message:
>>
>> Processing triggers for menu (2.1.46) ...
>> Setting up x2goserver (4.0.1.14-0x2go1+git20140402.842+wheezy.main.1) ...
>> Group x2gouser already exists.
>> User x2gouser already exists.
>> [info] Cleaning up stale X2Go sessions..
>>
>> … and the screen remains like this forever.
>>
>> The uname -a command produces the following result:
>>
>> Linux danube 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64
>> GNU/Linux
>>
>> Any help?
>>
>> --
>> Panayotis
>>
>>
>> _______________________________________________
>> X2Go-User mailing list
>> X2Go-User@lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/x2go-user
>> _______________________________________________
>> X2Go-Dev mailing list
>> X2Go-Dev@lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/x2go-dev
>>
> _______________________________________________
> X2Go-Dev mailing list
> X2Go-Dev@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/x2go-dev
> 

Send a report that this bug log contains spam.