Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Discussions about Z-Way software and Z-Wave technology in general
Post Reply
brizz
Posts: 6
Joined: 18 Oct 2017 19:15

Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Post by brizz »

I've had this problem a while now and really hoped 3.0.0 would fix it. I've seen a few other threads of people having similar issues. Unfortunately it's actually gotten worse in 3.0.0.

The Z-Way server randomly stops for me (not sure if it's a crash, or closing - nothing in the logs, even when set to most verbose). I'd say it's happening once every two days or so - not ideal at all for a smart house where my lights/sensors suddenly stop responding to button presses/actions/etc.

In 2.3.8 I could ssh into the pi and run

Code: Select all

sudo /etc/init.d/z-way-server restart
and the server would restart and everything continue to work. However, this no long works in 3.0.0. Restarting the server seems to do nothing and I have to perform a full reboot of the pi.

For now I'm going to be rolling back to a much earlier version that doesn't seem to have this problem.

Is there any chance of investigating this issue and fixing it once and for all? I'm willing to provide anything needed to help diagnose (including an image of what's on my pi if that's any help).
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Re: Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Post by PoltoS »

Hi!

We were hunting for those bugs for many months. Most were solved, but looks we have some more.

If you can help us, we would be glad to run gdb and similar tools on your side and cooperate very close with you to locate the issue.

Unfortunately just making an image do not help in most cases - environment influence a lot.

Please contact us in PM
jet11x
Posts: 53
Joined: 29 Dec 2014 21:15

Re: Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Post by jet11x »

Since installing 3.0.0 on 10-Aug-19 it's crashed twice. I've got monit installed to re-start process automatically if it crashes after problems with an earlier version of Z-Way, so isn't too much of a problem. I did use gdb previously to find out what was causing the crash. I have two problems though with doing that again:
- my wife tends to turn of the computer with putty running ...
- no re-start if it crashes

Likely ways around this, but my knowledge of gdb is rather basic.
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Re: Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Post by PoltoS »

First problem can be solved by running "screen" and inside gdb.

If you can provide us access, we would be happy to seek for this crash issue.

But first please do gdb and make "bt" and "info thr" after it crashes.
jet11x
Posts: 53
Joined: 29 Dec 2014 21:15

Re: Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Post by jet11x »

Thanks - I'll see what I can do
garth
Posts: 1
Joined: 08 Jan 2020 01:29

Re: Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Post by garth »

Running v3.0.3 on buster with all the latest updates. Sometimes z-way-server crashes on start sometimes after some time, but it never stays up more than a few hours. There is no info in the regular log file. Here is debug output of a crash on start.

Code: Select all

(gdb) exec-file z-way-server
(gdb) run
Starting program: /opt/z-way-server/z-way-server z-way-server
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x76694de8 in ?? () from libs/libcrypto.so.1.0.0
(gdb) bt
#0  0x76694de8 in ?? () from libs/libcrypto.so.1.0.0
#1  0x766914b4 in OPENSSL_cpuid_setup () from libs/libcrypto.so.1.0.0
#2  0x76fde2e8 in call_init (l=<optimized out>, argc=argc@entry=2, argv=argv@entry=0x7efff6c4, 
    env=env@entry=0x7efff6d0) at dl-init.c:72
#3  0x76fde3ec in call_init (env=<optimized out>, argv=<optimized out>, argc=<optimized out>, 
    l=<optimized out>) at dl-init.c:30
#4  _dl_init (main_map=0x76fff978, argc=2, argv=0x7efff6c4, env=0x7efff6d0) at dl-init.c:119
#5  0x76fcea74 in _dl_start_user () from /lib/ld-linux-armhf.so.3
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) info thr
  Id   Target Id                                   Frame 
* 1    Thread 0x762c9010 (LWP 6482) "z-way-server" 0x76694de8 in ?? () from libs/libcrypto.so.1.0.0
User avatar
PoltoS
Posts: 7565
Joined: 26 Jan 2011 19:36

Re: Z-Way 2.3.8 and 3.0.0 randomly closing. Pi now has to be rebooted in 3.0.0

Post by PoltoS »

This is not a crash. It is a normal operation. If you want to run gdb, please do:

Code: Select all

cd /opt/z-way-server
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:./libs:./modules gdb ./z-way-server
handle SIGPIPE nostop
handle SIGILL nostop
handle SIGHUP nostop
run
Post Reply