• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
uv__io_poll: Assertion `w->pevents != 0' failed
#1
After using pilight for more than a year I have started Eventing with my 433MHz switches and have also switched to 8.1.5 and Raspberry Pi3B.
Now I am getting randomly an assertion failure after pilight ran for some hours:

Code:
Jun 15 23:00:42 rp3b0 systemd[1]: Started pilight.
Jun 16 05:46:42 rp3b0 pilight-daemon[14932]: pilight-daemon: /home/pilight/source/daemon-dev/libs/libuv/unix/linux-core.c:228: uv__io_poll: Assertion `w->pevents != 0' failed.
Jun 16 05:46:42 rp3b0 systemd[1]: pilight.service: main process exited, code=killed, status=6/ABRT
Jun 16 05:46:42 rp3b0 systemd[1]: Unit pilight.service entered failed state.
How can I further debug this?

This is the rules section:

Code:
        "rules": {
                "Innenbeleuchtung1An": {
                        "rule": "IF (Sonne.sunset - 1 == ZeitDatum.hour + (ZeitDatum.minute / 100)) AND ZeitDatum.second < 1 THEN switch DEVICE Innenbeleuchtung1 TO on",
                        "active": 1
                },
                "Innenbeleuchtung2An": {
                        "rule": "IF (Sonne.sunset - 1 == ZeitDatum.hour + (ZeitDatum.minute / 100)) AND ZeitDatum.second < 1 THEN switch DEVICE Innenbeleuchtung2 TO on",
                        "active": 1
                },
                "Innenbeleuchtung3An": {
                        "rule": "IF (Sonne.sunset - 1 == ZeitDatum.hour + (ZeitDatum.minute / 100)) AND ZeitDatum.second < 1 THEN switch DEVICE Innenbeleuchtung3 TO on",
                        "active": 1
                },
                "Innenbeleuchtung1Aus": {
                        "rule": "IF (23 == ZeitDatum.hour + (ZeitDatum.minute / 100)) AND ZeitDatum.second < 2 THEN switch DEVICE Innenbeleuchtung1 TO off",
                        "active": 1
                },
                "Innenbeleuchtung2Aus": {
                        "rule": "IF (23 == ZeitDatum.hour + (ZeitDatum.minute / 100)) AND ZeitDatum.second < 2 THEN switch DEVICE Innenbeleuchtung2 TO off",
                        "active": 1
                },
                "Innenbeleuchtung3Aus": {
                        "rule": "IF (23 == ZeitDatum.hour + (ZeitDatum.minute / 100)) AND ZeitDatum.second < 2 THEN switch DEVICE Innenbeleuchtung3 TO off",
                        "active": 1
                },
                "AussenbeleuchtungAus": {
                        "rule": "IF (23 == ZeitDatum.hour + (ZeitDatum.minute / 100)) AND ZeitDatum.second < 2 THEN switch DEVICE Aussenbeleuchtung TO off",
                        "active": 1
                }
        },

This is what uname -a says:

Quote:Linux rp3b0 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
 
Reply
#2
Can you test if the latest nightly is better?
 
Reply
#3
(06-16-2020, 02:39 PM)curlymo Wrote: Can you test if the latest nightly is better?

I have installed pilight=8.1.5-110-g1af4c284 now and started pilight again. Will reply tomorrow.
 
Reply
#4
(06-16-2020, 02:54 PM)monok Wrote:
(06-16-2020, 02:39 PM)curlymo Wrote: Can you test if the latest nightly is better?

I had a problem that the hardware entries were gone in the config.json. Fixed it. 
I am testing again now pilight=8.1.5-110-g1af4c284
 
Reply
#5
(06-18-2020, 10:13 AM)monok Wrote:
(06-16-2020, 02:54 PM)monok Wrote:
(06-16-2020, 02:39 PM)curlymo Wrote: Can you test if the latest nightly is better?

I had a problem that the hardware entries were gone in the config.json. Fixed it. 
I am testing again now pilight=8.1.5-110-g1af4c284
It's running now for several days.
There was a SIGSEGV on Jun 23. Service was restarted automatically by systemd. So it's better than before.
This is all  I have for this error:

Code:
Jun 19 13:17:06 rp3b0 systemd[1]: Starting pilight...
Jun 19 13:17:08 rp3b0 systemd[1]: Started pilight.
Jun 23 11:16:50 rp3b0 systemd[1]: pilight.service: main process exited, code=killed, status=11/SEGV
Jun 23 11:16:50 rp3b0 systemd[1]: Unit pilight.service entered failed state.
Jun 23 11:16:50 rp3b0 systemd[1]: pilight.service holdoff time over, scheduling restart.
Jun 23 11:16:50 rp3b0 systemd[1]: Stopping pilight...
Jun 23 11:16:50 rp3b0 systemd[1]: Starting pilight...
Jun 23 11:16:51 rp3b0 systemd[1]: Started pilight.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight development installation -- failed / what is the secret? gneandr 5 3,275 02-04-2017, 10:06 AM
Last Post: gneandr
  v6 --> V7 (Nightly) failed -- pl.help gneandr 9 4,985 08-03-2015, 07:09 PM
Last Post: curlymo
  Error message when start of pilight failed. Landixus 8 7,915 07-25-2015, 06:53 PM
Last Post: curlymo
  "pilight failed!" with elro_hc protocol device o1y 0 1,945 05-09-2015, 02:44 PM
Last Post: o1y
  no pilight ssdp connections found/failed to kill 3400 Xilinx64 3 3,698 02-13-2015, 12:57 PM
Last Post: curlymo
  Failed to connect, touch to reload BenPi 2 2,608 02-28-2014, 11:21 PM
Last Post: creamers

Forum Jump:


Browsing: 1 Guest(s)