Re: [CentOS] problem on exceptional quit

On 10/10/2015 11:25 PM, Hua Wang wrote: I am not sure if we can not send attachments to the mailing list. There were quite a lot replies before, but I got nothing back since attachements was added. I will remove the attachments and send it again. You can use services like pastebin.com to

Re: [CentOS] problem on exceptional quit

I am not sure if we can not send attachments to the mailing list. There were quite a lot replies before, but I got nothing back since attachements was added. I will remove the attachments and send it again. Please have a look at the email below. Thanks for your help. --- Dear All, Thanks for

Re: [CentOS] problem on exceptional quit

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

Re: [CentOS] problem on exceptional quit

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

Re: [CentOS] problem on exceptional quit

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

Re: [CentOS] problem on exceptional quit

Which logfile shall I have a look? Thanks, Hua At 2015-10-08 21:55:50, "Jonathan Billings" wrote: >On Thu, Oct 08, 2015 at 09:32:41PM +0800, Hua Wang wrote: >> Is there a way to catch what’s happing before quit? I couldn’t see >> anything except for the line ‘write failed,

Re: [CentOS] problem on exceptional quit

On Thu, Oct 08, 2015 at 09:32:41PM +0800, Hua Wang wrote: > Is there a way to catch what’s happing before quit? I couldn’t see > anything except for the line ‘write failed, broken pipe’. At this point, I'd suggest looking at the logs on the remote end and look to see what's being logged when the

Re: [CentOS] problem on exceptional quit

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" wrote: >On 10/07/2015 11:45 PM, Hua Wang wrote: I tried to ping the server, and it can

Re: [CentOS] problem on exceptional quit

Am 08.10.2015 um 15:32 schrieb Hua Wang : > 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

Re: [CentOS] problem on exceptional quit

On Thu, Oct 08, 2015 at 10:20:17PM +0800, Hua Wang wrote: > Which logfile shall I have a look? Thanks, That depends on the OS of the remote server. If it's CentOS 6, then I suggest checking /var/log/messages and /var/log/secure. -- Jonathan Billings

Re: [CentOS] problem on exceptional quit

On 10/07/2015 07:33 PM, Hua Wang wrote: I installed Centos 7 on my server a few months ago. While using ssh, there is always a strange message "Write failed: Broken pipe”. That's very often a result of IP conflict. I'm assuming that you're connecting to an IPv4 address. If so, log in to

Re: [CentOS] problem on exceptional quit

​Can you trigger the error reliably by doing something network intenstive, like scp or rsync a large file? I've seen similar behaviour with a bad NIC that was in the process of dying. ___ CentOS mailing list CentOS@centos.org

Re: [CentOS] problem on exceptional quit

On 09/10/15 10:23, Gordon Messmer wrote: Since those don't help, that tends to suggest that the problem isn't an intermediate host, but the server itself. Possibly an IP conflict. Also, check the output of "dmesg" to see if there are any problems recorded with the NIC. Check the output of

Re: [CentOS] problem on exceptional quit

Dear All, Attached is my sushi_config file. In addition, I forgot to say that I added the second raid (raid 5 with 6*3Gb disks) while reinstalling Centos 7. There was only one raid for Centos 6.6 (raid 6 with 6*2Gb disks). So now there are two raids, and both are raid 5. Thanks. Hua

[CentOS] problem on exceptional quit

Dear Centos Users: I installed Centos 7 on my server a few months ago. While using ssh, there is always a strange message "Write failed: Broken pipe”. It forces quit of SSH. It’s really annoying as it happens very often with irregular time interval - from a couple of minutes to a few hours. I

Re: [CentOS] problem on exceptional quit

Hi Frank, Thanks for your prompt reply. The server is in my office. Because I tried a few computers, so it shouldn’t be a problem of Internet connection of the clients. I tried to ping the server, and it can accept all data. Is there a good way to check it? It always worked well for centos

Re: [CentOS] problem on exceptional quit

On Thu, 8 Oct 2015 10:33:55 +0800 Hua Wang wrote: > While using ssh, there is always a strange message "Write failed: Broken > pipe”. It forces quit of SSH. It sounds like the network connection between you and the server is dying for some reason. That being the case you probably can't fix it

Re: [CentOS] problem on exceptional quit

On Thu, 8 Oct 2015 11:18:17 +0800 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. > The problem came out while reinstalling centos 7.7. Since you're

Re: [CentOS] problem on exceptional quit

> >> 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