assert kommands starts failing randomly

Easy to use, 100% Lua-based event scripting framework.

Moderator: leecollings

Post Reply
mroerigdalgaard
Posts: 7
Joined: Tuesday 05 May 2020 21:19
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

assert kommands starts failing randomly

Post by mroerigdalgaard »

Hi.

I had this script running in several month without any error.
Now it starts creating an error once or twice a day (script runs every minute).

Scriptline:
local file = assert(io.open("/mnt/nfs/pihome/UpdateNeeded.txt", "r"), "OSup1: Error reading UpdateNeeded.txt")

error:
2020-05-05 04:06:00.308 Error: dzVents: Error: (3.0.2) OSUP 1: An error occurred when calling event handler ReadOSUpdates1
2020-05-05 04:06:00.308 Error: dzVents: Error: (3.0.2) OSUP 1: ...icz/scripts/dzVents/generated_scripts/ReadOSUpdates1.lua:20: assertion failed!

Domoticz version 2020.2 error startet before installation of 2020.2
running on an RaspberryPi 3b+ with buster installed.

Some ideas?
User avatar
waaren
Posts: 6028
Joined: Tuesday 03 January 2017 14:18
Target OS: Linux
Domoticz version: Beta
Location: Netherlands
Contact:

Re: assert kommands starts failing randomly

Post by waaren »

mroerigdalgaard wrote: Tuesday 05 May 2020 21:24 I had this script running in several month without any error.
Now it starts creating an error once or twice a day (script runs every minute).

Some ideas?
My idea is to have a close look at the log around the times you see this error and maybe activate the complete domoticz debug logging. From what I understand you should always get your defined messge when the io.open fail.
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
mroerigdalgaard
Posts: 7
Joined: Tuesday 05 May 2020 21:19
Target OS: Raspberry Pi / ODroid
Domoticz version:
Contact:

Re: assert kommands starts failing randomly

Post by mroerigdalgaard »

waaren wrote: Tuesday 05 May 2020 23:53
mroerigdalgaard wrote: Tuesday 05 May 2020 21:24 I had this script running in several month without any error.
Now it starts creating an error once or twice a day (script runs every minute).

Some ideas?
My idea is to have a close look at the log around the times you see this error and maybe activate the complete domoticz debug logging. From what I understand you should always get your defined messge when the io.open fail.
Tried to start domoticz with debug enabled but then it crashes on startup. Must do later some investigations to set debugging on. -loglevel 3 -debug crashes ....
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest