Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Jason Judge on May 19, 2002, 07:05:29 AM

Title: Internal network went dead!!
Post by: Jason Judge on May 19, 2002, 07:05:29 AM

Here's a strange one with SME 5.1.2

I was using the server (MySQL, PHP, Samba mounts, Web Proxy etc) when the backup started. After a few minutes the internal network stopped responding. I waited for the backups to finish (assuming the internal network was disabled while  the backups were ongoing) - the internal network was still dead.

So I rebooted my Windows machine thinking it had got confused by the dropped network - still dead. I found I could connect to server-manager through the console, so the web servers and databases were still running, it was just the internal network that did not work at all. No ping, no DNS, no web services, no Samba - nothing.

So - could this be a hardware problem, or is there something going on that kills network processes if you do certain things while the backup is running? Has this happened to anyone else, or is this a one off? A warn reboot via server-manager fixed the problem.

Jason

Title: Re: Internal network went dead!!
Post by: Nathan Fowler on May 20, 2002, 09:02:44 AM

Try running /etc/rc.d/init.d/masq restart

Title: Re: Internal network went dead!!
Post by: darren on May 20, 2002, 11:03:48 AM

I've had the same trouble also.
I too thought it was hardware, then the windows end...But as you have said a "reboot" of the server fixes everything.

I'll try "/etc/rc.d/init.d/masq restart" next time it happens too, Thanks Nathan.

Title: Re: Internal network went dead!!
Post by: Bill Talcott on May 20, 2002, 05:57:57 PM

I get it too. I can't ping to or from the local NIC, but everything else works fine, and a reboot fixes it. Sometimes it'll be fine for a month, another time it'll die again five minutes later...

Title: Re: Internal network went dead!!
Post by: Jason Judge on May 21, 2002, 03:36:59 AM

Thanks. Now I know where to start looking, I'll see if I can work what actually happened.

Sounds like it could be a common problem. If not common, it's certainly well-known.

-- JJ

Title: Re: Internal network went dead!!
Post by: Aavo Petrauts on May 21, 2002, 04:38:08 PM

Same problem here, about once a week.
# ifdown eth0
# ifup eth0
from console or remote over SSH fixes too.
I think this is 3Com905 NIC or driver problem?

Title: Re: Internal network went dead!!
Post by: Geoff Bennion on May 21, 2002, 05:06:01 PM

I have also had this problem.
I tracked it down to coping large amounts of data from my PC to Server ( Over 200mb would do it ).

To fix, I disabled full-duplex mode on my PC.

(Touch wood....... it hasn't happened since. )