Page 29 of 32

Re: New shell server transition

Posted: Wed May 30, 2018 8:23 am
by patty1
I just got the same error message on sh.sonic.net as Goetsch did a few days ago:

Code: Select all

Password: 
PTY allocation request failed on channel 0
Warning: no access to tty (Bad file descriptor).
Thus no job control in this shell.


Culture is the habit of being pleased with the best and knowing why.

So it took my password and even displayed a fortune, but then nothing else happened.

Re: New shell server transition

Posted: Thu May 31, 2018 9:09 am
by sdogjm
I am occasionally getting cron failures where cron cannot open the script file. I'm getting email from Cron Daemon with the following message:

Could not open input file: /home/s/sdogjm/wxpost2.php

It occurred several times this morning (5/31 between 2:20am and 2:45am)

Transport endpoint is not connected

Posted: Sun Jun 03, 2018 7:28 pm
by chongo
Hello,

I am helping my father try to get his TurboFTP program (on his Windows 7 box) to connect to the new shell.sonic.net.

When we ssh to paulnoll@shell.sonic.net we sometimes see the error message:

-bash: /home/p/paulnoll/.bash_profile: Transport endpoint is not connected
_[/home/p/paulnoll]_(paulnoll@sh)_

I seem to always be able ssh login to my account chongo@shell.sonic.net and see my files, but we sometimes cannot via his account. We say "sometimes see the error message" because sometimes the ssh connection to paulnoll@shell.sonic.net is successful as we DO see his files. This "Transport endpoint is not connected" problem comes and goes.

Any ideas why we sometimes see "Transport endpoint is not connected"?

Re: Transport endpoint is not connected

Posted: Tue Jun 05, 2018 11:29 am
by scott
chongo wrote:Hello,

I am helping my father try to get his TurboFTP program (on his Windows 7 box) to connect to the new shell.sonic.net.

When we ssh to paulnoll@shell.sonic.net we sometimes see the error message:

-bash: /home/p/paulnoll/.bash_profile: Transport endpoint is not connected
_[/home/p/paulnoll]_(paulnoll@sh)_

I seem to always be able ssh login to my account chongo@shell.sonic.net and see my files, but we sometimes cannot via his account. We say "sometimes see the error message" because sometimes the ssh connection to paulnoll@shell.sonic.net is successful as we DO see his files. This "Transport endpoint is not connected" problem comes and goes.

Any ideas why we sometimes see "Transport endpoint is not connected"?
That's the error that gets thrown when the backend ssh process to sshfs loses its connection. I've seen that after killing the underlying ssh process, but not sure why that would happen upon connect.

If it happens again, please note the time. I'm looking through the logs to see what could be causing this.

-Scott

Re: New shell server transition

Posted: Tue Jun 05, 2018 5:48 pm
by scott
Just read up on the "autologout" feature for tcsh.

Turns out it will log you out after 60 minutes if you don't have the "DISPLAY" variable set, which is its way of determining that one is running under a window system.

I'll increase that to 120 minutes. Folks can, of course, change it on their own...

-Scott

Re: New shell server transition

Posted: Wed Jun 06, 2018 8:15 am
by gtwrek
The new shell server is down this morning. Last night I received a wall message regarding a reboot "to clear old bind mounts". It's been unavailable since. An ssh session does connect, and accepts password, but then hangs.

oldshell.sonic.net seems fine.

Regards,

Mark

Re: New shell server transition

Posted: Wed Jun 06, 2018 11:08 am
by netllama
gtwrek wrote:The new shell server is down this morning. Last night I received a wall message regarding a reboot "to clear old bind mounts". It's been unavailable since. An ssh session does connect, and accepts password, but then hangs.

oldshell.sonic.net seems fine.

Regards,

Mark
Yup, same issue here. The reliability of the new server has been quite poor.

Re: New shell server transition

Posted: Thu Jun 07, 2018 3:54 am
by scott
netllama wrote:
gtwrek wrote:The new shell server is down this morning. Last night I received a wall message regarding a reboot "to clear old bind mounts". It's been unavailable since. An ssh session does connect, and accepts password, but then hangs.

oldshell.sonic.net seems fine.

Regards,

Mark
Yup, same issue here. The reliability of the new server has been quite poor.
Indeed it has. We appreciate your patience while we try to figure out this elusive and maddening problem.

It fell over again this morning at 2am. (It is now 3:52am, I reset it.) Adding memory didn't help. As much as it pains me, we're going to have to stagger 2am and 3am cron jobs until we can figure out why firing off a dozen cron jobs at once is causing a problem. (It _should_ be fine with that.)

-Scott

Re: New shell server transition

Posted: Thu Jun 07, 2018 8:18 am
by yronwode
It seems that you're still working on it. Thanks, if so. I keep getting disconnected. It's not urgent, but i would prefer not having to keep re-connecting.

Re: New shell server transition

Posted: Thu Jun 07, 2018 9:27 am
by casner
yronwode wrote:It seems that you're still working on it. Thanks, if so. I keep getting disconnected. It's not urgent, but i would prefer not having to keep re-connecting.
Scott mentioned turning off some keepalives. That may be counterproductive for this problem. So long as the underlying network connectivity is stable, sending keepalives avoids having NAT devices time out the connection.

[As an aside, I'll mention that back in the early days of the Internet (late 1970s and 1980s) there were folks working on packet radio who hated keepalives because their network connectivity was intermittent. Their TCP connections would break even if they weren't active during the time of a connectivity loss due to a keepalive being sent automatically. But that was before NATs created the converse problem.]