It is working now, but wasn't at the time I posted.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Wed, 24 Jun 2015, Michael DePaulo wrote:
Date: Wed, 24 Jun 2015 18:31:06 -0400 From: Michael DePaulo <mikedep333@gmail.com> To: Robert Dinse <nanook@eskimo.com> Cc: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org>, "x2go-project@lists.x2go.org" <x2go-project@lists.x2go.org>, "x2go-dev@lists.x2go.org" <x2go-dev@lists.x2go.org> Subject: Re: [X2Go-User] Japsand Maintenance Aftermath a.k.a. "Lessons Learned"
Right now, I am able to connect to japsand fine.
- That wiki URL loads successfully.
- I connected to an LXDE X2Go session (only X2Go developers have access.)
- I connected to an rdesktop session to the WinBuilder VM (although someone else was already logged in, so I canceled.)
-Mike#2
On Wed, Jun 24, 2015 at 5:56 PM, Robert Dinse <nanook@eskimo.com> wrote:
It would seem the Wiki is still down, when I try to go to: http://wiki.x2go.org/doku.php/doc:usage:pyhoca-gui I get cannot connect to server.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Wed, 24 Jun 2015, Mihai Moldovan wrote:
Date: Wed, 24 Jun 2015 23:25:33 +0200 From: Mihai Moldovan <ionic@ionic.de> Reply-To: "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> To: "x2go-project@lists.x2go.org" <x2go-project@lists.x2go.org>, "x2go-dev@lists.x2go.org" <x2go-dev@lists.x2go.org>, "x2go-user@lists.x2go.org" <x2go-user@lists.x2go.org> Subject: [X2Go-User] Japsand Maintenance Aftermath a.k.a. "Lessons Learned"
Hi
Due to a hanging rm process, we had to restart the server today.
After rebooting the machine, it was decided to also update the system to the latest packages version, but still staying on Debian Wheezy (for now.)
The server is using a custom kernel module provided by Realtek for its RTL8168 ethernet NIC. An in-kernel driver is available, but proved to be too unreliable, leading to frequent network outages and even machine crashes whenever the network IO load was higher than a few hundred KB/s. The hosting provider has a wiki entry for this issue at this location: http://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers/en
Unfortunately, the current driver version as provided by Realtek, 8.040, seems to be incompatible with the old 3.2.0-4-amd64 (3.2.68-1+deb7u2) kernel provided by Debian.
As of writing this, I do not know what happened exactly, but most likely the module caused a kernel panic during bootup.
Reverting to an older version, 8.037, fixed this issue and let the server boot up correctly again. For future maintenance work, please use this older version, at least on Debian Wheezy.
I put the module source code into /usr/src and created a symlink from /usr/src/r8168-current to /usr/src/r8168-8.037.00.
Other updated packages include Java (version 7 co-installed, the "alternatives" symlink now point to version 7 instead of 6) and Jenkins, including its plugins.
A test build run suggests the Jenkins update was successful.
Mihai
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user