I just tried to run the first command but it can’t seem to find doss2unix.
it should be sudo apt-get -y install dos2unix
. This does seem to work.
-
Pimatic dont start after Update
-
thx for reporting
i just changed the typo!pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
Thank @mwittig, this works! My second Pi just had the same problem. Now it’s all running smooth again.
-
Trank you very much @mwittig That was the Solution!!! Is it a Bug in Update or did i do something wrong?
-
@HarrySteff Unfortunately, a bug in releases pimatic@0.8.105 and pimatic@0.8.106. Actually, a packaging problem.
pimatic@0.8.107 fixes the issue
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
next problem after update, again no GUi
pi@raspberrypi:~ $ sudo service pimatic status ● pimatic.service - LSB: pimatic service Loaded: loaded (/etc/init.d/pimatic) Active: active (exited) since Fr 2016-04-22 22:52:39 CEST; 1 weeks 1 days ago Process: 30015 ExecStop=/etc/init.d/pimatic stop (code=exited, status=0/SUCCESS) Process: 30119 ExecStart=/etc/init.d/pimatic start (code=exited, status=0/SUCCESS) Apr 30 11:05:00 raspberrypi sudo[3083]: pam_unix(sudo:session): session clos...t Apr 30 11:10:00 raspberrypi sudo[3175]: root : TTY=unknown ; PWD=/home/pi ; ...t Apr 30 11:10:00 raspberrypi sudo[3175]: pam_unix(sudo:session): session open...) Apr 30 11:10:00 raspberrypi sudo[3175]: pam_unix(sudo:session): session clos...t Apr 30 11:15:00 raspberrypi sudo[3268]: root : TTY=unknown ; PWD=/home/pi ; ...t Apr 30 11:15:00 raspberrypi sudo[3268]: pam_unix(sudo:session): session open...) Apr 30 11:15:00 raspberrypi sudo[3268]: pam_unix(sudo:session): session clos...t Apr 30 11:20:00 raspberrypi sudo[3383]: root : TTY=unknown ; PWD=/home/pi ; ...t Apr 30 11:20:00 raspberrypi sudo[3383]: pam_unix(sudo:session): session open...) Apr 30 11:20:00 raspberrypi sudo[3383]: pam_unix(sudo:session): session clos...t Hint: Some lines were ellipsized, use -l to show in full. pi@raspberrypi:~ $ sudo service pimatic restart Job for pimatic.service failed. See 'systemctl status pimatic.service' and 'journalctl -xn' for details. pi@raspberrypi:~ $
-
I think we would need the pimatic-daemon.log file to help you.
@sweetpi Just had an interesting Idea… could we introduce a verry minimal express instance which forwards the pimatic-daemon.log file to the browser in the case of a failure?