Protocol Error Starting owserver

[Wt Riker]

I have installed owfs on my Pi4 platform. However, I am unable to start owserver as I get this error in journalctl:

-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit owserver.service has finished.
--
-- The job identifier is 1564 and the job result is done.
May 03 10:58:37 raspberrypi systemd[1]: owserver.service: Start request repeated too quickly.
May 03 10:58:37 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'.
May 03 10:58:37 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 1564 and the job result is failed.
May 03 10:58:51 raspberrypi sudo[1632]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xe
May 03 10:58:51 raspberrypi sudo[1632]: pam_unix(sudo:session): session opened for user root by (uid=0)

The message itself is virtually useless (to me) but my search turned up one thing here but that suggestion did not work. Can someone help me with this? TIA.

[Glenn McKechnie]

This has come up a few times and the solution remains ... vague and mysterious.
It's possibly a systemd issue, but we'll try a few other things in the meantime.

Have you setup and used owserver before?

Do you have a working /etc/owfs.conf or are you using the supplied default?

Are you running the kernel 1-wire module available through
raspi-config (if so turn it off and see if the service will start.)

What does the following command return...

sudo /usr/bin/owserver -c /etc/owfs.conf --debug

If you need to send that output to the list then

sudo /usr/bin/owserver -c /etc/owfs.conf --debug >> /tmp/owservdebug.txt

and attach /tmp/owservdebug.txt

On 04/05/2020, Wt Riker <wtrik...@gmail.com> wrote:
> I have installed owfs on my Pi4 platform. However, I am unable to start
> owserver as I get this error in journalctl:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

> *-- Defined-By: systemd-- Support: https://www.debian.org/support-- -- A
> stop job for unit owserver.service has finished.-- -- The job identifier is
>
> 1564 and the job result is done.May 03 10:58:37 raspberrypi systemd[1]:
> owserver.service: Start request repeated too quickly.May 03 10:58:37

> 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'.May 03 10:58:37 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
> 1564 and the job result is failed.May 03 10:58:51 raspberrypi

> sudo[1632]: pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ;

> COMMAND=/bin/journalctl -xeMay 03 10:58:51 raspberrypi sudo[1632]:
> pam_unix(sudo:session): session opened for user root by (uid=0)*

>
> The message itself is virtually useless (to me) but my search turned up one
>
> thing here but that suggestion did not work. Can someone help me with this?
>
> TIA.
>

> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/6218f9b4-1cb9-43c8-aef5-6699802b085a%40googlegroups.com.
>


--


Cheers
Glenn

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

[Wt Riker]

Thanks for the reply, It appears that this will continue to be mysterious. See embedded comments.

On Sunday, May 3, 2020 at 6:30:10 PM UTC-4, Glenn McKechnie wrote:

This has come up a few times and the solution remains ... vague and mysterious.
It's possibly a systemd issue, but we'll try a few other things in the meantime.

Have you setup and used owserver before?

No. 

Do you have a working /etc/owfs.conf or are you using the supplied default?

I modified the system default. It is attached. 

Are you running the kernel 1-wire module available through
raspi-config (if so turn it off and see if the service will start.)

It has been disabled. 

What does the following command return...

 sudo /usr/bin/owserver -c /etc/owfs.conf --debug

Oddly it outputs nothing 

[Glenn McKechnie]

On 04/05/2020, Wt Riker <wtrik...@gmail.com> wrote:

[...]

>> Have you setup and used owserver before?
>>
> No.

Okay, so no working config. Starting from scratch

>> Do you have a working /etc/owfs.conf or are you using the supplied
>> default?

> I modified the system default. It is attached.

There are a few things that are amiss there.

You have 2 device entries in owfs.conf

# USB device: DS9490

server: device = /dev/ic2-1

# Serial port: DS9097

server: device = /dev/ttyAMA0

Which one is it?
What do you have as an interface between the pi and the 1-wire
network? That is a crucial piece of missing information.

Also a DS9490R (the blue usb dongle) should be ...
server: usb = all

comment out the !server entry...
#! server: server = localhost:4304

select an appropriate device entry, choose one of ...
server: device = /dev/ic2-1
or
server: device = /dev/ttyAMA0
or
server: usb = all
comment out the remainder.

specify the port as 4304 ie:- no localhost in the string...

server: port = 4304

>> What does the following command return...
>>
>> sudo /usr/bin/owserver -c /etc/owfs.conf --debug

With those changes made, what happens this time ?

>> If you need to send that output to the list then

>> sudo /usr/bin/owserver -c /etc/owfs.conf --debug >> /tmp/owservdebug.txt

>> and attach /tmp/owservdebug.txt