job queue runs full after upgrade to v4.1.0

[johanneslarsson]

Replaced 4.1.0-27-g589c9812-lws16 with the fresh 4.1.1.

Code: Select all

PKG=z-way-4.1.1-lws16_armhf.deb && wget -O /tmp/$PKG https://storage.z-wave.me/z-way-server/$PKG && sudo dpkg -i /tmp/$PKG

Lets see if this version has fixed it for me.

Release notes, https://github.com/Z-Wave-Me/home-autom ... 72023-v411

[J.nissen]

Hello,
system hangs after few day´s.

2023-07-21 10_02_39-Z-Wave Expert UI – Mozilla Firefox.png (53.13 KiB) Viewed 22551 times

Is seems it was Device ID 64

2023-07-21 10_08_05-Z-Wave Expert UI – Mozilla Firefox.png (71.13 KiB) Viewed 22551 times

[micky1500]

For diagnostic purposes.
I have FGS-222
Working without any issues.

[PoltoS]

@J.nissen

If it is possible to provide us Expert UI access, we will look into it.

Please install the v4.1.1

[RolfKunkel]

It seems everybody in this forum is a Linux expert able to install releases via command line. I am not a Linux expert but I suffer as well from this bug. Need to restart my system almost two times per day. It would be realy great if v4.1.1 could be made available soon via the firmwareupdate menu so that less experienced users can get as well access to this more stable release.

[J.nissen]

Hello,
I have 4.1.1 Instaled . Same issue Daily …

For Remote Access i will send you credentials ..
Thanks

[johanneslarsson]

It seems everybody in this forum is a Linux expert able to install releases via command line. I am not a Linux expert but I suffer as well from this bug. Need to restart my system almost two times per day. It would be realy great if v4.1.1 could be made available soon via the firmwareupdate menu so that less experienced users can get as well access to this more stable release.

I don't think v4.1.1 has passed the internal QA round. I assume thats the reason for it not being promoted as an update option, yet.

[piet66]

V4.1.0:
Has anybody else the effect with growing cpu load?

Screenshot 2023-07-24 at 09-25-35 raspberrypi Monitoring.png (19.11 KiB) Viewed 22429 times

Code: Select all

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     11293 13.1  8.5 235000 80372 ?        Sl   Jul22 305:55 z-way-server

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     11293  0.0  8.5 235000 80372 ?        Sl   Jul22   0:05 z-way-server
root     11293  0.0  8.5 235000 80372 ?        Sl   Jul22   0:07 OptimizingCompi
root     11293  0.0  8.5 235000 80372 ?        Sl   Jul22   0:12 v8:SweeperThrea
root     11293  0.0  8.5 235000 80372 ?        Sl   Jul22   0:08 v8:SweeperThrea
root     11293  0.0  8.5 235000 80372 ?        Sl   Jul22   0:04 v8:SweeperThrea
root     11293  0.0  8.5 235000 80372 ?        Sl   Jul22   0:02 v8:SweeperThrea
root     11293  8.9  8.5 235000 80372 ?        Sl   Jul22 209:02 zway/core
root     11293  0.6  8.5 235000 80372 ?        Sl   Jul22  14:35 zway/webserver
root     11293  0.2  8.5 235000 80372 ?        Sl   Jul22   4:45 zway/timers
root     11293  3.2  8.5 235000 80372 ?        Sl   Jul22  76:06 zway/dev/ttyAMA
root     11293  0.0  8.5 235000 80372 ?        Sl   Jul22   0:17 zway/sockets

Postscript: I have no problem with the jobqueue:

Code: Select all

jobqueue:
     1	[[12.553875923156738,[1,0,0,0,1,1,1,1,1,0,0,0,0,0],0,"Get background noise level","RSSI Ch#1: -103 dBm, Ch#2: -107 dBm, Ch#3: -107 dBm",[]]]

current number of jobs in queue: 1

[seattleneil]

Yes, I see the exact same CPU growth by the z-way-server process (zway/core thread) on my 2 systems running 4.1.0. Since I haven't seen the load exceed 11%, it's not been a serious concern.

Like you, my systems have not experienced the job queue issue. Z-Way reports 100% delivery for all of my devices (as shown by expert ui Analytics->Packets). For users that have the job queue problem, I wonder whether fixing any mesh routing issues so that delivery was 100% would bypass the job queue problem.

packet stats.jpg (123.58 KiB) Viewed 22413 times

[johanneslarsson]

I think someone mentioned "battery powered device with low/empty battery" as suspect for the job queue hang in version v4.1.0.

7 days uptime with v4.1.1 now, without any issues. I'll promote it to another site to get more data.