> >> I tried to ping the server, and it can accept all data. Is there a good way >> to check it? > > ssh -v, ssh -vv and ssh -vvv might give you some interesting information. >Yes, I tried ssh -vvv. It gave a lot of information while login, but it quit without any further information except for ?write failed, broken pipe?.>> The problem came out while reinstalling centos 7.7. > > Since you're apparently using some kind of an unofficial or non-standard version of Centos, you might want to try using a current (regular) one instead. >Sorry I made a mistake for the version. I am using v7 instead of v7.7. Thanks, Hua ----------------------------- Hua Wang, Ph.D. in Geodesy Department of Surveying Engineering, Guangdong University of Technology, 100 Waihuan Xi Rd., Panyu District, Guangzhou, 510006, China. Tel: +86-13570019257 Email: ehwang at 163.com Homepage: http://homepages.see.leeds.ac.uk/~earhw
On 10/07/2015 10:45 PM, Hua Wang wrote:> >> >>> I tried to ping the server, and it can accept all data. Is there a good way >>> to check it? >> >> ssh -v, ssh -vv and ssh -vvv might give you some interesting information. >> > Yes, I tried ssh -vvv. It gave a lot of information while login, but it quit without any further information except for ?write failed, broken pipe?. > >>> The problem came out while reinstalling centos 7.7. >> >> Since you're apparently using some kind of an unofficial or non-standard version of Centos, you might want to try using a current (regular) one instead. >> > > Sorry I made a mistake for the version. I am using v7 instead of v7.7. >Try using ClientAliveMaxCount and ServerAliveCountMax (you can set them to 5 or 8 instead of the default of 3 and also make the timeouts higher than 60. make sure you are using 'protocol 2'. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20151008/a685330b/attachment-0001.sig>
On 10/07/2015 11:45 PM, Hua Wang wrote:>>> I tried to ping the server, and it can accept all data. Is there a good way >>> to check it? >> ssh -v, ssh -vv and ssh -vvv might give you some interesting information. >> > Yes, I tried ssh -vvv. It gave a lot of information while login, but it quit without any further information except for ?write failed, broken pipe?. > >>> The problem came out while reinstalling centos 7.7. >> Since you're apparently using some kind of an unofficial or non-standard version of Centos, you might want to try using a current (regular) one instead. >> > Sorry I made a mistake for the version. I am using v7 instead of v7.7. > > Thanks, > > HuaI'm grasping at straws, admittedly, but does this happen after an extended amount of time? i.e. you make the connection (possibly to use a ssh tunnel running over the session), leave it for some time, then return to trying to use the tunnel and go back to see the connection error about the failure to write to write? are you sure the remote server isn't doing some sort of idle cleanup to kill off idle sessions? -- public gpg key id: 1362BA1A
Dear Zep, Thanks for your email. But it happened even when I was typing some command line. So it could be a problem of idle cleanup. Hua At 2015-10-08 19:43:05, "zep" <zgreenfelder at gmail.com> wrote:>On 10/07/2015 11:45 PM, Hua Wang wrote: >>>> I tried to ping the server, and it can accept all data. Is there a good way >>>> to check it? >>> ssh -v, ssh -vv and ssh -vvv might give you some interesting information. >>> >> Yes, I tried ssh -vvv. It gave a lot of information while login, but it quit without any further information except for ?write failed, broken pipe?. >> >>>> The problem came out while reinstalling centos 7.7. >>> Since you're apparently using some kind of an unofficial or non-standard version of Centos, you might want to try using a current (regular) one instead. >>> >> Sorry I made a mistake for the version. I am using v7 instead of v7.7. >> >> Thanks, >> >> Hua > >I'm grasping at straws, admittedly, but does this happen after an extended amount of time? >i.e. you make the connection (possibly to use a ssh tunnel running over the session), leave >it for some time, then return to trying to use the tunnel and go back to see the connection >error about the failure to write to write? are you sure the remote server isn't doing >some sort of idle cleanup to kill off idle sessions? >-- >public gpg key id: 1362BA1A > >_______________________________________________ >CentOS mailing list >CentOS at centos.org >https://lists.centos.org/mailman/listinfo/centos
Dear Johnny, Yes, I have tried much larger numbers than 60 and 3 for the above two parameters respectively. And I am sure it is using ?protocol 2? because it?s uncommented in sshd_config. Is there a way to catch what?s happing before quit? I couldn?t see anything except for the line ?write failed, broken pipe?. Thanks. Hua At 2015-10-08 19:37:24, "Johnny Hughes" <johnny at centos.org> wrote:>On 10/07/2015 10:45 PM, Hua Wang wrote: >> >>> >>>> I tried to ping the server, and it can accept all data. Is there a good way >>>> to check it? >>> >>> ssh -v, ssh -vv and ssh -vvv might give you some interesting information. >>> >> Yes, I tried ssh -vvv. It gave a lot of information while login, but it quit without any further information except for ?write failed, broken pipe?. >> >>>> The problem came out while reinstalling centos 7.7. >>> >>> Since you're apparently using some kind of an unofficial or non-standard version of Centos, you might want to try using a current (regular) one instead. >>> >> >> Sorry I made a mistake for the version. I am using v7 instead of v7.7. >> > >Try using ClientAliveMaxCount and ServerAliveCountMax (you can set them >to 5 or 8 instead of the default of 3 and also make the timeouts higher >than 60. > >make sure you are using 'protocol 2'. >