job queue runs full after upgrade to v4.1.0

[hubert]

Happened again today - Screenshot of my expert GUI showing 110 jobs in queue and my z-way-server.log sent in PM to PoltoS

This seems like a software regression as it never happened before in years of running Z-Way, and I haven't added any new Z-Wave devices

[J.nissen]

Hello, same Issue on this morning...

[J.nissen]

so looks my Job Queue on this Failure....


What are an SuperVision Report ?

zwaveJobQueue.png (60.63 KiB) Viewed 8323 times

[AlesKO]

This status is after 3 days of not beeing home:



How do I send log file @PoltoS ? On PM there is no 'attach file' option.

Would someone be so kind and instruct me how to revert back to v4.0.3.

Tryed:


...but still v4.1.0

[otverber]

Similar problem wih loads of S2 items

Vendor: RaZberry by Z-Wave.Me
Vendors Product ID: 1024 / 2
Z-Wave Chip: ZW0500
Firmware
Library Type: Static Controller
SDK Version: 6.82.01
Serial API Version: 05.39

any solutions anybody?

Just a thought. Does SW0500 chip really support S2; have had some issues related to including 700 series devices.
Should I include items as unsecure as default?

[feuersee]

@AlesKO:

End of Post https://forum.z-wave.me/viewtopic.php?p=98216#p98216

Greetings Stephan

[RolfKunkel]

I do not have the knowhow to create such a cron Job and User harre provided already a log file. I have not seen a response yet from support Team that more is needed.

[AlesKO]

My Qubino 3 Phase smart meter:

2023-06-16 172811.jpg (324.88 KiB) Viewed 8269 times

Will exclude 3 Phase smart meter.

[AlesKO]

And end of Jobs queue. All my devices are unaccessible:

2023-06-16 173340.jpg (195.97 KiB) Viewed 8269 times

[seattleneil]

Although I haven't experienced the job queue problem (yet), the severity of the bug seems critical based on the number of users on this forum who have reported the problem and the only recourse being a restart of the z-way-server process. Excluding the node associated with a lot of queued jobs may be useful after the z-way-server process has been restarted.

Since this bug looks to be intermittent, I'm guessing it's going to be difficult/time-consuming for the developers to track down and resolve. Hopefully, @PoltoS will provide their customers with a status update on the bug.

For users who are experiencing the problem, perhaps the best course of action is to roll back to version 4.0.3 until a bug fix is provided. I haven't tested the roll back command, but the following command should work in theory:

Code: Select all

export BUILD=4.0.3-lws16; cd /tmp/ && wget https://storage.z-wave.me/z-way-server/z-way-4.0.3-lws16_armhf.deb && sudo dpkg -i z-way-${BUILD}_armhf.deb