LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices

Reply
 
LinkBack Search this Thread
Old 03-29-2003, 02:42 AM   #1
explorer
Member
 
Registered: Feb 2003
Posts: 229

Rep: Reputation: 34
Angry Network connection dies every 20 to 30 hours


Installed mdk 9 on a Pentium 200 mhz machine. Network card detected during install and woked fine on first boot. It's goint to be used as a company intranet server so it will need to run 24 x 7 x 365. After the install, the network connection died the following day. As soon as I rebooted it started working again, then died about a day and a half later again. Rebooting always gets the network going but it always dies after 20 to 30 hours. My network card is a 3com 3c905B-TX. There are no power management options enabled in the bios. I replaced the card with another one - same kind, still have same problem. Is there a problem with these 3com cards or should I look elsewhere ?
Any pci card recommendations ?

Thanks
 
Old 03-29-2003, 09:07 AM   #2
Crashed_Again
Senior Member
 
Registered: Dec 2002
Location: Atlantic City, NJ
Distribution: Ubuntu & Arch
Posts: 3,503

Rep: Reputation: 57
Its probably not your card. I would check the log files to see what is causing this.
 
Old 03-29-2003, 09:56 AM   #3
rnturn
Member
 
Registered: Jan 2003
Location: Illinois (Chicago area)
Distribution: Red Hat (8.0), SuSE (10.x, 11.x, 12.2), Solaris (8-10), Tru64
Posts: 889

Rep: Reputation: 45
Re: Network connection dies every 20 to 30 hours

Quote:
Originally posted by explorer
... It's goint to be used as a company intranet server so it will need to run 24 x 7 x 365. After the install, the network connection died the following day. As soon as I rebooted it started working again, then died about a day and a half later again. Rebooting always gets the network going but it always dies after 20 to 30 hours. ...
If this is in an office environment, see if there's any correlation to when the cleaning crew comes in. Perhaps they're unplugging something so they can vacuum. Perhaps a hub that your machine is plugged into and the power cycle causes the card to latch up. Stranger things have happened. (Years ago, we used to leave the PCs in our offices on all night. Some of us were running long simulations, etc., and many times we'd come in next morning to find that the systems had rebooted. Turns out that the cleaning crew had been told to turn off half the hallway lights, and since they were unable to find the right breaker in the panel, they'd randomly flip them until they got the right one, whacking the power in many of the offices in the process. Until we figured out what was going on and labeled the breakers for them. :-) )
 
Old 03-29-2003, 10:06 PM   #4
tcaptain
LQ Addict
 
Registered: Jul 2002
Location: Montreal
Distribution: Gentoo 2004 from stage 1 baby!
Posts: 1,403

Rep: Reputation: 45
also, if its a cable modem, your ISP is probably using DHCP, which means that your lease might be up at that time.

For me, every 2 weeks or so, my connection goes dead because my ISP switches IPs on my modem...so I have to do a /etc/init.d/network restart and all is fine again.
 
Old 03-29-2003, 11:34 PM   #5
explorer
Member
 
Registered: Feb 2003
Posts: 229

Original Poster
Rep: Reputation: 34
Arrow

I'm not sure which log files to check or exactly what to look for, but the ones I found showed nothing unusual. It is an office environment but it's not the cleaning crews. The machine is currently running in my office and it will be working fine when I come in in the morning then later in the day with no one there but me it will die, or it may run all day and die the next day at noon. I have seen the cleaning crews do some nasty power offs on computer equipment in the past though - good thing to consider. I't inhouse so there's no external isp involved. I was originally using dhcp to get it's address and suspected something was up with dhcp address lease renewals so I changed that and gave it a static IP and still have the problem.
 
Old 03-29-2003, 11:44 PM   #6
explorer
Member
 
Registered: Feb 2003
Posts: 229

Original Poster
Rep: Reputation: 34
I noticed one thing today though. I took the cover off to see if it had any ISA slots on the board or not. I was considering trying an ISA network card. While I had the cover I noticed the PCI Video card was barely seated in the slot. I shut it down and pulled the video card out so I could see if the network card was also not fully seated, and what I saw was the the network card was farther out of the PCI slot than the video card was - some of the pins must have been barely making contact. Since the mainboard fits in the case kind of funky, I had bend the case a little to make the video card seat right, and I had to move the network card to another PCI slot. This might possibly have been the problem all along but I won't know for sure until I try it this coming week. I'll keep you posted.....
 
Old 04-02-2003, 08:45 AM   #7
explorer
Member
 
Registered: Feb 2003
Posts: 229

Original Poster
Rep: Reputation: 34
Nope that wasn't the problem. The connection to it died about 7 oclock this morning. This time, powering down the hub for a minute and powering it back up made the conneciton live again without having to reboot. I have 2 other computers on the same hub and the network was still good on both of them ( w2k boxes ) only the mdk connections dropped.
 
Old 04-02-2003, 09:07 AM   #8
twan
Member
 
Registered: Feb 2003
Location: Brasschaat, Antwerpen - Belgium
Distribution: Gentoo
Posts: 52

Rep: Reputation: 15
maybe you have to change to log out time

i had a problem with this with my internet connection
 
Old 04-02-2003, 10:49 AM   #9
explorer
Member
 
Registered: Feb 2003
Posts: 229

Original Poster
Rep: Reputation: 34
How ? - tnx....
 
Old 04-02-2003, 11:39 AM   #10
explorer
Member
 
Registered: Feb 2003
Posts: 229

Original Poster
Rep: Reputation: 34
I found this in my /var/log/messages file. I don't understand everything in the file, but it looks like the server became a master browser for the workgroup at about 10:15, and about 9 minutes later started getting eth0 timeout message which continued every 10 seconds until I reset the hub this morning....I wonder if this is just coincidence or if something happenned when it became a master browser ....

---------------------------------------------------------------

Apr 1 10:15:00 cinizaweb CROND[9073]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:15:00 cinizaweb CROND[9074]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/gate_news)
Apr 1 10:15:08 cinizaweb nmbd[1894]: [2003/04/01 10:15:08, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404)
Apr 1 10:15:08 cinizaweb nmbd[1894]: *****
Apr 1 10:15:08 cinizaweb nmbd[1894]:
Apr 1 10:15:08 cinizaweb nmbd[1894]: Samba name server CINIZAWEB is now a local master browser for workgroup WTCIN on subnet 10.113.32.240
Apr 1 10:15:08 cinizaweb nmbd[1894]:
Apr 1 10:15:08 cinizaweb nmbd[1894]: *****
Apr 1 10:16:00 cinizaweb CROND[9076]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:17:00 cinizaweb CROND[9078]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:17:59 cinizaweb CROND[9080]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:19:00 cinizaweb CROND[9082]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:20:00 cinizaweb CROND[9085]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:20:00 cinizaweb CROND[9086]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/gate_news)
Apr 1 10:21:00 cinizaweb CROND[9088]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:22:00 cinizaweb CROND[9090]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:23:00 cinizaweb CROND[9092]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:24:00 cinizaweb CROND[9094]: (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
Apr 1 10:24:27 cinizaweb kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 1 10:24:27 cinizaweb kernel: eth0: transmit timed out, tx_status 00 status e000.
Apr 1 10:24:27 cinizaweb kernel: diagnostics: net 0ed2 media 88a0 dma 000000a0.
Apr 1 10:24:27 cinizaweb kernel: Flags; bus-master 1, dirty 15260(12) current 15276(12)
Apr 1 10:24:27 cinizaweb kernel: Transmit list 03b77500 vs. c3b77500.
Apr 1 10:24:27 cinizaweb kernel: 0: @c3b77200 length 8000006e status 0000006e
Apr 1 10:24:27 cinizaweb kernel: 1: @c3b77240 length 8000006e status 0000006e
Apr 1 10:24:27 cinizaweb kernel: 2: @c3b77280 length 800000de status 000000de
Apr 1 10:24:27 cinizaweb kernel: 3: @c3b772c0 length 80000106 status 00000106
Apr 1 10:24:27 cinizaweb kernel: 4: @c3b77300 length 800000fc status 000000fc
Apr 1 10:24:27 cinizaweb kernel: 5: @c3b77340 length 80000066 status 00000066
Apr 1 10:24:27 cinizaweb kernel: 6: @c3b77380 length 80000106 status 00000106
Apr 1 10:24:27 cinizaweb kernel: 7: @c3b773c0 length 800000fc status 000000fc
Apr 1 10:24:27 cinizaweb kernel: 8: @c3b77400 length 80000066 status 00000066
Apr 1 10:24:27 cinizaweb kernel: 9: @c3b77440 length 80000066 status 00000066
Apr 1 10:24:27 cinizaweb kernel: 10: @c3b77480 length 80000106 status 80000106
Apr 1 10:24:27 cinizaweb kernel: 11: @c3b774c0 length 800000fc status 800000fc
Apr 1 10:24:27 cinizaweb kernel: 12: @c3b77500 length 8000006e status 0000006e
Apr 1 10:24:27 cinizaweb kernel: 13: @c3b77540 length 8000006e status 0000006e
Apr 1 10:24:27 cinizaweb kernel: 14: @c3b77580 length 8000006e status 0000006e
Apr 1 10:24:27 cinizaweb kernel: 15: @c3b775c0 length 8000006e status 0000006e
Apr 1 10:24:37 cinizaweb kernel: NETDEV WATCHDOG: eth0: transmit timed out
Apr 1 10:24:37 cinizaweb kernel: eth0: transmit timed out, tx_status 00 status e000.
Apr 1 10:24:37 cinizaweb kernel: diagnostics: net 0ed2 media 88a0 dma 000000a0.
Apr 1 10:24:37 cinizaweb kernel: Flags; bus-master 1, dirty 15260(12) current 15276(12)
Apr 1 10:24:37 cinizaweb kernel: Transmit list 03b773c0 vs. c3b77500.

-----------------------------------------------
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Internet Connection Dies after Reboot kasra_23 Linux - Software 2 03-12-2005 10:51 PM
ISDN connection dies phil81 Debian 0 01-05-2005 03:57 AM
internet connection dies dsharples Linux - Networking 1 08-27-2004 04:27 PM
ADSL connection falls every 24 hours exactly jmcollin92 Linux - Networking 3 02-29-2004 08:16 PM
PPP Daemon dies on connection, but no when I'm in root Manyguns Linux - Newbie 1 05-27-2001 09:21 AM


All times are GMT -5. The time now is 09:09 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration