I think I've experienced a bug when auto upgrading to v1.2.9.
I'm running the snap version of node red on a centos 8 system. Today the node red snap has been automatically upgraded to v1.2.9. After that, the daemon was not able to start the service anymore.
These are the corresponding lines in the log file.
10 Feb 14:14:13 - [info] Dashboard version 2.24.0 started at /ui 10 Feb 14:14:14 - [error] Failed to start server: 10 Feb 14:14:14 - [error] Error: EPERM: operation not permitted, copyfile '/root/snap/node-red/671/.config.nodes.json' -> '/root/snap/node-red/671/.config.nodes.json.backup'
After discovering this I checked the permissions corresponding to that folder but I couldn't see anything unusual. The snap is running as user root and the permissions seem to be correct. To be sure I double checked the folder permissions using getfacl and set them to 777, just to be sure. That didn't help.
Any ideas how to tackle this error? It looks very much like a bug to me, especially because node red worked just fine until the upgrade.