Roberto, Thank you for the clue about "/etc/init.d/owserver status" sometimes being unreliable. I suspect "sudo service owserver status" might have the same issues?
I was double-checking those results with: ps -ef |grep 'owfs' root 1151 1 0 Oct19 ? 00:01:23 /usr/bin/owftpd -c /etc/owfs.conf --pid-file /var/run/owfs/owftpd.pid root 13064 1 0 14:44 ? 00:00:00 /usr/bin/owhttpd -c /etc/owfs.conf --pid-file /var/run/owfs/owhttpd.pid root 13605 1 0 15:27 ? 00:00:00 /usr/bin/owserver -c /etc/owfs.conf --pid-file /var/run/owfs/owserver.pid (That's after I successfully restarted both processes.) Mine always matched. It looked like owhttpd stopped serving pages a few minutes after owserver died, and would not work until owserver was running again. I guess your netstat check has the advantage of proving the server is actually listening on the network, rather than just running. Loren | Loren Amelang | lo...@pacific.net | > 1. Re: Updates while server not running, "simultaneous" kills > it? (Stefano Miccoli) > > Message: 1 > Date: Mon, 27 Oct 2014 00:39:18 +0100 > From: Stefano Miccoli <mo...@icloud.com> > Subject: Re: [Owfs-developers] Updates while server not running, > "simultaneous" kills it? > To: "OWFS (One-wire file system) discussion and help" > <owfs-developers@lists.sourceforge.net> > Message-ID: <6a591ccc-404a-477c-b1b3-5ae144b6d...@icloud.com> > Content-Type: text/plain; charset="us-ascii" > > > On 26 Oct 2014, at 23:55, Loren Amelang <lo...@pacific.net> wrote: > >> root@arm:/home/ubuntu# /etc/init.d/owhttpd status >> * owhttpd is not running >> root@arm:/home/ubuntu# /etc/init.d/owserver status >> * owserver is not running >> --- > > Don't trust too much the /etc/init.d scripts: sometimes they get confused > (at least on Debian+SysVinit; I have no experience with Ubuntu+Upstart). > I usually run (as root or with sudo) "netstat -tlp | grep 4304" to see if > there is an owserver listening. It was quite common for me to have a stale > owserver (not killed by repeated "/etc/init.d/owserver stop" calls) > preventing a fresh owserver from starting... In such cases killing by proc > number or "killall owserver" solved the problem. ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
