forum

And died again - I've disable my HTTPDevice plugin as that's almost certainly causing the crashes.
Shame about that - if you can fix this that's great, otherwise I'll have to consider checking alarm status in another process and then changing a device in z-wave.me process. Won't have time for the re-code in the foreseeable future though.

Can ypu provide me an example of the request, reply and HTTPDevice configuration - we can make 1000 requests per second to see if the error happens

Hi,

Without HTTPDevice configuration, it continue crashing. I have fresh installs and the same problem. Always v2.3.6 and firmware updated.

Hardware
Vendor: RaZberry by Z-Wave.Me
Vendors Product ID: 1024 / 2
Z-Wave Chip: ZW0500
Firmware
Library Type: Static Controller
SDK Version: 6.71.01
Serial API Version: 05.23

Regards.

@PoltoS - my apologies for taking so long to response to you request for examples.
I've put together all the details I think you'll need in the attached.
Of course I don't know if a different format of response is what's causing the crash - let me know if you have a debug version with extra logging that you'd like me to try.

Regards

Any update on this issue?

We are trying to locate the bug. We see some reports about openHAB integration (also HTTP) to cause random crash. The problem is a memory override in some place, so pretty hard to find. And we can not reproduce it in our lab - this makes us mad, because this might mean dependance on some arch or what ever else.

The more debug info (mostly gdb reports) we find, the better we can understand what happens

Got a crash without my HTTPDevice plugin activated.
Now installed monit to auto restart z-wave-server if it crashes.

Can you give us the gdb report?

I don't have it running under gdb all the time. Is there a way I can do that and still run it as a background process?

Yes, use "screen".

Is the problem still relevant on v2.3.7? If so, can you help us to reproduce it or use your environment to hunt?