I don't run mine under systemd, however; If I run through the same
install process as above, on a machine that has systemd installed I
get the same error as you IF I don't have the USB module plugged in
when I attempt to start it.

So, is yours plugged in when you do the install or attempt the restart?

If it is plugged in, I'm out of ideas as googling "owserver.service:
Failed with result 'protocol'." doesn't turn up much that appears
relevant.

On 19/07/2019, vigilancewx <vigilanc...@gmail.com> wrote:
> Hi Glenn
>
> thanks for helping out
>
> Tried the following but still getting errors
>
> sudo apt upate
> sudo apt upgrade
> sudo apt install owserver ow-shell
> /etc/owfs.conf
> file updated
>
>
>
>
> pi@raspberrypi:~ $ sudo apt install owserver ow-shell
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
> required:
>   libboost-system1.62.0 libboost-thread1.62.0 libreoffice-gtk2
> Use 'sudo apt autoremove' to remove them.
> The following additional packages will be installed:
>   libftdi1-2 libow-3.2-3 owfs-common
> The following NEW packages will be installed:
>   libftdi1-2 libow-3.2-3 ow-shell owfs-common owserver
> 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
> Need to get 375 kB of archives.
> After this operation, 1,348 kB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://archive-bm.raspbian.org/raspbian buster/main armhf libftdi1-2
> armhf 1.4-1+b2 [27.7 kB]
> Get:2 http://archive-bm.raspbian.org/raspbian buster/main armhf owfs-common
>
> all 3.2p3+dfsg1-2 [17.6 kB]
> Get:3 http://archive-bm.raspbian.org/raspbian buster/main armhf libow-3.2-3
>
> armhf 3.2p3+dfsg1-2 [269 kB]
> Get:4 http://archive-bm.raspbian.org/raspbian buster/main armhf ow-shell
> armhf 3.2p3+dfsg1-2 [29.8 kB]
> Get:5 http://archive-bm.raspbian.org/raspbian buster/main armhf owserver
> armhf 3.2p3+dfsg1-2 [30.8 kB]
> Fetched 375 kB in 6s (59.2 kB/s)
> Selecting previously unselected package libftdi1-2:armhf.
> (Reading database ... 140620 files and directories currently installed.)
> Preparing to unpack .../libftdi1-2_1.4-1+b2_armhf.deb ...
> Unpacking libftdi1-2:armhf (1.4-1+b2) ...
> Selecting previously unselected package owfs-common.
> Preparing to unpack .../owfs-common_3.2p3+dfsg1-2_all.deb ...
> Unpacking owfs-common (3.2p3+dfsg1-2) ...
> Selecting previously unselected package libow-3.2-3:armhf.
> Preparing to unpack .../libow-3.2-3_3.2p3+dfsg1-2_armhf.deb ...
> Unpacking libow-3.2-3:armhf (3.2p3+dfsg1-2) ...
> Selecting previously unselected package ow-shell.
> Preparing to unpack .../ow-shell_3.2p3+dfsg1-2_armhf.deb ...
> Unpacking ow-shell (3.2p3+dfsg1-2) ...
> Selecting previously unselected package owserver.
> Preparing to unpack .../owserver_3.2p3+dfsg1-2_armhf.deb ...
> Unpacking owserver (3.2p3+dfsg1-2) ...
> Setting up libftdi1-2:armhf (1.4-1+b2) ...
> Setting up owfs-common (3.2p3+dfsg1-2) ...
>
> Creating config file /etc/owfs.conf with new version
> Setting up ow-shell (3.2p3+dfsg1-2) ...
> 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
> required by its unit configuration.
> See "systemctl status owserver.service" and "journalctl -xe" for details.
> invoke-rc.d: initscript owserver, action "start" failed.
> ● owserver.service - Backend server for 1-wire control
>    Loaded: loaded (/lib/systemd/system/owserver.service; disabled; vendor
> preset: enabled)
>    Active: activating (auto-restart) (Result: protocol) since Thu
> 2019-07-18 15:55:14 BST; 28ms ago
>      Docs: man:owserver(1)
>   Process: 8854 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited,
>
> status=0/SUCCESS)
>  Main PID: 8854 (code=exited, status=0/SUCCESS)
> dpkg: error processing package owserver (--configure):
>  installed owserver package post-installation script subprocess returned
> error exit status 1
> Processing triggers for man-db (2.8.5-2) ...
> Processing triggers for libc-bin (2.28-10+rpi1) ...
> Processing triggers for systemd (241-5+rpi1) ...
> Errors were encountered while processing:
>  owserver
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> pi@raspberrypi:~ $ sudo nano /etc/owfs.conf/
> pi@raspberrypi:~ $ sudo nano /etc/owfs.conf
>
> then
> /etc/init.d/owserver status return
>
>
> pi@raspberrypi:~ $ /etc/init.d/owserver status
> ● owserver.service - Backend server for 1-wire control
>    Loaded: loaded (/lib/systemd/system/owserver.service; disabled; vendor
> preset: enabled)
>    Active: failed (Result: protocol) since Thu 2019-07-18 16:02:44 BST;
> 1min 45s ago
>      Docs: man:owserver(1)
>   Process: 9530 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited,
>
> status=0/SUCCESS)
>  Main PID: 9530 (code=exited, status=0/SUCCESS)
>
> Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Service
> RestartSec=100ms expired, scheduling restart.
> Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Scheduled restart
>
> job, restart counter is at 5.
> Jul 18 16:02:44 raspberrypi systemd[1]: Stopped Backend server for 1-wire
> control.
> Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Start request
> repeated too quickly.
> Jul 18 16:02:44 raspberrypi systemd[1]: owserver.service: Failed with
> result 'protocol'.
> Jul 18 16:02:44 raspberrypi systemd[1]: Failed to start Backend server for
> 1-wire control.
> pi@raspberrypi:~ $ ^C
>
>
>
>
>
>
>
> On Thursday, July 18, 2019 at 8:55:42 AM UTC+1, vigilancewx wrote:
>>
>> I have used OWFS service for a few years and its worked flawlessly
>>
>> I am trying to get it to work on a new PI4 but i cant get to read any
>> sensors
>>
>>
>> I have followed the owfs service installation guide as in the past
>>
>>
>>
>>
>> pi@raspberrypi:~/Myideas $ sudo PYTHONPATH=/home/weewx/bin python
>> /home/weewx/bin/user/owfs.py --sensors
>> Traceback (most recent call last):
>>   File "/home/weewx/bin/user/owfs.py", line 618, in <module>
>>     main()
>>   File "/home/weewx/bin/user/owfs.py", line 578, in main
>>     ow.init(iface)
>>   File "/usr/lib/python2.7/dist-packages/ow/__init__.py", line 221, in
>> init
>>     raise exNoController
>> ow.exNoController
>>
>> Previously i  think the only time i have had the above error is when i
>> have forgotten to plug the dalas adapter in to a USB port
>>
>> it appears the service cant read my usb port
>>
>> from the syslog file
>> Jul 18 08:29:44 raspberrypi OWFS[3132]: DEFAULT: owlib.c:(208) Cannot open
>>
>> USB bus master
>> Jul 18 08:29:44 raspberrypi OWFS[3132]: DEFAULT: owlib.c:(52) No valid
>> 1-wire buses found
>>
>> but the device is connected
>>
>>
>> pi@raspberrypi:~/Myideas $ lsusb
>> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 001 Device 003: ID 04fa:2490 Dallas Semiconductor DS1490F 2-in-1 Fob,
>>
>> 1-Wire adapter
>> Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> pi@raspberrypi:~/Myideas $
>>
>>
>> any ideas how to read the senors??
>>
>> thanks for any help
>>
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9fb91704-7d3f-4c57-b16c-ec4065b70552%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAAraAzhcBrx_aVdB8CA8EW3SExcVPLfMuuB8tSAoeL4harWVwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to