search

Supergiovane / node-red-contrib-boolean-logic-ultimate

Enhanced boolean logic with persistent values after reboot and more
https://www.youtube.com/watch?v=sYc6L5QQrTw&list=PL9Yh1bjbLAYoRH4IyQB7EL5srHAihiKpy
MIT License
27 stars 3 forks source link

Persistence not working after node-red restart #7

Closed Botched1 closed 3 years ago

Botched1 commented 3 years ago

Not sure if this is new to Node-RED 1.2.x, is because I run node-red in a docker container, or other, but...

After a node-red restart I am losing all persistent states and the boolean node is starting as uninitialized. I verified that the "remember" checkbox IS checked.

EDIT: I rolled the container back to 1.1.3 and get the same thing, so I guess it is not a NR 1.2.x issue. Must be something with my container install I guess. 🤷‍♂️

Supergiovane commented 3 years ago

Hi Please be sure that the node-red’s user, has the rights to write to the filesystem. For example, if node red is running under other user than root, simply give this user the rights to write to the filesystem 😉

Botched1 commented 3 years ago

If I'm the only one complaining, I'm sure the issue is on my end. That said, I've tried running the container as multiple different users (root, node-red:dialout, etc), and get the same thing each time.

After I reboot I just see this on the node: image

Botched1 commented 3 years ago

EDIT: Never mind, it is definitely a docker/permissions issue. Instead of running it in Portainer, I made the container from scratch with "-u node-red:dialout" and persistence works as expected.

I'll close this.