Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution

Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution

Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution
Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution
Sunday
Model: Deco X50-5G  
Hardware Version: V1
Firmware Version: 1.2.1 Build 20241217 RL. 63056

Hello.

 

I'm not quite sure what's happening with my X50-5G.

I've been using the 1.2.0 firmware for a while now, without a problem... Daily schedule reboot at 4am. No connection drops, nor any other problem.

But since a few days back every time the scheduled reboot happens everything goes down the drain...

The update of the firmware to the version 1.2.1 didn't help.

 

Symptoms:

No device can connect to the X50-5G, after the reboot. Its CPU Usages stays at 100%, but the values seem somewhat all over the place.

For instance the "Online Time". Yesterday at 8:20am it was reading: "9m". At 8:40am it was "17d 23h 15m".

On both occasions the CPU was at 100% and all devices, even those connected by Ethernet cable were unable to connect; as if the DHCP was not working and no device had been given its IP.

 

 

I do suspect the firmware (1.6.3 Build 241112112 Rel. 78921) of the X50 (3 pack), that was updated more recently, may be the cause that's affecting the entire system. At least the recent date of its implementation seems somewhat to check when the problems started. In the app I can see that the firmware was available on 27/12/2024.

 

After some tests; turning off all the X50 APs from the X50-5G, the problem seems to disappear. Even when the scheduled reboot happened the next day there were no problems.

 

 

I Imagine there's something going on during the 'handshake' between the X50 access points and the X50-5G, after the scheduled reboot, that crashes and overuses the CPU until not even the DHCP is working.

 

Once again, the fact that the System logs are constantly being cleared out doesn't help anyone. The moment you are able to connect to the router the logs are already gone. I do imagine the software team are worried about the memory used by the logs (the LTE/NSA/SA services really do create a lot of debug info), but a solution such as having the option to remotely save the logs (such as a remote network server - NAS) as many other manufactures use would be ideal.

  2      
  2      
#1
Options
4 Reply
Re:Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution
Monday

  @Osz 

Hi, Thank you very much for your feedback.

Did Deco X50(non-5G mode) work in wireless router mode or Access Point mode?

It is also suggested to install the beta firmware here for Deco X50-5G to see whether it helped:

https://community.tp-link.com/en/home/forum/topic/727392

 

After that, It is recommended to submit a support ticket via email for efficient assistance. Please include your Forum ID, community nickname, a detailed description of the issue, and the troubleshooting steps you've taken in the subject or email content.

(PS: I've already started a support ticket this time. Please check whether you have received my email.)

Wait for your reply and best regards.

  0  
  0  
#2
Options
Re:Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution
Monday

Hey, David.

 

So it's okay to downgrade from the 1.2.1 Build 20241217 Rel. 63056 to the 1.2.0_build20241230_Beta?

 

The mesh system was all wired by Ethernet cable. I never had much luck using it in wireless mode.

 

  1  
  1  
#3
Options
Re:Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution
Yesterday

  @Osz 

Hi, yes, the 1.2.1 build 20241217 could be updated to 1.2.0 build 20241230 directly.

Best regards.

  0  
  0  
#4
Options
Re:Deco X50-5G - Has become unusable after reboot (CPU: 100% / DHCP: Not working) - Possible solution
Yesterday

So, I tried the Beta 1.2.0 firmware and reconnected the Mesh System.

 

Had no problem after the scheduled reboot at 4am:

 

Will see how things go the next days.

  1  
  1  
#5
Options