suddenly getting dzvents errors

[Gravityz]

i am currently using build 2020.1.11839 on a synoloy DS718+

This version is running stable for months now.

suddenly i got these errors in the log which were caused at 00:00
i did not change anything and the script dzV-Tuinsproeier does exist in /usr/local/domoticz/var/scripts/dzVents/generated_scripts/

what could have caused this behaviour?
the errors also stopped on their own

Code: Select all

2020-05-25 00:00:00.527 Error: dzVents: Error: (3.0.1) module 'dzV-Tuinsproeier' not found:
2020-05-25 00:00:00.527 no field package.preload['dzV-Tuinsproeier']
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/dzVents/runtime/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/dzVents/runtime/device-adapters/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/dzVents/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/scripts/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/../lua/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/scripts/modules/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/generated_scripts/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/data/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/modules/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/share/lua/5.3/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/share/lua/5.3/dzV-Tuinsproeier/init.lua'
2020-05-25 00:00:00.527 no file '/usr/local/lib/lua/5.3/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/lib/lua/5.3/dzV-Tuinsproeier/init.lua'
2020-05-25 00:00:00.527 no file './dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file './dzV-Tuinsproeier/init.lua'
2020-05-25 00:00:00.527 no file '/usr/local/domoticz/var/scripts/dzVents/dzV-Tuinsproeier.lua'
2020-05-25 00:00:00.527 no file '/usr/local/lib/lua/5.3/dzV-Tuinsproeier.so'
2020-05-25 00:00:00.527 no file '/usr/local/lib/lua/5.3/loadall.so'
2020-05-25 00:00:00.527 no file './dzV-Tuinsproeier.so'

[waaren]

I am currently using build 2020.1.11839 on a synoloy DS718+
suddenly i got these errors in the log which were caused at 00:00

what could have caused this behaviour?

You seem to have hit a rare timing issue.

At every reset of the event System, domoticz read the internal dzVents scripts from the database and write them to the OS file system just after deleting the old ones. This is done in another thread then the event system.
Event System resets are triggered by domoticz (re) starts , hardware module changes, adding or deleting a device, dzVents internal script modifications and... every day at 00:00.
It looks like dzVents did read this script's on = section just before the script was replaced and tried to process it further the moment between deletion and recreation.

Can you keep an eye on it to see if it occurs frequently?

[Gravityz]

ok. i will watch out for this if it happens again.

I have only seen something similar before. at that time i was playing a lot with os.execute commands which did put a lot of load on the system and the memory consumption. this is not the case this time(memory 11.91%, CPU 2.64%)

[Gravityz]

just to make sure

this is in the on section of that script
it is supposed to only be activated by device Tuinsproeier from april 1th until september 30th
Maybe it has something to do with it

Code: Select all

on = {
       devices = { ['Tuinsproeier'] = {'on 01/04-30/09'} }

in another script i have this

Code: Select all

on = {
        devices = {
            ['PIR sensor'] = {'between sunset and 00:00'}
        }

these are the only 2 scripts which have both a device as trigger as well as a timeframe