job queue runs full after upgrade to v4.1.0

[PoltoS]

No, it is in the C code, not in JS. But changes are very small and we need a way to reproduce it or understand how it happened. So please provide us with more info.

[johanneslarsson]

Ok, is the c code also open source and available on github?

I'll try to compare the logs from 4.0.3 vs 4.1.0 later.

[PoltoS]

No need to compare logs. Please reproduce the queue stuck and send us the extended queue inspector page in the debug v4.1.0-23 together with the log

[johanneslarsson]

Reverting to 4.0.3 works like charm. But here we go, installed the version you mentioned. Anything else I need to get the debug enabled?

Code: Select all

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

[PoltoS]

You can check the Inspect Queue in the Expert UI - it should contain many columns (you might need to clear the browser cache). This is what we will need (together with the log) once it hangs.

[johanneslarsson]

Soon 24h without hanging. We just have to wait or is there any differences in this 4.1.0-23 version?

[PoltoS]

The only difference is that queue inspector shows more fields. No changes in the queue handling. So we need to wait.

Thanks for your help!

[thomas@unverzagt.org]

Hi.

Same Problem here.

It seems to me that one single device w/o responding can block the JQ.
E.g. a battery device which ran low or a device which was sent a GET but which has long way to go to its next wakeup.

BR
Thomas

[PoltoS]

@thomas@unverzagt.org please provide your log file and the queue inspector view (screenshot or better save the html page) (click on Jobs on the top of expert UI)

[PoltoS]

If someone with the issue can provide remote access during such hang, would be perfect