Hi Armen,
first at all there is no support for older release, you have a 5 years
old version. Developmen can be done on the current release.
Mongoose was update several times in between. The log just says that the
Websocket communication to some underlying devices is not working. The
master (device running the swuforward handler) then waits for packets.
It is expected that, if the connection could be established, devices
will send the result. Here it seems it is not the case, I cannot say the
reason, and no, this does not happen. It should be analyzed on your
environment what is really happening.
Best regards,
Stefano Babic
> After this, parent swupdate process is stuck in waiting.
> On Friday, July 19, 2024 at 9:32:30 AM UTC-5 Armen wrote:
>
> I have 4 subsystems that I am trying to update using SWUFORWARD
> (with swupdate 2019.11).
> I am facing a problem where subsystem never returns after swupdate
> is completed. Parent system gets stuck waiting and doesn't go to the
> next subsystem (I have 4 image sections for each subsystem to do
> update 1 by 1).
>
> swuforward has no problem connecting or sending the file. At least
> one system always gets updated. It can get stuck either on 1st or
> 2nd subsystem - this is random. But main problem is that last
> subsystem never return done. It will show "SUCCESS !" from
> swupdate-progress but never update parent swupdate process that it
> is completed.
>
> Is it a know problem and how do I resolve it?
>
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
swupdate+u...@googlegroups.com
> <mailto:
swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/swupdate/dea6381c-701d-437b-a3fd-6d34e02d7a6an%40googlegroups.com <
https://groups.google.com/d/msgid/swupdate/dea6381c-701d-437b-a3fd-6d34e02d7a6an%40googlegroups.com?utm_medium=email&utm_source=footer>.