I've come across rare cases where RM throws an exception on the Append to file action. I have two rules sharing the same log file and I wonder if the problem occurs when both are trying to log to the same file at the "same time", triggering the exception. Failure looks like this:
Is there an easy way to resolve this? I would prefer to avoid having to use separate files.
(this is on .196)
That will happen any time you have 2 (or more) different processes trying to manipulate the same file…
I didn't realize it at first but the consequence was that the file was truncated to zero...
In RM that can mean many things, like different instances of one rule, different rules, or even a delayed action. If there was a way to protect the user from having to consider these caveats when using RM...
Competes with KISS in this case, but ok, fair enough. I don't have a choice to go with a single rule with ignore triggers while running set, given the potential destructive impact (the content of the file was lost).
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
