On 24.11.2015 18:57, Johan Ström wrote: >> > > Great! For you git new-comers, 'git pull' will most likely not work > properly here (due to rebase). I suggest a new checkout (git clone > https://github.com/M-o-a-T/owfs.git)
A faster way to do the same thing is: $ git fetch $ git reset --hard origin/master >> > * after some hours, owserver doesn't react any more >> > * restarting it doesn't work, still hangs >> > * run owserver under strace, it works >> > * restart it normally, still works >> > * repeat > I *may* have had similar on my owfs running on FreeBSD. In my case I've > been able to reset it by totally pulling the power from the bus, then > restoring it a few seconds later (after all devices have discharged). I > haven't seen this since i replaced a old-owslave device with new > moat-based though, but need a few more months of proper operation to > reliably claim that was the issue... > Don't quite remember how owserver acted though, but I think it tried to > do searches which just timed out.. > > Some ideas: > > * Does --traffic output give any hints? Is it totally dead, or > communicating with controller? I don't know, will test by running it under screen or quivalent. > * Tried disconnecting the physical network? > No, since (a) it's inside a utility closet and (b) the "strace" method works. > Regarding strace, do you mean that killing owserver and starting it does > not help, but killing it and then restarting it under strace DOES help? > Not reliably. Killing it (systemctl stop), running it manually under strace, killing *that* (assuming it doesn't segfault then, which it sometimes does) and then restarting it (via systemctl start) always works. I've tried gdb, but the stack traces are inconclusive. I've seen anecdotal evidence suggesting that this problem started sometime after 2.9, but "git bisect"ing that far back would take a couple of months -- as it sometimes does run a week before crashing again. I've tried running owserver under valgrind. *Yowch*. Something's very wrong if you see that many "you used uninitialized memory" messages, but I suspect that's a buggy valgrind/ARM. I really should do this on a x86 box. -- Matthias ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
