I'm running everything within a Docker container on my Raspberry Pi, that way I need not to think about all the requirements and compiling compiling Owfs myself. And if something is not working right I just throw the container away and start a new one.
https://github.com/smarthomerocks/owserver // Henrik Östman Den tors 18 juli 2019 kl 16:07 skrev Jaroslav Sobota <jsob...@kky.zcu.cz>: > Hi Colin, > thanks for your reply. There seems to be a problem with owserver start > job during installation. Although an error is shown, owserver is > running. Terminal output below. > > The most suspicious is this message: > owserver.service: Failed with result 'protocol'. > > If I run "dpkg --configure -a" after the failed installation, everything > seems fine. > > In Stretch and earlier releases, everything worked out of the box. The > /etc/owfs.conf file is the same as in Stretch. > > Tried restarting the owserver service few more times and it seems the > problem only appears a few times on a clean Raspbian image. After a > while (an hour or so), I am not able to reproduce the issue anymore. > > Any hints please? Thank you. > > With kind regards, > Jaroslav > > > pi@raspberrypi:~ $ systemctl status owserver.service > ● owserver.service - Backend server for 1-wire control > Loaded: loaded (/lib/systemd/system/owserver.service; disabled; > vendor preset: enabled) > Active: active (running) since Thu 2019-07-18 12:23:25 BST; 12min ago > Docs: man:owserver(1) > Main PID: 952 (owserver) > Tasks: 2 (limit: 2200) > Memory: 772.0K > CGroup: /system.slice/owserver.service > └─952 /usr/bin/owserver -c /etc/owfs.conf > > Jul 18 12:23:25 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > Jul 18 12:23:25 raspberrypi OWFS[952]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 12:23:25 raspberrypi systemd[1]: Started Backend server for > 1-wire control. > > > > root@raspberrypi:~# journalctl -n 50 > -- Logs begin at Wed 2019-07-10 01:21:16 BST, end at Thu 2019-07-18 > 14:27:04 BST. -- > Jul 18 14:13:34 raspberrypi systemd[705]: Stopped target Timers. > Jul 18 14:13:34 raspberrypi systemd[705]: gpg-agent-ssh.socket: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[705]: Closed GnuPG cryptographic > agent (ssh-agent emulation). > Jul 18 14:13:34 raspberrypi systemd[705]: dirmngr.socket: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[705]: Closed GnuPG network > certificate management daemon. > Jul 18 14:13:34 raspberrypi systemd[705]: Stopped target Paths. > Jul 18 14:13:34 raspberrypi systemd[705]: Reached target Shutdown. > Jul 18 14:13:34 raspberrypi systemd[705]: systemd-exit.service: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[705]: Started Exit the Session. > Jul 18 14:13:34 raspberrypi systemd[705]: Reached target Exit the Session. > Jul 18 14:13:34 raspberrypi systemd[708]: > pam_unix(systemd-user:session): session closed for user pi > Jul 18 14:13:34 raspberrypi systemd[1]: user@1000.service: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: Stopped User Manager for UID 1000. > Jul 18 14:13:34 raspberrypi systemd[1]: Stopping User Runtime Directory > /run/user/1000... > Jul 18 14:13:34 raspberrypi systemd[757]: run-user-1000.mount: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: run-user-1000.mount: Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: user-runtime-dir@1000.service: > Succeeded. > Jul 18 14:13:34 raspberrypi systemd[1]: Stopped User Runtime Directory > /run/user/1000. > Jul 18 14:13:34 raspberrypi systemd[1]: Removed slice User Slice of UID > 1000. > Jul 18 14:14:00 raspberrypi groupadd[945]: group added to /etc/group: > name=Debian-ow, GID=114 > Jul 18 14:14:00 raspberrypi groupadd[945]: group added to /etc/gshadow: > name=Debian-ow > Jul 18 14:14:00 raspberrypi groupadd[945]: new group: name=Debian-ow, > GID=114 > Jul 18 14:14:00 raspberrypi useradd[950]: new user: name=Debian-ow, > UID=109, GID=114, home=/var/lib/owfs, shell=/usr/sbin/nologin > Jul 18 14:14:00 raspberrypi chage[957]: changed password expiry for > Debian-ow > Jul 18 14:14:00 raspberrypi chfn[961]: changed user 'Debian-ow' information > Jul 18 14:14:04 raspberrypi systemd[1]: Reloading. > Jul 18 14:14:04 raspberrypi systemd[1]: getty@tty1.service: Current > command vanished from the unit file, execution of the command list won't > be resumed. > Jul 18 14:14:04 raspberrypi systemd[1]: serial-getty@ttyAMA0.service: > Current command vanished from the unit file, execution of the command > list won't be resumed. > Jul 18 14:14:04 raspberrypi systemd[1]: Reloading. > Jul 18 14:14:05 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > Jul 18 14:14:05 raspberrypi OWFS[1134]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 14:14:05 raspberrypi systemd[1]: owserver.service: Failed with > result 'protocol'. > Jul 18 14:14:05 raspberrypi systemd[1]: Failed to start Backend server > for 1-wire control. > Jul 18 14:14:05 raspberrypi systemd[1]: owserver.service: Service > RestartSec=100ms expired, scheduling restart. > Jul 18 14:14:05 raspberrypi systemd[1]: owserver.service: Scheduled > restart job, restart counter is at 1. > Jul 18 14:14:05 raspberrypi systemd[1]: Stopped Backend server for > 1-wire control. > Jul 18 14:14:05 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > Jul 18 14:14:05 raspberrypi OWFS[1178]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 14:14:05 raspberrypi systemd[1]: Started Backend server for > 1-wire control. > Jul 18 14:14:07 raspberrypi systemd[1]: Reloading. > Jul 18 14:17:01 raspberrypi CRON[1256]: pam_unix(cron:session): session > opened for user root by (uid=0) > Jul 18 14:17:01 raspberrypi CRON[1260]: (root) CMD ( cd / && run-parts > --report /etc/cron.hourly) > Jul 18 14:17:01 raspberrypi CRON[1256]: pam_unix(cron:session): session > closed for user root > Jul 18 14:17:34 raspberrypi systemd[1]: Stopping Backend server for > 1-wire control... > Jul 18 14:17:34 raspberrypi systemd[1]: owserver.service: Succeeded. > Jul 18 14:17:34 raspberrypi systemd[1]: Stopped Backend server for > 1-wire control. > Jul 18 14:17:56 raspberrypi OWFS[1282]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 14:27:04 raspberrypi systemd[1]: Starting Cleanup of Temporary > Directories... > Jul 18 14:27:04 raspberrypi systemd[1]: systemd-tmpfiles-clean.service: > Succeeded. > Jul 18 14:27:04 raspberrypi systemd[1]: Started Cleanup of Temporary > Directories. > > > > pi@raspberrypi:~ $ journalctl -xe > Jul 18 12:23:24 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > -- Subject: A start job for unit owserver.service has begun execution > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has begun execution. > -- > -- The job identifier is 320. > Jul 18 12:23:24 raspberrypi OWFS[944]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 12:23:24 raspberrypi systemd[1]: owserver.service: Failed with > result 'protocol'. > -- Subject: Unit failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- The unit owserver.service has entered the 'failed' state with result > 'protocol'. > Jul 18 12:23:24 raspberrypi systemd[1]: Failed to start Backend server > for 1-wire control. > -- Subject: A start job for unit owserver.service has failed > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has finished with a failure. > -- > -- The job identifier is 320 and the job result is failed. > Jul 18 12:23:24 raspberrypi systemd[1]: owserver.service: Service > RestartSec=100ms expired, scheduling restart. > Jul 18 12:23:25 raspberrypi systemd[1]: owserver.service: Scheduled > restart job, restart counter is at 1. > -- Subject: Automatic restarting of a unit has been scheduled > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- Automatic restarting of the unit owserver.service has been scheduled, > as the result for > -- the configured Restart= setting for the unit. > Jul 18 12:23:25 raspberrypi systemd[1]: Stopped Backend server for > 1-wire control. > -- Subject: A stop job for unit owserver.service has finished > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A stop job for unit owserver.service has finished. > -- > -- The job identifier is 377 and the job result is done. > Jul 18 12:23:25 raspberrypi systemd[1]: Starting Backend server for > 1-wire control... > -- Subject: A start job for unit owserver.service has begun execution > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has begun execution. > -- > -- The job identifier is 377. > Jul 18 12:23:25 raspberrypi OWFS[952]: DEFAULT: ow_daemon.c:(144) > Entered background mode, quitting. > Jul 18 12:23:25 raspberrypi systemd[1]: Started Backend server for > 1-wire control. > -- Subject: A start job for unit owserver.service has finished successfully > -- Defined-By: systemd > -- Support: https://www.debian.org/support > -- > -- A start job for unit owserver.service has finished successfully. > -- > -- The job identifier is 377. > Jul 18 12:23:26 raspberrypi systemd[1]: Reloading. > Jul 18 12:23:28 raspberrypi sudo[700]: pam_unix(sudo:session): session > closed for user root > > > > On 16.07.2019 22:43, Colin Law wrote: > > On Tue, 16 Jul 2019 at 19:08, Jaroslav Sobota <jsob...@kky.zcu.cz> > wrote: > >> > >> Creating config file /etc/owfs.conf with new version > >> Setting up libow-3.2-3:armhf (3.2p3+dfsg1-2) ... > >> Setting up owserver (3.2p3+dfsg1-2) ... > >> Job for owserver.service failed because the service did not take the > >> steps requi red by its unit > >> configuration. > >> See "systemctl status owserver.service" and "journalctl -xe" for > details. > > > > Not certain, but I think it installed ok, but failed to start. Did > > you run the commands suggested to see what it says? Perhaps you just > > need to setup the config properly. > > > > Colin > > > > > > _______________________________________________ > > Owfs-developers mailing list > > Owfs-developers@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > > > > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers >
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
