Okay, I understand that Buster install is a bit wonky...
I don't really understand why mine is so troublesome.
I have tried to load the right modules but it seems it's hard to get
anything right now..
*/etc/modprobe.d/raspi-blacklist.conf * - empty
*lsmod | grep i2c*
i2c_bcm2708 16384 0
i2c_dev 20480 0
i2c_bcm2835 16384 0
*owfs.conf* - server: device=/dev/i2c-1
*sudo /usr/bin/owserver -c /etc/owfs.conf --debug*
DEBUG MODE
libow version:
3.2p3
DEBUG: ow_daemon.c:(170) main thread id = 3070111472
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
isn't found
CALL: ow_parsename.c:(174) path=[]
DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
adapters)
DEBUG: ow_regex.c:(24) Reg Ex expression <^$> compiled to 0xb6fa860c
DEBUG: ow_regex.c:(24) Reg Ex expression <^all$> compiled to 0xb6fa862c
DEBUG: ow_regex.c:(24) Reg Ex expression <^scan$> compiled to 0xb6fa864c
DEBUG: ow_regex.c:(24) Reg Ex expression <^\*$> compiled to 0xb6fa866c
DEBUG: ow_regex.c:(24) Reg Ex expression
<^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$>
compiled to 0xb6fa868c
DEBUG: ow_regex.c:(24) Reg Ex expression <^-?[[:digit:]]+$> compiled to
0xb6fa86ac
]*$> compiled to 0xb6fa86ccg Ex expression <^ *([^ ]+)[
]*$> compiled to 0xb6fa86ecg Ex expression <^ *([^ ]+) *: *([^ ]+)[
]*$> compiled to 0xb6fa870cg Ex expression <^ *([^ ]+) *: *([^ ]+) *: *([^
]+)[
DEBUG: ow_regex.c:(53) Not found
DEBUG: ow_regex.c:(53) Not found
DEBUG: ow_regex.c:(100) 0: 0->10 found <></dev/i2c-1><>
DEBUG: ow_regex.c:(100) 1: 0->10 found <></dev/i2c-1><>
DEBUG: ow_parse_address.c:(87) Text </dev/i2c-1>
DEBUG: ow_parse_address.c:(142) First </dev/i2c-1>
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 19
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1A
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1B
DEBUG: ow_ds2482.c:(516) ok
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1C
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1D
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1E
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1F
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F cannot be
reset. Not a DS2482.
DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on /dev/i2c-1
DEFAULT: owlib.c:(52) No valid 1-wire buses found
DEBUG: ow_exit.c:(17) Exit code = 1
CALL: ow_lib_close.c:(21) Starting Library cleanup
CALL: ow_lib_stop.c:(22) Clear Cache
DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
CALL: ow_lib_stop.c:(24) Closing input devices
CALL: ow_lib_stop.c:(26) Closing output devices
CALL: ow_lib_close.c:(42) Finished Library cleanup
DEBUG: ow_lib_close.c:(50) Libraries closed
So, is it strange or did I not load the right modules?
the i2c module card I have attached to my raspberry is:
https://en.m.nu/adapters-network-managment/r-pi-i2c-1wire-expansion-module-v11
Let me know your thoughts!
I'm dying to get this network up and working again.
//Robert
[image: Linkedin] <http://de.linkedin.com/in/rlagus> *Robert Lagus*
+358 (0)40 662 44 99
rob...@lagus.net
On Tue, 17 Sep 2019 at 23:31, Stefano Miccoli via Owfs-developers <
owfs-developers@lists.sourceforge.net> wrote:
>
>
> On 17 Sep 2019, at 14:35, Robert Lagus <rob...@lagus.net> wrote:
>
> I tried to start the ofserver with:
> *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.
>
>
> You have two independent problems:
>
> 1) the ds2482 is not found by owserver. You should first debug this
> problem starting owserver manually:
> sudo /usr/bin/owserver -c /etc/owfs.conf --debug
>
> 2) the owserver.service unit file on buster is problematic.
>
>
> I cannot give you advice on 1), but I have solved 2) with a drop-in unit
> configuration file. I run owserver on an headless server with the following
> configuration.
>
> *$* sudo systemctl cat owserver.service
> *# /lib/systemd/system/owserver.service*
> [Unit]
> Description=Backend server for 1-wire control
> Documentation=man:owserver(1)
>
> [Service]
> Type=notify
> NotifyAccess=all
> ExecStart=/usr/bin/owserver -c /etc/owfs.conf
> Restart=on-failure
> #User=Debian-ow
> #Group=Debian-ow
>
> [Install]
> WantedBy=multi-user.target
> Also=owserver.socket
>
> *# /etc/systemd/system/owserver.service.d/override.conf*
> [Service]
> User=Debian-ow
> Group=Debian-ow
> ExecStart=
> ExecStart=/usr/bin/owserver -c /etc/owfs.conf --foreground
>
> [Install]
> Also=
>
>
> A long story short.
>
> /lib/systemd/system/owserver.service is the system file shipped with
> Buster, and it did not work for me out of the box.
> /etc/systemd/system/owserver.service.d/override.conf is an override file,
> that you create with `sudo systemctl edit owserver.service`.
>
> My changes with respect to the shipped configuration.
>
> 1) Do not run the server as root. I use an USB adapter, and I wrote a
> couple of udev rules to change the ttyUSBxx group to Debian-ow and symlink
> it to a persistent /dev node. Skip this if you plan to run owserver with
> root privileges. (I’m not sure, but I think that root privileges are
> necessary to access the i2c bus.)
>
> 2) Add the the --foreground option to the owserver command. This is
> crucial for starting owserver under systemctl without socket activation.
>
> 3) Disable socket activation. I expect the owserver service to start at
> boot, before that the first client connects, so socket activation is not
> needed. I found that in edge conditions socket activation may interfere
> with the correct startup, therefore I prefer to disable it.
>
>
> Bye
>
> S.
>
>
>
> _______________________________________________
> 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
