owserver ran fine for a day or so, then I began to see random device dropouts on one bus. This went on for nearly an hour before I noticed and killed owserver. At that time most devices on that bus were unreadable. Restarting it fixed the problem.
I have a full trace, but it's big, about 1GB. bzip2'd it's 16MB and it can be downloaded here: http://voksenlia.net/owserver.log.bz2 Note that the end includes about half a minute of a new owserver session after I killed the original. A backward search for "exit_handler" from the end will take you back to the failing owserver session, and before that the log should show that something is wrong. The "broken" bus was bus.2 (assuming that the restart did not change the bus numbering). Anyway, the devices on the bus were: 10.53F652010800 28.CCA131000000 28.FA9831000000 28.56747E010000 28.856C31000000 28.6D6B31000000 28.ED7715000000 28.1D437E010000 26.396385000000 26.3F4AB5000000 1D.9E220A000000 1D.311B09000000 So the question is why couldn't owserver read the values of these? No problems were logged in the syslog. Please let me know if there is anything I can do to debug this. The cases when owserver simply dies are easy to work around as I can have owserver restart automatically. Device dropouts can more easily go undetected for a while. A possible workaround is to kill owserver every X minutes automatically to ensure that the error isn't allowed to stay active very long. I run owserver this way: owserver -uall -p 3000 --foreground --error_level=9 --error_print 2 I have 16 DS9490R adapters connected. owserver 2.8p13. -Steinar Steinar Midtskogen <[email protected]> writes: > Unfortunetaly, owserver only ran a few hours this way and died. I'll > try to get some debug info. > > -Steinar > > Steinar Midtskogen <[email protected]> writes: > >> Paul Alfille <[email protected]> writes: >> >>> I just tried 7 DS9490R adapters (all I had at hand). Worked well. >> ... >>> I believe that the only limit of adapters is libusb and the USB protocol. >>> owserver puts all the adapters in linked list of effectively unlimited >>> size. >> >> I've now tried a setup with 15 adapters (will become 18 when I'm >> done). At first I wasn't able to get owserver to see more than 8-9 >> adapters at a time. If I added more than that, either it didn't >> appear, or it appeared but another adapter disappeared. But all >> devices showed up in the system log. >> >> I was using two 10 port USB hubs, one connected to the other. Then I >> tried to connect both hubs directly to the computer, i.e. flattening >> the USB bus hierarchy, and this made owserver see everything. >> >> Do you think this is an owserver issue or a usblib issue? > > -- > Steinar > > > ------------------------------------------------------------------------------ > Get a FREE DOWNLOAD! and learn more about uberSVN rich system, > user administration capabilities and model configuration. Take > the hassle out of deploying and managing Subversion and the > tools developers use with it. > http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > Owfs-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------------ FREE DOWNLOAD - uberSVN with Social Coding for Subversion. Subversion made easy with a complete admin console. Easy to use, easy to manage, easy to install, easy to extend. Get a Free download of the new open ALM Subversion platform now. http://p.sf.net/sfu/wandisco-dev2dev _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
