Problems with RVS4000

Unanswered Question
May 25th, 2010

Heya,

Lets cut to the chase, I got some problems with the RVS4000. Once in a while, I'd say every other day the past week or two, it's been dying at night. If I'm connected when it "dies" I'm still able to use the Internet, but if I disconnect one computer and then connect it again it won't work.

I'm still able to ping to the router when it dies, as seen here:

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Windows\system32>

I'm unable to access the webgui though, IE says that it can't display the web page and Firefox says  that the connection was reset.

If I manually reset the router by removing the power cable and then inserting it again, it will work as soon as it boots up. Usually it doesn't say anything in the log, but  just a moment  ago I found this:

May 24 23:34:13 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 24 23:34:13 - VM: killing process sh
May 24 23:42:01 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 24 23:42:01 - VM: killing process iptables

which seems interesting. I googled on the alloc pages errors and from what I understand it's an error message you get when linux runs out of memory, which then explains the VM: killing process sh and VM: killing process iptables.

So, I'm just guessing here, but is it possible that the router runs out of memory and then shutdown the process required to enter the webgui for example? If that's the case, how do I stop the router from running out of memory? Is there an hardware failure casing it to leak memory?

Before this it was running stable for at least 6 months.

I might also mention that I have updated to the latest firmware, that didn't help, I got a new improved GUI though, heh.

Also, found something else, I were in the GUI earlier, before it died, and then after it died I updated the page and I got this error:

500 Internal Error

Something unexpected went wrong running a CGI program.

I attacted a printscreen of that error as well.

So, do any of you guys got an idea on what's happening, and if there's anything I can do. I apprecative any reply.. =)

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Johan,

If you want to use this as a learning experiance and figure out this problem yourself, then the following maybe for you:

In all of your communications. I hear you saying your RVS-4000 freezes and will not communicate. No in or out of data. Is that correct?

You are also saying, these freezes occur at various times. Correct?

Which I hope this means is that it is working until it stops working...

If that is correct. Then you need to figure out if the problem is coming in over your WAN connection or it's the hardware of the Router itself.

If you think it's the hardware of the Router. Then do things like measure the temperatures of the Router. (Carefully, Try to heat it or cool it to see if this makes it fail, quicker...) Check the Voltage to this Router and make sure it's correct and you are not getting blackouts or brownouts, etc... Also check for lose data connectors.  Watch the lights on the front panel while doing the above.

However, If you think this is from a incoming data problem. Then you can place a HUB between your Router and the Cable/DSL Modem and the Router. Next plug in a PC into the same HUB and run Network Software Monitoring on this PC in Continues Record mode. Until a failure. Then go thru the Data and see what you find.

There are a few free Network Software Monitoring Tools you can find and download. Even Microsoft has a nice one for free. Microsoft Network Monitor 3.3 http://www.microsoft.com/downloads/details.aspx?familyid=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en

You can also buy another Router. And if you have the same kind of problems. Then it just might be coming in over your connection. And the new Router can then be returned as its still new.

If it is a incoming data problem: You can call Cisco and or your local ISP and work with them on this problem.

These are just a few Ideas... I'm sure others will have even more.

Beemabc123 Tue, 06/01/2010 - 03:37
you saying your RVS-4000 freezes and will not communicate. No in or out of data. Is that correct?

Yea, I guess you could say that. When it dies I'm still able to ping other computers on the LAN, but I'm not able to connect to any IP outside my local network. However, if I do a Static IP Mapping on one of the computers, that computer can often use the internet even though the router feezes. It will work until that computer has been rebooted.

Though the problem with accessing the Routers GUI once it dies varies. Last night I was able to access it, but some options were missing, for example I could't see any System Information, like Port Statistics, Network Setting Status etc.

I was able to access the log though, and this is what I could grab


All Log 
Type:   ALL System Log Access Log Firewall Log VPN Log    
May 30 15:25:21 - Configuration changed!
May 30 15:25:25 - ipsec0: no IPv6 routers present
May 30 15:25:36 - [VPN Log]: shutting down
May 30 15:25:36 - IPSEC EVENT: KLIPS device ipsec0 shut down.
May 30 15:25:39 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID [email protected])
May 30 15:25:39 - [VPN Log]: @(#) built on Aug 18 2009:19:15:55:
May 30 15:25:39 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
May 30 15:25:39 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
May 30 15:25:39 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
May 30 15:25:39 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
May 30 15:25:39 - [VPN Log]: starting up 1 cryptographic helpers
May 30 15:25:39 - [VPN Log]: started helper pid=1720 (fd:5)
May 30 15:25:39 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
May 30 15:25:39 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
May 30 15:25:39 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
May 30 15:25:39 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
May 30 15:25:39 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
May 30 15:25:39 - [VPN Log]: Warning: empty directory
May 30 15:25:47 - ipsec0: no IPv6 routers present
May 31 13:25:22 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 13:25:22 - VM: killing process sh
May 31 13:41:17 - __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
May 31 13:41:17 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 13:41:17 - VM: killing process switch_app
May 31 13:55:20 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 13:55:20 - VM: killing process [
May 31 13:55:21 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 13:55:21 - VM: killing process rc
May 31 13:55:21 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 13:55:21 - VM: killing process udhcpd
May 31 14:09:00 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:09:00 - VM: killing process crond
May 31 14:09:44 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:09:44 - VM: killing process pluto
May 31 14:15:26 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:15:26 - VM: killing process upnpd
May 31 14:25:21 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:25:21 - VM: killing process sh
May 31 14:25:21 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:25:21 - VM: killing process udhcpc.script
May 31 14:39:05 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:39:05 - VM: killing process ipsd
May 31 14:39:23 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:39:23 - VM: killing process pb_ap
May 31 14:45:08 - __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
May 31 14:45:08 - VM: killing process lld2

and like the earlier log it's killing processes again.

You are also saying, these freezes occur at various times. Correct?

Yea, but most, if not all has occured late evening/night.

Then you need to figure out if the problem is coming in over your WAN connection or it's the hardware of the Router itself.

So it could be the ISP? Actually, my ISP connection died two days ago for about 2-3 hours, so they've had some trouble. The router trouble has been going on for a few weeks though, if it's the ISP, wouldn't they have sorted it by now?

Then do things like measure the temperatures of the Router.

That was actually one of my initial thoughts, and it gets quite hot, but maybe that's normal, it's on 24 hours a day.

You can also buy another Router.

Yea, and thats what I was going to do, but I found this forum and thought I'd least give it a ago before I'll buy a new one. =)

Also, the router had an uptime for about 5 days, before I rebooted it two days ago when the ISP had problems, and then it crashed last night. Sometimes it can work for like a week/a few days before it starts freezing again.

Thanks for the reply by the way.

Beemabc123 Tue, 06/01/2010 - 10:41

Johan,

It's looking like a hardware memory problem to me.

I would say at this point you should call in the Cisco Doctor for a consultation.

Depending on how old your RVS-4000 is you may have to pay and replace it with another Gateway/Router.

Sorry Buddy,

Bruce

Yea, I thought so too. Thanks for confirming. It's a shame really, it's a good router.

It's quite old, the place were I bought it from went out of business back in 2008. So I reckon it's at least 3 years now. I'll start looking for a replacement router.

Thanks for the help.

Actions

This Discussion