ZWay crashing daily
Re: ZWay crashing daily
Please checkout this github post:
https://github.com/Z-Wave-Me/z-way-issues/issues/125
seems that the problem could be related in very big notification.json
As a workaround you can try one of the following options:
stop z-way-server
a.) remove notification.json from automation/storage:
b.) overwrite notification.json from automation/storage with []
c.) or reduce it's content with an editor to the last entries and save it
and finally restart the server:
Keep in mind that if you clear it, all notifications of the last week are gone.
Meanwhile we'll refactor the notification handling und reduce there RAM usage.
Also 24 Hours Device History app related to a z-wave household with a lot of devices could be a reason for that. Stopping the app could be a try to solve the issue. In next future we'll also enhance this app, too.
If you still have problem's please have a look at the debugging steps on page 2. Collect your issues and send it to our support ( support@zwaveeurope.com ), post it here in the thread or on github.
https://github.com/Z-Wave-Me/z-way-issues/issues/125
seems that the problem could be related in very big notification.json
As a workaround you can try one of the following options:
stop z-way-server
Code: Select all
$ sudo /etc/init.d/z-way-server stop
Code: Select all
$ sudo rm /opt/z-way-server/automation/storage/notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
Code: Select all
$ sudo sh -c 'echo "[]" > /opt/z-way-server/automation/storage/notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json'
and finally restart the server:
Code: Select all
$ sudo /etc/init.d/z-way-server start
Meanwhile we'll refactor the notification handling und reduce there RAM usage.
Also 24 Hours Device History app related to a z-wave household with a lot of devices could be a reason for that. Stopping the app could be a try to solve the issue. In next future we'll also enhance this app, too.
If you still have problem's please have a look at the debugging steps on page 2. Collect your issues and send it to our support ( support@zwaveeurope.com ), post it here in the thread or on github.
Re: ZWay crashing daily
40+ devices.. Rebooted yesterday.
uptime: 17:25:04 up 1 day, 7:49, 0 users, load average: 0.54, 0.27, 0.15
/opt/z-way-server/automation/storage
total 47704
-rw-r--r-- 1 root root 9374 Mar 29 08:20 admin1490793654441gif-a04e296a4b28afbaa1a336a7ba3dd07a.json
-rw-r--r-- 1 root root 54745 Apr 24 17:22 configjson-06b2d3b23dce96e1619d2b53d6c947ec.json
-rw-r--r-- 1 root root 149 Mar 29 20:48 expertconfigjson-0ef43e77bc4a34ec19a6c355a525b65c.json
-rw-r--r-- 1 root root 224458 Apr 24 17:20 incomingPacketjson-5fa134bd40ea2f6f328252a67a68d93d.json
-rw-r--r-- 1 root root 13 Mar 29 08:03 moduleTokensjson-e29993de748adf5cf0e062ce571f1bc1.json
-rw-r--r-- 1 root root 48336410 Apr 24 17:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
-rw-r--r-- 1 root root 92396 Apr 24 17:20 originPacketsjson-a9224461330689488046261dbbc78a6d.json
-rw-r--r-- 1 root root 103637 Apr 24 17:20 outgoingPacketjson-5ac52a30a37d9ec108b8b540a6ee42cf.json
-rw-r--r-- 1 root root 178 Apr 23 09:35 storageContent-0c40aa7c27d2121efdfa27fff03c9548.json
-rw-r--r-- 1 root root 737 Apr 23 09:26 userSkinsjson-3b22ba526c58b899e53cfc3217141334.json
total used free shared buffers cached
Mem: 947732 375212 572520 6340 43736 151376
uptime: 17:25:04 up 1 day, 7:49, 0 users, load average: 0.54, 0.27, 0.15
/opt/z-way-server/automation/storage
total 47704
-rw-r--r-- 1 root root 9374 Mar 29 08:20 admin1490793654441gif-a04e296a4b28afbaa1a336a7ba3dd07a.json
-rw-r--r-- 1 root root 54745 Apr 24 17:22 configjson-06b2d3b23dce96e1619d2b53d6c947ec.json
-rw-r--r-- 1 root root 149 Mar 29 20:48 expertconfigjson-0ef43e77bc4a34ec19a6c355a525b65c.json
-rw-r--r-- 1 root root 224458 Apr 24 17:20 incomingPacketjson-5fa134bd40ea2f6f328252a67a68d93d.json
-rw-r--r-- 1 root root 13 Mar 29 08:03 moduleTokensjson-e29993de748adf5cf0e062ce571f1bc1.json
-rw-r--r-- 1 root root 48336410 Apr 24 17:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
-rw-r--r-- 1 root root 92396 Apr 24 17:20 originPacketsjson-a9224461330689488046261dbbc78a6d.json
-rw-r--r-- 1 root root 103637 Apr 24 17:20 outgoingPacketjson-5ac52a30a37d9ec108b8b540a6ee42cf.json
-rw-r--r-- 1 root root 178 Apr 23 09:35 storageContent-0c40aa7c27d2121efdfa27fff03c9548.json
-rw-r--r-- 1 root root 737 Apr 23 09:26 userSkinsjson-3b22ba526c58b899e53cfc3217141334.json
total used free shared buffers cached
Mem: 947732 375212 572520 6340 43736 151376
Re: ZWay crashing daily
gosh ... that seems to be realy huge ... usually every entry older than one week should be removed daily at 0:00 am but I think if the file is this big, this won't work - too much data. Possible that this routine will crash z-way-server after several time each day ...-rw-r--r-- 1 root root 48336410 Apr 24 17:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
we need to find out why the routine fails.
What happens if you try one of the steps above? Will it work after?
Of course you can make a backup of the whole folder and restore it if necessary.
Re: ZWay crashing daily
ronie,
I'll work on setting up something today and report back.
--CN
I'll work on setting up something today and report back.
--CN
What happens if you try one of the steps above? Will it work after?ronie wrote:-rw-r--r-- 1 root root 48336410 Apr 24 17:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
Re: ZWay crashing daily
Stopped z-way, removed the file and restarted z-way. Everything seems good so far. Here are the metrics after 12 hours of use.
-rw-r--r-- 1 root root 9374 Mar 29 08:20 admin1490793654441gif-a04e296a4b28afbaa1a336a7ba3dd07a.json
-rw-r--r-- 1 root root 54806 Apr 25 20:46 configjson-06b2d3b23dce96e1619d2b53d6c947ec.json
-rw-r--r-- 1 root root 149 Mar 29 20:48 expertconfigjson-0ef43e77bc4a34ec19a6c355a525b65c.json
-rw-r--r-- 1 root root 461154 Apr 25 20:46 incomingPacketjson-5fa134bd40ea2f6f328252a67a68d93d.json
-rw-r--r-- 1 root root 13 Mar 29 08:03 moduleTokensjson-e29993de748adf5cf0e062ce571f1bc1.json
-rw-r--r-- 1 root root 194654 Apr 25 20:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
-rw-r--r-- 1 root root 49788 Apr 25 20:43 originPacketsjson-a9224461330689488046261dbbc78a6d.json
-rw-r--r-- 1 root root 124049 Apr 25 20:40 outgoingPacketjson-5ac52a30a37d9ec108b8b540a6ee42cf.json
-rw-r--r-- 1 root root 178 Apr 25 08:32 storageContent-0c40aa7c27d2121efdfa27fff03c9548.json
-rw-r--r-- 1 root root 737 Apr 25 08:32 userSkinsjson-3b22ba526c58b899e53cfc3217141334.json
total used free shared buffers cached
Mem: 947732 234216 713516 6340 44228 114628
-rw-r--r-- 1 root root 9374 Mar 29 08:20 admin1490793654441gif-a04e296a4b28afbaa1a336a7ba3dd07a.json
-rw-r--r-- 1 root root 54806 Apr 25 20:46 configjson-06b2d3b23dce96e1619d2b53d6c947ec.json
-rw-r--r-- 1 root root 149 Mar 29 20:48 expertconfigjson-0ef43e77bc4a34ec19a6c355a525b65c.json
-rw-r--r-- 1 root root 461154 Apr 25 20:46 incomingPacketjson-5fa134bd40ea2f6f328252a67a68d93d.json
-rw-r--r-- 1 root root 13 Mar 29 08:03 moduleTokensjson-e29993de748adf5cf0e062ce571f1bc1.json
-rw-r--r-- 1 root root 194654 Apr 25 20:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
-rw-r--r-- 1 root root 49788 Apr 25 20:43 originPacketsjson-a9224461330689488046261dbbc78a6d.json
-rw-r--r-- 1 root root 124049 Apr 25 20:40 outgoingPacketjson-5ac52a30a37d9ec108b8b540a6ee42cf.json
-rw-r--r-- 1 root root 178 Apr 25 08:32 storageContent-0c40aa7c27d2121efdfa27fff03c9548.json
-rw-r--r-- 1 root root 737 Apr 25 08:32 userSkinsjson-3b22ba526c58b899e53cfc3217141334.json
total used free shared buffers cached
Mem: 947732 234216 713516 6340 44228 114628
Re: ZWay crashing daily
There are definitely issues with the notification.json! The included data starts with the time of the last system reboot and is not deleted even when restarting the z-way-server. If the file is to big, z-way crashs.
Why are all notifications stored in this file permanently? This is not a good design. Something like this should be stored in /var/log and has to be rotated frequently!
Please fix it soon!
Why are all notifications stored in this file permanently? This is not a good design. Something like this should be stored in /var/log and has to be rotated frequently!
Please fix it soon!
Re: ZWay crashing daily
I have updated to the latest version, and my crashes stopped.
My notifications file is:
-rw-r--r-- 1 root root 79118334 Apr 28 20:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
My notifications file is:
-rw-r--r-- 1 root root 79118334 Apr 28 20:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
Re: ZWay crashing daily
Why do not you have these two files. They are so great with me!
-rw-r--r-- 1 root root 2056569 Apr 21 21:33 dedevicesjson-b02fc6609e0022e8f55ff6bb5b853d35.json
-rw-r--r-- 1 root root 2179432 Apr 21 21:33 endevicesjson-7904daacdb872d656b01c6c9eddd3a48.json
Should i delete the files?
v2.3.4
The reduction of the notifications ... 5dd.json had no success. It still chrash.
-rw-r--r-- 1 root root 2056569 Apr 21 21:33 dedevicesjson-b02fc6609e0022e8f55ff6bb5b853d35.json
-rw-r--r-- 1 root root 2179432 Apr 21 21:33 endevicesjson-7904daacdb872d656b01c6c9eddd3a48.json
Should i delete the files?
v2.3.4
The reduction of the notifications ... 5dd.json had no success. It still chrash.
Re: ZWay crashing daily
CHASH, Files:
-rw-r--r-- 1 root root 9322 Apr 21 21:33 admin1491077878163gif-566e02c50e71dbfbaaa779d3d09dc571.json
-rw-r--r-- 1 root root 9612 Apr 21 21:33 backupConfig201606211744-de278d7dc12d90e0b6a13b17e1c115d1.json
-rw-r--r-- 1 root root 63408 May 1 21:42 configjson-06b2d3b23dce96e1619d2b53d6c947ec.json
-rw-r--r-- 1 root root 2055817 Apr 30 11:16 dedevicesjson-b02fc6609e0022e8f55ff6bb5b853d35.json
-rw-r--r-- 1 root root 2179082 Apr 30 11:16 endevicesjson-7904daacdb872d656b01c6c9eddd3a48.json
-rw-r--r-- 1 root root 162 Apr 30 11:10 expertconfigjson-0ef43e77bc4a34ec19a6c355a525b65c.json
-rw-r--r-- 1 root root 87936 May 1 21:31 incomingPacketjson-5fa134bd40ea2f6f328252a67a68d93d.json
-rw-r--r-- 1 root root 0 Apr 21 21:33 .keep
-rw-r--r-- 1 root root 13 Apr 21 21:33 moduleTokensjson-e29993de748adf5cf0e062ce571f1bc1.json
-rw-r--r-- 1 root root 793758 May 1 21:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
-rw-r--r-- 1 root root 13832 May 1 21:34 originPacketsjson-a9224461330689488046261dbbc78a6d.json
-rw-r--r-- 1 root root 52113 May 1 21:40 outgoingPacketjson-5ac52a30a37d9ec108b8b540a6ee42cf.json
-rw-r--r-- 1 root root 324 Apr 21 21:33 RaZberry-a5f9fbc303b7d5d74f99c840f738b01f.json
-rw-r--r-- 1 root root 228 Apr 30 10:41 storageContent-0c40aa7c27d2121efdfa27fff03c9548.json
-rw-r--r-- 1 root root 9322 Apr 21 21:33 admin1491077878163gif-566e02c50e71dbfbaaa779d3d09dc571.json
-rw-r--r-- 1 root root 9612 Apr 21 21:33 backupConfig201606211744-de278d7dc12d90e0b6a13b17e1c115d1.json
-rw-r--r-- 1 root root 63408 May 1 21:42 configjson-06b2d3b23dce96e1619d2b53d6c947ec.json
-rw-r--r-- 1 root root 2055817 Apr 30 11:16 dedevicesjson-b02fc6609e0022e8f55ff6bb5b853d35.json
-rw-r--r-- 1 root root 2179082 Apr 30 11:16 endevicesjson-7904daacdb872d656b01c6c9eddd3a48.json
-rw-r--r-- 1 root root 162 Apr 30 11:10 expertconfigjson-0ef43e77bc4a34ec19a6c355a525b65c.json
-rw-r--r-- 1 root root 87936 May 1 21:31 incomingPacketjson-5fa134bd40ea2f6f328252a67a68d93d.json
-rw-r--r-- 1 root root 0 Apr 21 21:33 .keep
-rw-r--r-- 1 root root 13 Apr 21 21:33 moduleTokensjson-e29993de748adf5cf0e062ce571f1bc1.json
-rw-r--r-- 1 root root 793758 May 1 21:00 notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json
-rw-r--r-- 1 root root 13832 May 1 21:34 originPacketsjson-a9224461330689488046261dbbc78a6d.json
-rw-r--r-- 1 root root 52113 May 1 21:40 outgoingPacketjson-5ac52a30a37d9ec108b8b540a6ee42cf.json
-rw-r--r-- 1 root root 324 Apr 21 21:33 RaZberry-a5f9fbc303b7d5d74f99c840f738b01f.json
-rw-r--r-- 1 root root 228 Apr 30 10:41 storageContent-0c40aa7c27d2121efdfa27fff03c9548.json