job queue runs full after upgrade to v4.1.0

[lanbrown]

tried it, but

this command through putty:
wget -qO - https://storage.z-wave.me/z-way-server/ ... _armhf.deb | sudo bash

returns theese errors
bash: line 1: syntax error at "newline", which is an unexpected symbol
bash: line 1: `!<arch>'

have tried typing the command letter by letter, but the samme error is returned
what's wrong?

Then try this:
wget - https://storage.z-wave.me/z-way-server/ ... _armhf.deb
sudo dpkg -i z-way-4.0.3_armhf.deb

[otverber]

@otverber Your queue looks ok - 22 sent packets - nothing wrong here. But If you still think there is an issue, please send us the log on support -mail (with a link to this thread).

The problem others are experiencing is a different one. Could someone with this issue help us by providing remote access to chase the issue? We are still unable to reproduce it ;(

hello
where do I find the support-mail adress?

The Z-way log file is very large, the job queue list isn't that large will try to capture both lists for you. I suspect a flood at midnight..

[PoltoS]

support@z-wave.me

Please purge the log before starting and do

Code: Select all

sudo killall z-way-server -HUP

to let it rotate the log

[PoltoS]

Hello @hubert, @otverber, @AlesKO, @JohannesF, @J.nissen

Since we can't catch it for a few weeks, we made a new build where we enabled additional queue inspection on the http://localhost:8083/expert/#/network/queue page. Please install the new v4.1.0-22-g964ba9d9 (https://storage.z-wave.me/z-way-server/ ... _armhf.deb) and once the issue happens again (jobs are stuck in the queue and nothing is sent out), please provide the log file and the queue inspector (better as a page save to .html [Ctrl + S] rather than a screenshot). Hope it will allow us to track it down.

Thank you in advance for your help in improving Z-Way!

[hubert]

Thanks @PoltoS, I have installed the new build and will send info next time it happens

On the most recent hang that happened, according to /expert/#/device/status a Fibaro Dimmer 2 device was the last to be updated before the queue hung

[otverber]

Hello @hubert, @otverber, @AlesKO, @JohannesF, @J.nissen

Since we can't catch it for a few weeks, we made a new build where we enabled additional queue inspection on the http://localhost:8083/expert/#/network/queue page. Please install the new v4.1.0-22-g964ba9d9 (https://storage.z-wave.me/z-way-server/ ... _armhf.deb) and once the issue happens again (jobs are stuck in the queue and nothing is sent out), please provide the log file and the queue inspector (better as a page save to .html [Ctrl + S] rather than a screenshot). Hope it will allow us to track it down.

Thank you in advance for your help in improving Z-Way!

hello
please indicate how to install the new update;
which commands trough ssh should i use?

[RandomTask]

Use this command to install this version of the z-way package. You can replace the contents of PKG= with another version

Code: Select all

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

[otverber]

Hello @hubert, @otverber, @AlesKO, @JohannesF, @J.nissen

Since we can't catch it for a few weeks, we made a new build where we enabled additional queue inspection on the http://localhost:8083/expert/#/network/queue page. Please install the new v4.1.0-22-g964ba9d9 (https://storage.z-wave.me/z-way-server/ ... _armhf.deb) and once the issue happens again (jobs are stuck in the queue and nothing is sent out), please provide the log file and the queue inspector (better as a page save to .html [Ctrl + S] rather than a screenshot). Hope it will allow us to track it down.

Thank you in advance for your help in improving Z-Way!

Use this command to install this version of the z-way package. You can replace the contents of PKG= with another version

Code: Select all

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

thanks a lot, it worked!

[otverber]

Thanks @PoltoS, I have installed the new build and will send info next time it happens

On the most recent hang that happened, according to /expert/#/device/status a Fibaro Dimmer 2 device was the last to be updated before the queue hung

I just reincluded a Fibaro dimmer 2(#75>#202), and the Z-Wave version vent from 4.24 to 6.51 in (zz):8083/expert/#/device/type
I have a FIBARO Single Switch 2 (#82) that are still on 4.24; will try exclude and include tomorrow.

[hubert]

Thanks @PoltoS, I have installed the new build and will send info next time it happens

On the most recent hang that happened, according to /expert/#/device/status a Fibaro Dimmer 2 device was the last to be updated before the queue hung

I just reincluded a Fibaro dimmer 2(#75>#202), and the Z-Wave version vent from 4.24 to 6.51 in (zz):8083/expert/#/device/type
I have a FIBARO Single Switch 2 (#82) that are still on 4.24; will try exclude and include tomorrow.

Z-Wave Version is showing 6.51.06 for me on my Fibaro Dimmer 2, not sure if this has changed recently

Device firmware version 3.04, as far as I know it's not possible to update this through Razberry/Z-Way.

All of my devices (Fibaro, Aeotec, Goap) are on Z-Wave version 6.51.06 except 1 Remotec thermostat which is on 4.54.01