Balance 305 fw. 8.3.0 rebooting almost at the turn of the hour

Product Discussion
1

Hello,

Today my Balance 305, with four Wans’ and a Fusion Hub connection, started rebooting about every half hour.
It’s not the fusion hub rebooting, it’s the actual router, it did it in front of me, I saw it on the display and heard the click of the relay.
It did not do it until yesterday, and the only thing I did today was to play with the outbound policy, what device connect to what wan/fusion hub.
It’s also behind an UPS.

This is a serious production issue, what could it be? This is a piece of a recent log:

Jul 19 20:42:33 Admin: admin (192.168.1.29) login successful
Jul 19 20:36:18 System: Time synchronization successful (ntp1.inrim.it)
Jul 19 20:35:28 DDNS: Domain barropuladsl.dyndns.org updated successfully for WAN 3 - ADSL
Jul 19 20:35:24 DDNS: Domain barropulaeolo.dyndns.org updated successfully for WAN 1 - EOLO
Jul 19 20:35:22 WAN: WAN 2 - STARLINK (Priority 1) connected (100.77.174.30)
Jul 19 20:35:20 DDNS: Domain barropuladsl.dyndns.org updated successfully for WAN 3 - ADSL
Jul 19 20:35:19 System: Time synchronization successful (InControl)
Jul 19 20:35:16 WAN: WAN 3 - ADSL (Priority 1) connected (192.168.10.2)
Jul 19 20:35:14 DDNS: Domain barropulaeolo.dyndns.org updated successfully for WAN 1 - EOLO
Jul 19 20:35:13 WAN: WAN 1 - EOLO (Priority 1) connected (192.168.20.3)
Jul 19 20:34:52 System: Started up (8.3.0 build 5200)
Jul 19 20:25:18 System: Started up (8.3.0 build 5200)
Jul 19 20:10:19 System: Started up (8.3.0 build 5200)
Jul 19 19:55:45 System: Started up (8.3.0 build 5200)
Jul 19 19:01:18 System: Time synchronization successful (ntp1.inrim.it)
Jul 19 19:00:47 DDNS: Domain barropuladsl.dyndns.org updated successfully for WAN 3 - ADSL
Jul 19 19:00:45 DDNS: Domain barropulaeolo.dyndns.org updated successfully for WAN 1 - EOLO
Jul 19 19:00:44 Admin: admin (192.168.1.29) login successful
Jul 19 19:00:42 WAN: WAN 2 - STARLINK (Priority 1) connected (100.77.174.30)
Jul 19 19:00:39 DDNS: Domain barropuladsl.dyndns.org updated successfully for WAN 3 - ADSL
Jul 19 19:00:39 System: Time synchronization successful (InControl)
Jul 19 19:00:35 WAN: WAN 3 - ADSL (Priority 1) connected (192.168.10.2)
Jul 19 19:00:33 DDNS: Domain barropulaeolo.dyndns.org connection timeout for WAN 1 - EOLO.
Jul 19 19:00:32 WAN: WAN 1 - EOLO (Priority 1) connected (192.168.20.3)
Jul 19 19:00:12 System: Started up (8.3.0 build 5200)
Jul 19 18:06:55 System: Time synchronization successful (ntp1.inrim.it)
Jul 19 18:06:25 DDNS: Domain barropuladsl.dyndns.org updated successfully for WAN 3 - ADSL
Jul 19 18:06:21 DDNS: Domain barropulaeolo.dyndns.org updated successfully for WAN 1 - EOLO
Jul 19 18:06:20 WAN: WAN 2 - STARLINK (Priority 1) connected (100.77.174.30)
Jul 19 18:06:16 DDNS: Domain barropuladsl.dyndns.org updated successfully for WAN 3 - ADSL
Jul 19 18:06:14 WAN: WAN 3 - ADSL (Priority 1) connected (192.168.10.2)
Jul 19 18:06:11 DDNS: Domain barropulaeolo.dyndns.org updated successfully for WAN 1 - EOLO
Jul 19 18:06:11 System: Time synchronization successful (InControl)
Jul 19 18:06:09 WAN: WAN 1 - EOLO (Priority 1) connected (192.168.20.3)
Jul 19 18:05:49 System: Started up (8.3.0 build 5200)

2

Since my posting, dozens of reboots, basically every 5-10 minutes.

Fan is running at 4750rpm and temp is 59.5C / 139F

Could it be hardware? Is there a more detail log I can pull?

3

If you are certain your power is OK (particularly, no low-V sags) and your Peplink Partner cannot help you I’d recommend submitting a ticket with Peplink. Attach a diagnostic report and turn on RA.

And, while it is operating and happy download a current config file as a precaution.

  • Rick
4

How do I generate a diagnostic report and turn RA ?

5

The router’s status page has both links.

:slight_smile:

7

Created ticket 23070703, RA is enabled and uploaded diagnostic report.

8

OK, I see @C_Metz answered you – good. Please let us know what is found on this; I’m curious.

9

So for now, this is where I stand: I connected it directly to the wall outlet, to write off possible UPS issues.
With only the three RJ-45 LAN’s connected, it hasn’t rebooted in two separate test sessions 36-48h long.
When I connect the fourth WAN, which has to be via USB and TP-Link UE306 adapter, it does reboot about once every few hours.
Mind that the TP-Link UE306 worked flawlessly without any reboot ever for more than one year.
The jury is still open, testing now a longer stretch without TP-Link UE306 , so far no reboots in 48h…

10

Do you have an answer to your support ticket yet?

11

Hi All,

I find the cause of the reboot with 100% certainty, as an incompatibility with my RJ-45 Adapter plugged in one of the USB ports.
Back in 2021, a few models of RJ to USB adapters were recommended and tested, including Tp-Link UE306, of which I bought two back then. I used one seamlessly until last month when these reboots started.

When these reboots started, in order I did:

  • bypassed the UPS: reboots still happening
  • unplugged everything except power cord: no reboots in 2 days
  • ruled out overheating issues: unit is well cooled and ventilated
  • plugged back RJ45 WAN’s one by one, one every day: no reboots yet
  • plugged back the TP-Link UE306 for WAN4: random reboots started again!
  • switched USB ports: still reboots
  • unplugged TP-Link: no reboots anymore
  • tried a second TP-LINK UE306: reboots start again
  • tried an UGreen ‎50922 : no reboots in one week https://www.amazon.it/gp/product/B07M91X2NW/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
  • put back one of the TP-Link : reboot in 5 minutes.

At this point it’s certain: both TP-Link UE306 make my Balance 305, fw 8.3.0, reboot randomly. As I find extremely unlikely that both TP-Link’s are defective, I can only conclude that there is an incompatibility of some sort with the new fw and at least my Balance 305 that makes it reboot. Mind that support could not find anything suspicious in the diagnostic log, only “reboots as if you were unplugging it and plugging it back”.

This was the solution for me, in case it may help anyone else.

Thanks!

3 Likes