Crashing every few hours

6 posts / 0 new
Last post
Saidin
Saidin's picture
Crashing every few hours

I posted this in the discussion for the latest build, 23430, but thought I might have a better chance of a response in the main forums. So I apologize for a double post.

 

I've been having an issue where my router (using the latest build of dd-wrt) will crash and restart every few hours. This is the 2nd router that has had the issue (I returned the previous one yesterday for a new one thinking it was a hardware issu), so I believe it is firmware related. 

Anyone else having this issue? Any suggestions on what I could try to resolve the problem or pointers on what to check for a problem? This is my first experience using dd-wrt, so I'm sure there are things I can check that I just don't know about yet.

I have turned on logging, and have seen a bunch of messages like the following, but I'm not sure if this is actually an issue or not, or how to correct it:

2014-02-11 09:59:15 Daemon.Error 192.168.1.99 Jan  1 03:35:53 watchquagga[992]: Forked background command [pid 4903]: zebra -d

2014-02-11 09:59:15 Daemon.Warning 192.168.1.99 Jan  1 03:35:53 watchquagga[992]: restart zebra process 4903 exited with non-zero status1

2014-02-11 10:09:16 Daemon.Error 192.168.1.99 Jan  1 03:45:54 watchquagga[992]: Forked background command [pid 5063]: zebra -d

2014-02-11 10:09:16 Daemon.Warning 192.168.1.99 Jan  1 03:45:54 watchquagga[992]: restart zebra process 5063 exited with non-zero status 1

2014-02-11 10:19:17 Daemon.Error 192.168.1.99 Jan  1 03:55:55 watchquagga[992]: Forked background command [pid 5224]: zebra -d

2014-02-11 10:19:17 Daemon.Warning 192.168.1.99 Jan  1 03:55:55 watchquagga[992]: restart zebra process 5224 exited with non-zero status 1

 

The next messages logged appears to be the router starting back up:

2014-02-11 10:24:18 Kernel.Notice 192.168.1.99 Jan  1 00:00:03 kernel: klogd started: BusyBox v1.22.1 (2014-01-27 21:05:34 CET)

2014-02-11 10:24:18 Kernel.Info 192.168.1.99 Jan  1 00:00:03 kernel: Booting Linux on physical CPU 0x0

Accid
Accid's picture
Do you have the router in an

Do you have the router in an AC environment or non AC? Maybe its is your environment or your power source. These devices are made to run in a bit of heat but to much heat will cause damage and hinder there normal operations.

Try the router on a UPS with only the network cables plugged in, see if it still gives the same problem,.

Putting an external fan on the Router will help to reduce the heat, to the side where the vents are. I have used an 4 inch 110v fan, my CPU temperature is down to 61 degrees c from 71.

DO a 30/30/30 reset and upgrade to the latest update r23550 07-Feb-2014 17:59
Follow the DDWRT flash instructions carefully.

Saidin
Saidin's picture
Thank you for the reply and

Thank you for the reply and suggestions. The router is running in my apartment, with a thermostat set at 74F. I believe it has plenty of breathing room around the router, but I'll check to see if there is anything I can do to improve it. Here are the temps that are currently displayed under the Status screen:
CPU 57.5 °C / WL0 44.70 °C / WL1 46.50 °C

I'll give the reset and update a try also. Where can I find the r23550 build? When I go to http://www.myopenrouter.com/download/list?cat=95 the newest download I see was uploaded on 1/27/2014.

Also, where can I find the specific DDWRT flash instructions that I should use? When I originally installed DDWRT I just went into the upgrade firmware section and selected the ddwrt file.

Thanks for the assistance.

Accid
Accid's picture
GO tohttp://www.desipro.de

GO to
http://www.desipro.de/ddwrt/
then
K3-AC-Arm/
the temperature is ok check your power source now.

Saidin
Saidin's picture
After performing the 30/30/30

After performing the 30/30/30 reset, my router has been up for about 19.5 hours. Prior to the reset, it would reboot/crash every few hours. So at this point it appears that the reset has solved my issues. Thanks Accid for the assistance.

Accid
Accid's picture
Did you update the firmware

Did you update the firmware?
Please allow my to share my experience.

I had similar problems with my ASUS RT-N16 due to torrents downloads. My router would lockup after a few days after downloading torrents.
I fixed this by setting an automatic reboot every night at a time I knew all the users are asleep.

I HAVE SUCCESSFULLY LIMITED AND TO A POINT BLOCKED P2P TORRENT USING THE NETGEAR R7000.

This is a big topic on the internet and I have been trying to do it for a while.

The torrent speed has droped to 1-10k or in some instances 0

Here is the link

http://www.dd-wrt.com/wiki/index.php/Peer-to-Peer_%28P2P%29_Throttling