On 25/08/16 06:59, Andy Carter wrote: > On Wednesday 24 Aug 2016 23:46:20 Jan Kandziora wrote: >> Am 24.08.2016 um 20:47 schrieb Nigel Titley: >>> I'm carrying on investigations but I'm running out of ideas. Can anyone >>> make a suggestion? >> Check whether the network is up and thus, the enet device reachable at >> the moment owserver is started. Otherwise it may just fail or be stuck. > There is an option in raspi-config 'Wait for network' which delays boot until > the network is up > > Perhaps setting this would help - depending on when owserver starts of course > This is a possibility and it had crossed my mind that this might be the issue but it doesn't explain why a subsequent attempt to start it from the command line fails. Is there cleanup that "owserver stop" does that would explain this behaviour? I can only see it cleaning up the pid file and there is no pid file after the failed start at boot.
I'll try switching on error reporting and see if I can get a clue about what's happening into the log. I'll get back when/if I get something Thanks for your responses Nigel ------------------------------------------------------------------------------ _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
