Updates while server not running, "simultaneous" kills it?
Loren Amelang <loren <at> pacific.net>
2014-10-26 22:55:47 GMT
Your comment about "two processes competing for the same resource" made me think of my random problem with
temperature values of "-62". My config file is just like the one at:
Except I (thought I had) commented the "server: FAKE = DS18S20,DS2405" line,
and added "server: w1" right under the "#server: usb = all" line.
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:4304
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
! server: FAKE = DS18S20,DS2405
# USB device: DS9490
#server: usb = all
I think I just learned something... The manpage says:
server: opt = value # only owserver effected by this line
! server: opt = value # owserver NOT effected by this line
What I missed until now is that "! server:" apparently DOES apply to everything BUT owserver. That makes
sense of the first command copied above - it tells everyone except server to read from server.
When I took '!' for another type of comment character, and used it before "server: FAKE = DS18S20,DS2405" it
didn't stop the fake devices from appearing. So that has been telling everybody except owserver to read
the fake devices directly... But owserver was not reading them, so not a resource competition? And they
shouldn't affect the real hardware devices? Changing "!" to '#' and "sudo service owhttpd restart" has
eliminated the fake devices.
When I added "server: w1", it did cause owserver (or someone) to read my configured BBB hardware pin. So I
guess that must be correct.
While poking around the http display, I notice:
All the other error counts are 0.
This is with:
tries.ALL 492, 6, 6
Still the same 58 errors at 524 reads. I can't find any explanation of what NET_connection_errors are. Or
why tries.ALL is always 8 more than calls... Or the difference between tries.0/1/2?
New issue... For no obvious reason (but see below), the real devices disappeared from the web page, and
after a few more tries the web page refused to load. The filesystem is still visible and temperatures are
still being updated, but apparently both server and httpd are gone:
root <at> arm:/home/ubuntu# /etc/init.d/owhttpd status
* owhttpd is not running
root <at> arm:/home/ubuntu# /etc/init.d/owserver status
* owserver is not running
When I first tried to restart http using sudo, it gave no error, but didn't work.
ubuntu <at> arm:~$ sudo service owhttpd stop
* Stopping 1-Wire HTTP Daemon owhttpd [ OK ]
ubuntu <at> arm:~$ sudo service owhttpd start
* Starting 1-Wire HTTP Daemon owhttpd [ OK ]
ubuntu <at> arm:~$ sudo service owhttpd status
* owhttpd is not running
Maybe it won't start if server is not running? When I switched to real root and started server first, it
--> BUT - if owserver is the only module that reads actual hardware devices, and it was not running, who was
maintaining the filesystem and updating the temperatures?
At the "top" of the http page, only bus.0 shows. But if I click bus.0, the new page shows bus.1 as well, and it
appears my real devices are on bus.1. What does this mean?
Also on that bus.0 page (and on the top page) is "simultaneous":
present Error: Input/output error
present_ds2400 Error: Software caused connection abort
single Error: Software caused connection abort
single_ds2400 Error: Software caused connection abort
temperature Error: Software caused connection abort
voltage Error: Software caused connection abort
Aha! Visiting that page kills owserver! That's what made the page loads fail earlier. At least now I know
what not to do...
Sorry if these are all obvious newbie questions,
| Loren Amelang | loren <at> pacific.net |
> 3. Re: Missing data (Paul Alfille)
> Date: Sun, 26 Oct 2014 07:12:41 -0400
> From: Paul Alfille <paul.alfille <at> gmail.com>
> Subject: Re: [Owfs-developers] Missing data
> To: "OWFS (One-wire file system) discussion and help"
> <owfs-developers <at> lists.sourceforge.net>
> <CAP_SGzeYU0Aabs5kLnPW=n4t0TOaU8jNFzJs6L1MdMn8NFfH9A <at> mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> Well there's always the possibility that there is a wiring problem, but
> also there could be two processes competing for the same resource.
> Is owserver and owfs running at the same time? Your configuration file
> would have them both grabbing the same serial devices and stepping on each
> If they both run at the same time, owfs should connect to owserver and
> have owserver make the exclusive hardware connection.