Re: [X2Go-Dev] Bug#471: ATTENTION @Mike#1 - serious bug in x2goserver upgrade script (debian wheezy+squeeze)
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
Further Info:
- 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
- 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
Am 03.04.2014 10:13, schrieb Stefan Baur:
ps ax | grep x2gocleansessions | grep perl
| awk ' { print $1 }' | xargs -n 1 kill
Yep, can confirm. Hangs the whole update process. Just killed the x2gocleansessions process. Btw. the awk command above did not work on Kubuntu 13.10.
Hi Stefan, hi Panayotis
On Do 03 Apr 2014 09:52:58 CEST, Stefan Baur wrote:
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
Can you please:
o upgrade to 4.0.1.14 o killall x2gocleansessions once the init script hangs during upgrade o replace /usr/sbin/x2gocleansessions by this file [1] o sudo service x2goserver start o now it should not hang...
Sorry, I forgot one cherry-pick to the release/4.0.1.x branch in
x2goserver.git.
[1]
http://code.x2go.org/gitweb?p=x2goserver.git;a=blob;f=x2goserver/sbin/x2gocl...
Greets, 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/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 03.04.2014 10:19, schrieb Mike Gabriel:
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
Can you please:
o upgrade to 4.0.1.14
That is actually what I was doing - no idea why the ps output suggests that the 4.0.1.13-postinst is being called.
o killall x2gocleansessions once the init script hangs during upgrade
I used
ps ax | grep x2gocleansessions | grep perl
| awk ' { print $1 }' | xargs -n 1 kill
instead as I came up with that before you replied. (I wasn't sure if killall does more nasty things, and the system I was trying it on was already b0rked enough.)
... so I skipped this part ...
o replace /usr/sbin/x2gocleansessions by this file [1] o sudo service x2goserver start
... because this happens immediately after the kill:
o now it should not hang...
Sorry, I forgot one cherry-pick to the release/4.0.1.x branch in x2goserver.git.
Gna. Gnagnagna. :-/
-Stefan
On Do 03 Apr 2014 10:47:34 CEST, Stefan Baur wrote:
... because this happens immediately after the kill:
o now it should not hang...
Does service x2goserver start now work? Does the system reboot without
hanging?
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/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 03.04.2014 11:31, schrieb Mike Gabriel:
On Do 03 Apr 2014 10:47:34 CEST, Stefan Baur wrote:
... because this happens immediately after the kill:
o now it should not hang...
Does service x2goserver start now work? Does the system reboot without hanging?
Seems to work just fine here.
/etc/init.d/x2goserver start
squeeze: Cleaning up stale X2Go sessions.. And returns to the prompt immediately.
wheezy: [info] Cleaning up stale X2Go sessions.. And returns to the prompt immediately.
I rebooted my test machines (users wouldn't be happy about unscheduled reboots on the production ones) and it worked, too.
-Stefan
Hi Stefan,
On Do 03 Apr 2014 11:41:37 CEST, Stefan Baur wrote:
Am 03.04.2014 11:31, schrieb Mike Gabriel:
On Do 03 Apr 2014 10:47:34 CEST, Stefan Baur wrote:
... because this happens immediately after the kill:
o now it should not hang...
Does service x2goserver start now work? Does the system reboot without hanging?
Seems to work just fine here.
/etc/init.d/x2goserver start
squeeze: Cleaning up stale X2Go sessions.. And returns to the prompt immediately.
wheezy: [info] Cleaning up stale X2Go sessions.. And returns to the prompt immediately.
I rebooted my test machines (users wouldn't be happy about unscheduled reboots on the production ones) and it worked, too.
-Stefan
Ok. Same here.
Packages (4.0.1.15) are building on jenkins.x2go.org...
(Lauchpad/Ubuntu builds will follow soon).
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/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 03.04.2014 11:43, schrieb Mike Gabriel:
Packages (4.0.1.15) are building on jenkins.x2go.org... (Lauchpad/Ubuntu builds will follow soon).
Build failed. :-(
What's wrong?
-Stefan
-
Buddy Butterfly -
Mike Gabriel -
Stefan Baur