Page 5 of 5

Re: Server is constantly crashing

Posted: 25 Apr 2018 00:02
by Spirit78
PoltoS: I can just say that I have had constant crashes at least twice a week. And have had problems with the HomeKit app after it was updated some weeks ago. I suspected that apple had to do something about it, because it crashed all within 2-3 days and somtimes after just a few hours. But suddenly it seems that maybe apple have done something in their end, and the z-way nore the HomeKit app crashes, and I have done no changes at all. And suddenly i just goes rather stable. I know have 3 restarts a week of z-way with cronjob. I will reduse it to twice and then ones a week to se if it is stable. So hopefully it can have something with HomKit/Apple/z-way that makes it crash and now apple have done some changes that affects z-way? ( I know the HK app isnt Apples own developed app ) For those who have had crashes, can there be some connection between the users, that all of them uses HK-app? My z-way server seems to be much much more stable over all know, without me having done any changes. And HK too. It all seems to been stable for a few weeks and HK also works even when I restart the server, witch it rarely have done before. Almost all the time I had to re pair the z-way with HK again. But now it seems to work great

Re: Server is constantly crashing

Posted: 25 Apr 2018 14:51
by PoltoS
Can you run it via GDB to help us hunt it?

Re: Server is constantly crashing

Posted: 25 Apr 2018 23:54
by Spirit78
Sorry, but dont know what GDB is?

Re: Server is constantly crashing

Posted: 07 May 2018 20:30
by equathza
Well I will try and keep that one in mind Spirit78. I'm planning to add a couple of new devices as changes in. If it crashes I'll try and make a GDB of the crash for PoltoS. For what I noticed renaming devices seem to make HomeKit do really weird things. In my case I've had to rebuild and make some more changes after some unpredicted Siri turn off wrong devices events. Found out renaming the devices suddenly became important for Homekit ease of use. For now the z-way works stable

Reporting back, I now have z-way running with GDB. Hope to catch this anomaly.. HomeKit first shows my devices are not responding. Z-way still running OK.. few hours later it seem to have crashed. This while I did a complete rebuild before reinstalling the HomeKit app again. I did find suggestion on reactivating my HomeKit hub on the Apple TV to fix crashing HomeKit. Guess it still needs some work

Code: Select all

pi@raspberrypi:/opt/z-way-server $ screen
Module modhttp.so loaded
Module modhomekit.so loaded
Module modws.so loaded
Module modsockets.so loaded
Module modcrypto.so loaded
Module modiconinstaller.so loaded
Using default configuration file config.xml
Error: 'debug-port' number is out of range. Skipping it.
[New Thread 0x756a8450 (LWP 7950)]
[New Thread 0x74ea8450 (LWP 7951)]
[New Thread 0x74e98450 (LWP 7952)]
[New Thread 0x74e88450 (LWP 7953)]
[New Thread 0x74e78450 (LWP 7954)]
[New Thread 0x74e68450 (LWP 7955)]
[New Thread 0x742ff450 (LWP 7958)]
[New Thread 0x73aff450 (LWP 7959)]
[New Thread 0x72eff450 (LWP 7960)]
[New Thread 0x71eff450 (LWP 7961)]
[New Thread 0x716ff450 (LWP 7962)]

Program received signal SIGPIPE, Broken pipe.

Program received signal SIGPIPE, Broken pipe.

Program received signal SIGPIPE, Broken pipe.
[Thread 0x716ff450 (LWP 7962) exited]
[Thread 0x71eff450 (LWP 7961) exited]
[New Thread 0x71eff450 (LWP 8418)]
[New Thread 0x716ff450 (LWP 8419)]
login as: pi
~~~~
~ some screen output missing
~~~~
pi@raspberrypi:~ $ attach
-bash: attach: command not found
pi@raspberrypi:~ $ screen -r
    isem=isem@entry=0x6475c) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:48
  5    Thread 0x74e88450 (LWP 7953) "v8:SweeperThrea" 0x76986a40 in do_futex_wait (
    isem=isem@entry=0x64654) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:48
  4    Thread 0x74e98450 (LWP 7952) "v8:SweeperThrea" 0x76986a40 in do_futex_wait (
    isem=isem@entry=0x6454c) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:48
  3    Thread 0x74ea8450 (LWP 7951) "v8:SweeperThrea" 0x76986a40 in do_futex_wait (
    isem=isem@entry=0x64444) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:48
  2    Thread 0x756a8450 (LWP 7950) "OptimizingCompi" 0x76986a40 in do_futex_wait (
    isem=isem@entry=0x642fc) at ../nptl/sysdeps/unix/sysv/linux/sem_wait.c:48
* 1    Thread 0x7634b000 (LWP 7949) "z-way-server" 0x76403360 in nanosleep ()
    at ../sysdeps/unix/syscall-template.S:81
(gdb) c
Continuing.

*** Error in `/opt/z-way-server/z-way-server': free(): invalid next size (fast): 0x724e1a90 ***

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x72eff450 (LWP 7960)]
0x76391f70 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)
Continuing.
[Thread 0x7634b000 (LWP 7949) exited]
[Thread 0x716ff450 (LWP 8419) exited]
[Thread 0x71eff450 (LWP 8418) exited]
[Thread 0x73aff450 (LWP 7959) exited]
[Thread 0x742ff450 (LWP 7958) exited]
[Thread 0x74e68450 (LWP 7955) exited]
[Thread 0x74e78450 (LWP 7954) exited]
[Thread 0x74e88450 (LWP 7953) exited]
[Thread 0x74e98450 (LWP 7952) exited]
[Thread 0x74ea8450 (LWP 7951) exited]
[Thread 0x756a8450 (LWP 7950) exited]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
(gdb)

*** Error in `/opt/z-way-server/z-way-server': free(): invalid next size (fast): 0x724e1a90 ***

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x72eff450 (LWP 7960)]
0x76391f70 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56      ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)
Continuing.
[Thread 0x7634b000 (LWP 7949) exited]
[Thread 0x716ff450 (LWP 8419) exited]
[Thread 0x71eff450 (LWP 8418) exited]
[Thread 0x73aff450 (LWP 7959) exited]
[Thread 0x742ff450 (LWP 7958) exited]
[Thread 0x74e68450 (LWP 7955) exited]
[Thread 0x74e78450 (LWP 7954) exited]
[Thread 0x74e88450 (LWP 7953) exited]
[Thread 0x74e98450 (LWP 7952) exited]
[Thread 0x74ea8450 (LWP 7951) exited]
[Thread 0x756a8450 (LWP 7950) exited]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.
Above is the SSH scree output. @PoltoS; I've send a pm to get in touch for providing remote access to my box

Re: Server is constantly crashing

Posted: 05 Mar 2019 13:17
by Confuzer
What fixed crashing so much for me was with all versions I disabled the logging. I have 50 to 60 z-wave device endpoints (a lot of multi-sensors) and the logging file was spammed a lot.

The server crashed up to 7 times a day, also on another SD card. When I disable the save method in the .js file, the server runs much more stable.