10 seconds [Solved]

[pvklink]

Hi,

is there a way to check which script is running more than 10 seconds.. I dont get this warning every time so putting scripts on/off is not a way to do it..

Code: Select all

2019-08-16 12:02:16.323 Error: SMTP Mailer: Error sending Email to: <[email protected]> !
2019-08-16 19:50:10.363 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2019-08-16 21:20:10.770 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2019-08-16 22:00:10.498 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2019-08-16 23:45:10.026 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2019-08-17 00:20:10.287 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2019-08-17 00:50:10.665 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2019-08-17 06:20:10.700 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds

[waaren]

is there a way to check which script is running more than 10 seconds.. I dont get this warning every time so putting scripts on/off is not a way to do it..

The warning / error is generated by domoticz when the dzVents.lua is executing for more then 10 seconds. dzVents.lua is the dispatcher process within dzVents for all the user scripts. If you set the loglevel for dzVents to

Errors + minimal execution info

you will see which script is started just before the domoticz warning.
The warning can also point to other processes on your system taking (for a moment) all available resources. Like the automatic backup from domoticz executing on the hour.

[pvklink]

ok, gonna do that right away... curious which script...

[pvklink]

It was the philips hue-device....

[waaren]

It was the philips hue-device....

Can you please elaborate a bit on this ? Still guessing now what the root cause is.

[pvklink]

I think that the hue plugin has some problems. Domoticz does not see the hue-hub.
I think because the router was restarted after a lighting strike and the hue had his old hcp-ticket and could refresh it... or something like that...

I will restart the hue and connect it again... and see if the messages dissapear

[pvklink]

is the rule before the time-out the cause of the timeout?
so i have to many pings....

2019-08-22 13:18:55.223 Error: Pinger: This is a read-only sensor!
2019-08-22 13:18:55.572 Error: Pinger: This is a read-only sensor!
2019-08-22 13:18:57.093 Error: Pinger: This is a read-only sensor!
2019-08-22 13:18:57.653 Error: Pinger: This is a read-only sensor!
2019-08-22 18:40:17.596 Error: EventSystem: Warning!, lua script /home/pi/domoticz/dzVents/runtime/dzVents.lua has been running for more than 10 seconds
2019-08-22 19:56:01.161 Error: Pinger: This is a read-only sensor!

[waaren]

is the rule before the time-out the cause of the timeout?

No not necessarily. In this case the times of the errors are not close enough to the Warning.

The Warning can come from a busy system (waiting for disk / network IO, Memory, CPU or another resource) caused by domoticz or another process or from a script (dzvents, Lua, Python) blocking the event system (this can happen if you wait for an HTPP response via curl or from another OS call to return or from a very resource hungry script (look for nested loops or loop over a very, very large table (_G or similar)

[pvklink]

ok...thanks..
will pause some scripts and services for a period of time...