NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBS960 satellite memory creep again
Just started - noticed it early this morning. As it shows, it's been up for over 3 weeks. It will be interesting to see if it stops or if it ends up restarting or losing its connection via backhaul.
Time: 06/01/2024, 10:11:26 CPU %: 5.84% Memory Usage: 446 MB/812 MB Uptime: 22 days 0:6:10 HopCount: 1
Time: 06/01/2024, 10:21:28 CPU %: 5.84% Memory Usage: 447 MB/812 MB Uptime: 22 days 0:16:12 HopCount: 1
Time: 06/01/2024, 10:31:30 CPU %: 5.84% Memory Usage: 447 MB/812 MB Uptime: 22 days 0:26:14 HopCount: 1
Time: 06/01/2024, 10:41:32 CPU %: 5.84% Memory Usage: 448 MB/812 MB Uptime: 22 days 0:36:16 HopCount: 1
Time: 06/01/2024, 10:51:34 CPU %: 5.84% Memory Usage: 449 MB/812 MB Uptime: 22 days 0:46:18 HopCount: 1
Time: 06/01/2024, 11:01:36 CPU %: 5.84% Memory Usage: 449 MB/812 MB Uptime: 22 days 0:56:20 HopCount: 1
Time: 06/01/2024, 11:11:37 CPU %: 5.84% Memory Usage: 450 MB/812 MB Uptime: 22 days 1:6:22 HopCount: 1
Time: 06/01/2024, 11:21:39 CPU %: 5.84% Memory Usage: 451 MB/812 MB Uptime: 22 days 1:16:24 HopCount: 1
Time: 06/01/2024, 11:31:41 CPU %: 5.84% Memory Usage: 451 MB/812 MB Uptime: 22 days 1:26:26 HopCount: 1
Time: 06/01/2024, 11:41:43 CPU %: 5.84% Memory Usage: 452 MB/812 MB Uptime: 22 days 1:36:28 HopCount: 1
Time: 06/01/2024, 11:51:45 CPU %: 5.83% Memory Usage: 453 MB/812 MB Uptime: 22 days 1:46:30 HopCount: 1
Time: 06/01/2024, 12:01:47 CPU %: 5.83% Memory Usage: 453 MB/812 MB Uptime: 22 days 1:56:32 HopCount: 1
Time: 06/01/2024, 12:11:49 CPU %: 5.83% Memory Usage: 454 MB/812 MB Uptime: 22 days 2:6:33 HopCount: 1
Time: 06/01/2024, 12:21:51 CPU %: 5.83% Memory Usage: 454 MB/812 MB Uptime: 22 days 2:16:35 HopCount: 1
Time: 06/01/2024, 12:31:53 CPU %: 5.83% Memory Usage: 454 MB/812 MB Uptime: 22 days 2:26:37 HopCount: 1
Time: 06/01/2024, 12:41:55 CPU %: 5.83% Memory Usage: 455 MB/812 MB Uptime: 22 days 2:36:39 HopCount: 1
31 Replies
Does the RBS exhibit the same thing or different.
Keep monitoring and see if this one RBS fails.
Wondering if you swapped RBS around if the problem would follow.
FW v.31?
Does the RBS exhibit the same thing or different. This is the RBS. The other RBS is fine.
Keep monitoring and see if this one RBS fails. - News flash! It went all day to 6:41 PM, now up to 476MB. I had to try something lol - I unplugged the Eth cable and after 2 minutes (LED was magenta - too far aw3ay for WiFi Backhaul) I plugged it back in., It's only been 20 minutes, but the memory has already dropped TWICE! 473 then 472. I'll keep watching, then if that continues update my support ticket with this failure.
Wondering if you swapped RBS around if the problem would follow.
FW v.31? It may take 22 days!
Forgot to reply to last question - yes - 7.2.6.31 FW.
The system has been stable for over 22 days with minor increases in memory usage and consistent CPU usage.
Here's my latest update on "memory creep" --
1st floor RBS is up to 604MB now; most I have ever seen is the router at around 660MB max. I am really curious to see what will happen. AND - NEW NEWS - the other RBS started creeping yesterday. It was around 388MB for a long time, now it's up to 444MB. Both will be up 24 days in a few hours!
The odd thing is the CPU on the RBSs - one is 5.8%, the other 6.2%. They are pretty idle yet memory usage grows.
Everything else is good - RBR stable CPU/mem, no disconnects or restarts, IPv6 fine, modem signals/errors etc clean.I'll post again when one or both RBSs' memory creeping is resolved - at some point they will either stabilize on their memory creep or be forced to auto restart I think!
At 3:00:13 AM EDT approximately, the RBS960 on the first floor restarted after experiencing a memory creep for days. Memory used got to 782MB. I have included a zip file (via a dropbox link) with this summary along with all the supporting files mentioned in this report. Besides the memory creep/restart problem, you'll also read that there were problems getting the RBS to come back up properly connected on backhaul.
After the 3 AM restart, memory was back in a normal range - 340MB, but Hop Count was blank at 6:30 AM when I discovered it.
Also, all devices had disconnected from RBS by morning - smart plugs, and mobile devices.
I did 2 debug captures for 5 minutes, one with LAN-WAN packet capture, and one without. They are in this zip file.
Then I powered the RBS off for 2 minutes - and then powered it on. But the router admin page showed the Backhaul status as good, but not connected to the router (see attached screen shot). Hop Count is also blank after 15 minutes (see screen shot). So I powered the RBS960 down again, waited 2 minutes, and powered it up. This time, it shows the RBS hard wire connected to the third floor RBS, instead of the Router! Hop Count is still blank. The Orbi app shows the same thing. I tried a third time - power cycling the RBS960 - Hop Count is blank and nothing connects to it. So then, I turned off the offending RBS, then powered off the 3rd floor RBS, then powered up the offending RBS. It came up perfectly immediately! So this is another problem I have seen in the past - with 2 RBSs with wired backhaul, it can be very problematic restarting/power cycling one of them.
I then powered up the RBS that was working fine on the 3rd floor - came up fine. Both RBSs now have Hop Count 1, memory is at 341MB for both.
I also included in this zip file a Txt file of the debug page for the RBS960 showing the memory creep over the last several days, scraped every 10 minutes. This shows the memory creep over the last several days.
Dropbox link if anyone is interested:
This 3AM restart, was that on it's own or did you intervene?
Wondering if you should open up another support ticket for this particular issue. đ€
No, it did it on its own - likely out of memory.
I added this info to my existing support ticket, as my original problem indicated memory creep issues among other problems. I had another support ticket open with similar issues, and they closed that one - I think they wanted this all lumped into one support ticket.
