As I'm no longer able to VNC into ss-andreas, I'm not able to do any diagnostics on the production server. I emailed about this a few weeks ago but got no responses.
Remmina is suddenly refusing to connect, and I see this message in my terminal window:
channel 3: open failed: administratively prohibited: open failed .
I'm tunneling port 5901 to that on my localhost when I log in:
ssh -L 5901:locahost:5901 chrismuller@andreas
and then connecting Remmina to localhost:5901. I tried using ssh within the tunnel, I didn't see the "administrative message" but Remmina locked up.
I never had this problem before, and not expert enough with SSH and haven't had time to google it. Sorry.
- Chris On Tue, Oct 2, 2018 at 12:08 PM Levente Uzonyi leves@caesar.elte.hu wrote:
My impression is that these slowdowns are present since the update to the Magma backend. I haven't seen the code yet, but I presume the code accessing data from Magma is responsible for this, and someone familiar with Magma can easily fix it.
Levente
Hi Chris,
I just checked and I could create tunnels and connect to the VNC server in the image through the tunnel. I also checked the server configuration and didn't find any restriction on tunnel creation which would explain the problems you experienced. One thing I would try is to use 127.0.0.1 instead of localhost in the command, because localhost is just a name that can resolve to whatever address on the server:
ssh -L 5901:127.0.0.1:5901 chrismuller@andreas
Levente
On Tue, 2 Oct 2018, Chris Muller wrote:
As I'm no longer able to VNC into ss-andreas, I'm not able to do any diagnostics on the production server. I emailed about this a few weeks ago but got no responses.
Remmina is suddenly refusing to connect, and I see this message in my terminal window:
channel 3: open failed: administratively prohibited: open failed .
I'm tunneling port 5901 to that on my localhost when I log in:
ssh -L 5901:locahost:5901 chrismuller@andreas
and then connecting Remmina to localhost:5901. I tried using ssh within the tunnel, I didn't see the "administrative message" but Remmina locked up.
I never had this problem before, and not expert enough with SSH and haven't had time to google it. Sorry.
- Chris
On Tue, Oct 2, 2018 at 12:08 PM Levente Uzonyi leves@caesar.elte.hu wrote:
My impression is that these slowdowns are present since the update to the Magma backend. I haven't seen the code yet, but I presume the code accessing data from Magma is responsible for this, and someone familiar with Magma can easily fix it.
Levente
One thing I would try is to use 127.0.0.1 instead of localhost in the command, because localhost is just a name that can resolve to whatever address on the server:
ssh -L 5901:127.0.0.1:5901 chrismuller@andreas
That worked, thank you Levente!
I logged in and checked the processes, there were no stuck Mutex's as we've gotten a few times in the past.
So it's looking more and more like it was probably just that background indexing that was happening at that moment. My guess is, response times are reasonable again.
box-admins@lists.squeakfoundation.org