Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Slackware 10.1 Server Hangs When large amounts of...

Status
Not open for further replies.

tobyheywood

IS-IT--Management
Apr 20, 2001
122
GB
Dear all,

I have a SuperMicro server (P4, 1GB RAM, 1TB SATA HDD using RAID 5). OS is Slackware 10.1 with kernel 2.6.13.2.

For some unknown reason, whilst connected via SSH if I were to perform a directory list starting from / or maybe extract a tar file verbosely it will output a certain amount of text to the ssh console and then the server locks up. Cannot be be reached again via the network and I have to request that someone attend it to physically reboot it.

Could anyone suggest possible reasons for this?

There seems to be no really pattern other than that described above, however i can some times perform the above task without incident.

I would greatly appreciate any suggestions you may have.

Regards

Toby Heywood

 
What version of SSH are you using?
I've never had an issue with 10.1 or 10.2 on the standard versions of SSH


"If you always do what you've always done, you will always be where you've always been."
 
depending on what network devices you are traversing to get from your client to that server (ie maybe a router or 2)

check the mtu size on the server and if you can the routers.
 
rzs0502:

ssh version is nothing special. It's the standard version which ships with 10.1 of slackware.

Stanhubble:

MTU is set to 1500 on the box experiencing the issues but I checked the other boxes (admittedly on different hardware) but the are set to 1500. Only major difference is that I'm using a 2.6 kernal on the supermicro box and a 2.4 on the other ones.

I'll ask my ISP if they are willing to share information about MTU size of their routers, but some how doubt it.

When the server dies it doesn't have a chance to write anything to logs, so I guess that it is quite possible for it to be related to SSH or the NIC driver, however I have now used two different versions of the NIC driver and I still end up with the same symptoms.

If you have any other suggestions they would be greatly appreciated.

Regards

Toby Heywood

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top