Page 1 of 1

Failed to start Backend server for 1-wire control

Posted: Sat Sep 14, 2019 8:03 pm
by micksulley
I have just done a fresh install of Buster and updated. I ran raspi-config and enabled 1-wire and i2c.
I have installed owserver ow-shell
At first it worked, I could see devices with owdir, but it has stopped working, owdir returns nothing
I have run "sudo systemctl enable owserver.service"
but I see -

Code: Select all

[email protected]:~ $ sudo systemctl status owserver.service
● owserver.service - Backend server for 1-wire control
   Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
   Active: failed (Result: protocol) since Fri 2019-09-13 21:47:16 BST; 48s ago
     Docs: man:owserver(1)
 Main PID: 493 (code=exited, status=0/SUCCESS)

Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Service RestartSec=100ms expired, scheduling 
Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Scheduled restart job, restart counter is at 
Sep 13 21:47:16 pi-solar-old systemd[1]: Stopped Backend server for 1-wire control.
Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Start request repeated too quickly.
Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Failed with result 'protocol'.
Sep 13 21:47:16 pi-solar-old systemd[1]: Failed to start Backend server for 1-wire control.
[email protected]:~ $ 
I have edited /boot/config.txt the only active lines are

Code: Select all

dtparam=i2c_arm=on
dtparam=audio=on
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
dtoverlay=w1-gpio
dtparam=i2c1=on
Restarting owserver gives me

Code: Select all

[email protected]:~ $ sudo systemctl restart owserver
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.
[email protected]:~ $ 
I have no idea what to do next, can anyone help please?
Thanks
Mick

Re: Failed to start Backend server for 1-wire control

Posted: Sat Sep 14, 2019 9:08 pm
by d_older
Hi Mick,

I did this a couple of nights ago on a ZeroW with Buster and got the same/very similar results (for a DS9490 USB controller).

After going through the "systemctl enable / start / stop/ disable" options I couldn't find anything obviously wrong.

I also couldn't find any solutions by searching.

However after leaving it enabled through probably about 5 or 6 boot it now starts reliably - no real idea why - my only suspicion is that its initialisation is based on init.d and it seems to take a couple of boot cycles to get the "automagic" conversion right.


Hope this helps,

Dave

Re: Failed to start Backend server for 1-wire control

Posted: Sat Sep 14, 2019 10:40 pm
by micksulley
Thanks for the reply Dave, at least it is not just me:)

I have just rebooted a couple of times, made no difference. I also tried reinstalling owserver and it shows an error -

Code: Select all

[email protected]:~ $ sudo apt-get reinstall owserver
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer required:
  rpi.gpio-common
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/30.8 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 38870 files and directories currently installed.)
Preparing to unpack .../owserver_3.2p3+dfsg1-2_armhf.deb ...
Unpacking owserver (3.2p3+dfsg1-2) over (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 "restart" failed.
● owserver.service - Backend server for 1-wire control
   Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: protocol) since Sat 2019-09-14 23:26:25 BST; 61ms ago
     Docs: man:owserver(1)
  Process: 601 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited, status=0/SUCCESS)
 Main PID: 601 (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 systemd (241-7~deb10u1+rpi1) ...
Errors were encountered while processing:
 owserver
E: Sub-process /usr/bin/dpkg returned an error code (1)
I have removed owserver and then installed again, this time it installed without the error message, but status still shows backend server not started and owdir does not work.

Any other ideas?

Re: Failed to start Backend server for 1-wire control - Fixed

Posted: Sun Sep 15, 2019 6:13 pm
by micksulley
OK I think I have fixed it. Looks like my /etc/owfs.conf file was screwed up. I was expecting it to have the default file with the fake server, but that wasn't there. I deleted that and created a new one and it is working again.

Re: Failed to start Backend server for 1-wire control - Fixed

Posted: Fri Nov 29, 2019 7:55 pm
by nattila
micksulley wrote:
Sun Sep 15, 2019 6:13 pm
OK I think I have fixed it. Looks like my /etc/owfs.conf file was screwed up. I was expecting it to have the default file with the fake server, but that wasn't there. I deleted that and created a new one and it is working again.
Hi Mick,
Could you please describe detailed how did you created a new conf file? It would help me a lot.
thanks

Re: Failed to start Backend server for 1-wire control

Posted: Mon Dec 02, 2019 9:56 am
by micksulley
Sorry I had missed this post.

I am running with a Sheepwalk adapter. A basic config file (/etc/owfs.conf) is
! server: server = localhost:4304
server: device=/dev/i2c-1 # for modern Pi's, very early ones use i2c-0

You can also test with a fake adapter with
server: fake=10.053C8A010800,10.2AFE89010800,10.90F889010800
where the id's can be anything and it reports random value reads.

There is a good startup guide on the Sheepwalk site
https://www.sheepwalkelectronics.co.uk/ ... ftware.php

Best of luck!