Swupdate update issues

18 views
Skip to first unread message

Jyothi K

unread,
Jan 29, 2026, 6:10:02 AM (4 days ago) Jan 29
to swupdate

Hi all,

I am using SWUpdate version 2025.05 in a master–slave setup and I am observing an unexpected update behavior.

Setup:

  • One Master device: 192.168.1.1

  • Two Slave devices: 192.168.1.2, 192.168.1.3

Update flow:

  1. The .swu image is uploaded to the Master.

  2. The sw-description handles detection of the slave devices and triggers the update on them.

  3. SWUpdate reports a successful update on both slave devices, and both slaves reboot as expected.

  4. However, the Master device neither reboots nor applies the update, even though the logs indicate that SWUpdate completed successfully on the Master as well.

Below is the log snip
==============================================================
 swupdate[434]: [INFO ] : SWUPDATE successful ! SWUPDATE successful !
swupdate[443]: [TRACE] : SWUPDATE running :  [swupdate_web_answer] : http://192.168.1.1:8080 : SWUPDATE successful !
Line 603805:                                                                   "text": "[swupdate_web_answer] : http://192.168.1.1:8080 : SWUPDATE successful !"
 swupdate[443]: [TRACE] : SWUPDATE running :  [swupdate_web_answer] : http://192.168.1.3:8080 : SWUPDATE successful !
Line 603881:                                                                   "text": "[swupdate_web_answer] : http://192.168.1.3:8080 : SWUPDATE successful !"
swupdate[443]: [TRACE] : SWUPDATE running :  [swupdate_web_answer] : http://192.168.1.2:8080 : SWUPDATE successful !
Line 603933:                                                                   "text": "[swupdate_web_answer] : http://192.168.1.2:8080 : SWUPDATE successful !"
swupdate[443]: [INFO ] : SWUPDATE successful ! SWUPDATE successful !
Line 603966:                                                                   "text": "SWUPDATE successful !"
swupdate[443]: [TRACE] : SWUPDATE running :  [swupdate_web_answer] : http://192.168.1.3:8080 : SWUPDATE successful !
Line 623559:                                                                    "text": "[swupdate_web_answer] : http://192.168.1.3:8080 : SWUPDATE successful !"
swupdate[443]: [TRACE] : SWUPDATE running :  [swupdate_web_answer] : http://192.168.1.2:8080 : SWUPDATE successful !
Line 623627:                                                                    "text": "[swupdate_web_answer] : http://192.168.1.2:8080 : SWUPDATE successful !"
=======================================================================

Issue:

  • The update is applied correctly on the slave devices.

  • The Master reports success in the logs but does not reboot or update its image.

This behavior does not happen consistently, and I am unable to identify the exact conditions under which it occurs.

Has anyone encountered a similar issue in a master–slave SWUpdate setup, or can suggest what might cause the Master to skip reboot/update despite a successful status?

Any guidance or pointers would be appreciated.

Thanks in advance.



Reply all
Reply to author
Forward
0 new messages