I’m frustrated! One more time my system doesn’t start up after my weekly backup. This backup will be executed automatically triggered by pimatic. The backup script stops pimatic, make the job and starts pimatic after the backup was done. This is the normal way since over one year. I really have no idea what went wrong last week and this time. This time I have the problem to get it not more working.
Pimatic worked without any error in the last time. First I tried to start the system with sudo pimatic.js to get directly the output from the console. I could see that all plugins get loaded without any problem. Because I have many rules containing telegram the telegram debug output is the next what was logged. This took round about 2 minutes. Yes, I have many rules… After this I got errors for two devices which cannot be updated, because the device is expecting numeric value, but it is getting a string (“unknown”) during startup. I was complaining this in the past. Hopefully it will be handled somehow in the future. A next I was expecting the rendering of the frontend, but the output stops.
When I start it in the standard way by using sudo pimatic.js start, the log ends with only 4 or 5 loaded plugins. It is far away from the content I can see during startup with sudo pimatic.js.
Next step was to get back on the backup version from the night. Same behavior like before. I tried as well to delete the database and one other try was to let reinstall sqlite… No luck!
My last chance was to reinstall pimatic, but as well no luck.
I do not understand, why it is working over long time, but the system dies during a restart. When I ask the status of the daemon with sudo pimatic.js status it is running.
Maybe it is really a problem with the frontend. Is there a way to enforce the start of the frontend?