System log spamming Segmentation Fault

[Wynn]

My Almond+ is spamming the system log with Segmentation fault every second. I tried rebooting, but it is still happening every second. Any idea what causes it or how to fix it? This is using the R070as firmware.

Mar 27 15:18:10 AlmondPlus user.info sysinit: .Segmentation fault
Mar 27 15:18:11 AlmondPlus user.info sysinit: Segmentation fault
Mar 27 15:18:12 AlmondPlus user.info sysinit: .Segmentation fault
Mar 27 15:18:13 AlmondPlus user.info sysinit: Segmentation fault
Mar 27 15:18:14 AlmondPlus user.info sysinit: Segmentation fault
Mar 27 15:18:15 AlmondPlus user.info sysinit: .Segmentation fault
Mar 27 15:18:16 AlmondPlus user.info sysinit: Segmentation fault
Mar 27 15:18:17 AlmondPlus user.info sysinit: Segmentation fault
Mar 27 15:18:18 AlmondPlus user.info sysinit: .Segmentation fault
Mar 27 15:18:19 AlmondPlus user.info sysinit: Segmentation fault

[LGNilsson]

Have you created any rules?
If so, can you please delete them and see if it's still happening?

[Wynn]

No, I do not have any rules.
I will wait for the firmware update later this week. Hopefully that will clean things up and restore operation. I will report back when the time comes!

[Wynn]

I updated to R072, and performed a factory reset. It is still happening, exactly like before. Here's a sample from the System Log:


Apr  1 16:29:23 AlmondPlus user.info sysinit: Segmentation fault
Apr  1 16:29:24 AlmondPlus user.info sysinit: Segmentation fault
Apr  1 16:29:25 AlmondPlus user.info sysinit: Segmentation fault
Apr  1 16:29:26 AlmondPlus user.info sysinit: [938:6459] ERR: WebsocketSegmentation fault
Apr  1 16:29:27 AlmondPlus user.info sysinit: Segmentation fault
Apr  1 16:29:28 AlmondPlus user.info sysinit: Segmentation fault
Apr  1 16:29:28 AlmondPlus user.info sysinit: Segmentation fault
Apr  1 16:29:29 AlmondPlus user.info sysinit: Segmentation fault

[Wynn]

While on the phone with help desk, I was able to finally pair a zwave device. As soon as I paired a device, the segmentation faults stopped. I uploaded logs and the tech support will follow up with the dev team.

So this issue is now resolved.