OWFS file system is not active

[Natrixz]

After the most recent update I suddenly get this warning;
2018-11-21 08:08:34,760 - WARNING - terrariumSensor - OWFS file system is not actve / installed on this device!
2018-11-21 08:08:34,764 - WARNING - terrariumSensor - Measured value None% from humidity sensor 'Rechts-Warm' is outside valid range 50.00% - 180.00% in 0.01454 seconds.
2018-11-21 08:08:34,897 - WARNING - terrariumSensor - OWFS file system is not actve / installed on this device!
2018-11-21 08:08:34,899 - WARNING - terrariumSensor - Measured value NoneC from temperature sensor 'Rechts-Warm' is outside valid range 15.00C - 40.00C in 0.00789 seconds.
2018-11-21 08:08:35,146 - WARNING - terrariumSensor - OWFS file system is not actve / installed on this device!
2018-11-21 08:08:35,148 - WARNING - terrariumSensor - Measured value NoneC from temperature sensor 'Midden' is outside valid range 15.00C - 40.00C in 0.00791

Curious as to what happend =)

[theyosh]

For OWFS there are a lot of changes.... but it is working for me... So lets see...

1. Which python version are you running
2. Is the process owserver running? Could be that it will not start at a reboot
3. Is there a port open at 4304: sudo netstat -tulpn | grep 4304

After sudo service owserver restart is there an owserver process and is it than working?

[Natrixz]

1. Old python 2.7 version (can upgrade if you want)
2. Yes it's running (see Appendix A)
3. Nope that one isn't....

Strangely after the owserver there isn't a 4304 either

Appendix A:
owserver.service - LSB: 1-wire TCP server
Loaded: loaded (/etc/init.d/owserver; generated; vendor preset: enabled)
Active: active (exited) since Wed 2018-11-21 08:20:09 CET; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 493 ExecStart=/etc/init.d/owserver start (code=exited, status=0/SUCCE
CGroup: /system.slice/owserver.service

Nov 21 08:20:07 terrarium01 systemd[1]: Starting LSB: 1-wire TCP server...
Nov 21 08:20:08 terrarium01 OWFS[547]: DEFAULT: ow_daemon.c:(144) Entered backgr
Nov 21 08:20:09 terrarium01 owserver[493]: Starting 1-Wire TCP Server: owserver
Nov 21 08:20:09 terrarium01 systemd[1]: Started LSB: 1-wire TCP server.

[theyosh]

And what give: sudo netstat -tulpn | grep owserver ?

[theyosh]

And what is in the /etc/owfs.conf? There should be a line like: server: port = localhost:4304

[theyosh]

The line: Active: active (exited) since Wed 2018-11-21 08:20:09 CET; 5min ago looks wrong.

I have Active: active (running) since Sun 2018-11-18 19:05:11 CET; 2 days ago I have state running and not exited.

so is ps fax | grep owserver give the output:
847 ? Ssl 6:26 /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid

[Natrixz]

sudo netstat -tulpn | grep owserver Strangely doesnt report anything...

However catting owfs.conf shows the correct line at the bottom

[Natrixz]

Hmmm perhaps my owfs controller died right before/during/after upgrade?
Everything else seems fine

[Natrixz]

The line: Active: active (exited) since Wed 2018-11-21 08:20:09 CET; 5min ago looks wrong.

I have Active: active (running) since Sun 2018-11-18 19:05:11 CET; 2 days ago I have state running and not exited.

so is ps fax | grep owserver give the output:
847 ? Ssl 6:26 /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid

ps fax | grep owserver
2316 pts/0 S+ 0:00 _ grep --color=auto owserver
So im thinking the controller has an issue (perhaps)

[theyosh]

Hmm this is strange. Then you should try to reinstall owhttpd and start that. If that does start, it should provide a web interface on port 2121 of your pi. It that is also not starting, we need to figure out how to debug this and see if it is indeed failing hardware. But that would be somehow strange after an update...

And could it be that my installer has changed your device settings in the /etc/owfs.conf settings?

And I noticed that systemd sucks with owserver. So make sure you run a couple of times service owserver stop to make sure it is stopped and dead... then do a restart or run manually the command" /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid

[Natrixz]

When I really make sure it's killed and then manually run the command, I get the same results (strangely enough)
I compared it to a different Pi that I haven't updated and the file in /etc/owfs.conf looks exactly the same.

When I get home in the afternoon I will swap out the hardware to see if that's the thing that failed.
I have both a new one and one in use I know works so thats an easy check.

[Natrixz]

Alright I’m officially clueless.
I switched the “broken” owfs device including breakout board and sensors to a different (working) Pia and it worked flawlessly. Switch a different owfs board and sensors to the non working pi and it didn’t work anymore either, tried a few things.
Reinstalled software in between three swaps, all working on the other two pi’s.
Got annoyed, tried purging and reinstalling stuff, nothing.
Went to cook dinner, drank coffee, figured I’d continue troubleshooting.
Plugged in the original setup for the I dunno 6-10th time and it worked...all other boards and sensors as well....
I officially have NO clue why it suddenly worked again because I rebooted at least 2-3 times before quitting without doing anything else.... (because i was trying the other boards and sensors)

[theyosh]

DO NOT TOUCH IT ANYMORE :) :) :)

But this is very strange.... I have had those situations also.... My experience is that they are rare... But again, I am not a hardware specialist... but I think it has to do with the electronics somehow..

[Natrixz]

Well I cloned the SD-card before doing anything, but I can't seem to replicate it on my other Pi, weird in itself...
Must have been residual power in some of the components or something....Can't imagine any other issue if it's not present on the cloned SD-card >.<'
It's still electronics in a very humid environment (sensors that is) so who knows.

[Natrixz]

Closing due to can't reproduce.