[Ulrich.Arnold]

Can you guide me to the error lines?

Except for log13.log, which ran for 10 min without error and was terminated by me, all other runs quit after the last line 

Code:

pilight-daemon: /home/pilight/source/daemon-dev/libs/libuv/threadpool.c:312: uv__queue_done: Assertion `(((const QUEUE *) (&(req->loop)->active_reqs) == (const QUEUE *) (*(QUEUE **) &((*(&(req->loop)->active_reqs))[0]))) == 0)' failed.

Just a thought: As you can't reproduce it, could it be some external signal from the receiver which causes the failure? I see some 

Code:

[Apr 14 13:41:44:803752] pilight-daemon: DEBUG: **** RAW CODE ****
[Apr 14 13:41:44:803846] pilight-daemon: DEBUG: **** RAW CODE ****

in the logs
Uli

[curlymo]

I have a few ideas that could be causing this, but i have to think some more about the solution.

[curlymo]

Currently testing my fixes myself.

[curlymo]

There are still some small issues left, but i'm wondering if you are still encountering the same issue?

[Ulrich.Arnold]

There are still some small issues left, but i'm wondering if you are still encountering the same issue?

Which version shall i test ?

Uli

[Ulrich.Arnold]

There are still some small issues left, but i'm wondering if you are still encountering the same issue?

Which version shall i test ?

Uli

Hi curlymo

Today I installed nightly 8.1.4-49. Looks good until now. Running for more than 2 hours,  before it did quit after some minutes.
Out of curiosity: what was special about my config and what did you change?

Thanks Uli

[curlymo]

You can check github for all changed made in the code. That's the most time efficient answer.

[Ulrich.Arnold]

Hi curlymo

Today I installed nightly 8.1.4-49. Looks good until now. Running for more than 2 hours,  before it did quit after some minutes.
Out of curiosity: what was special about my config and what did you change?

Thanks Uli

Hi curlymo!

I'm sorry to report, that the issue is not yet solved. The time until crashing is a lot longer, but I still get the crash after some hours in the full config.

This is the debug-output

Code:

 Start and end in log21.txt

pilight.log ends with:

Code:

[May 12 18:50:45:888334] pilight-daemon: INFO: executed rule: SetArbeitstagAus
[May 12 18:50:45:905402] pilight-daemon: INFO: executed rule: SetLabelEGArbeit2
[May 12 18:50:45:907166] pilight-daemon: INFO: executed rule: SetLabelEG2
[May 12 18:50:45:908594] pilight-daemon: INFO: executed rule: SetLabelEG4
[May 12 18:50:45:910236] pilight-daemon: INFO: executed rule: SetLabelOG1
[May 12 18:50:45:911579] pilight-daemon: INFO: executed rule: SetLabelRollos1
[May 12 18:50:45:916262] pilight-daemon: ERROR: attempt to index a number value
[May 12 18:50:45:916262] pilight-daemon: ERROR: attempt to index a number value

This is a second case:

Code:

Start and end in log22.txt

and the pilight.log end in:

Code:

ERROR: attempt to index a number value

Uli

[curlymo]

It seems that this is a new error unknown before because it crashed too soon. Can you open a new one for this one?

[curlymo]

I believe i FINALLY fixed it.

For those interested in the background.

The lua c metatables i built where not concurrent, therefor when multiple threads (lua states) where writing to the same metatable index, it errored. Making data-structures properly thread safe is pretty difficult (hence my long development time). I tried using existing concurrent hashtable implementations, but none of them worked the way i wanted, to i decided to fix my own implementation. Which i believe i did.

I'm currently running this code myself first, i will push this weekend.