Re: [Owfs-developers] Problems

[Matt]

Thanks Paul.   I’ll try the ./configure --disable-owtcl technique next week.   Regarding owserver issue, this is all via command line.   ./owserver -d /dev/ttyS0 -p 3001 --error_level 4 26941 ttyS0    Ss+    0:00 ./owserver -d /dev/ttyS0 -p 3001 --error_level 4   snmpmgr:/opt/owfs/bin# ./owdir -s 3001 / bus.0 settings system statistics /26.F6DC80000000 /26.415281000000 /01.061C640B0000   It finds my devices, but owserver is now no longer running.   Here are the entries in syslog   Nov  5 16:54:05 snmpmgr OWFS[27841]: PARSENAME path=[] Nov  5 16:54:08 snmpmgr OWFS[27841]: owserver: parse path=/ Nov  5 16:54:08 snmpmgr OWFS[27841]: PARSENAME path=[/] Nov  5 16:54:08 snmpmgr OWFS[27841]: Directory message Nov  5 16:54:08 snmpmgr OWFS[27841]: DIRECTORY path=/ Nov  5 16:54:08 snmpmgr OWFS[27841]: Starting Library cleanup Nov  5 16:54:08 snmpmgr OWFS[27841]: Closing Cache Nov  5 16:54:08 snmpmgr OWFS[27841]: Closing input devices Nov  5 16:54:08 snmpmgr OWFS[27841]: Cannot restore port attributes: /dev/ttyS0 : Input/output error Nov  5 16:54:08 snmpmgr OWFS[27841]: Closing outout devices     Here’s what happens if I run with --foreground snmpmgr:/opt/owfs/bin# ./owserver -d /dev/ttyS0 -p 3001 --error_level 4 --foreground    CALL: PARSENAME path=[] ServerAddr: [(null)] [3001]    CALL: owserver: parse path=/    CALL: PARSENAME path=[/]    CALL: Directory message    CALL: DIRECTORY path=/    CALL: owserver: parse path=/    CALL: PARSENAME path=[/]    CALL: Directory message    CALL: DIRECTORY path=/   Works fine, and I can repeat queries.   I’ll recompile and try again.   Thanks From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Alfille Sent: Sunday, 5 November 2006 12:18 AM To: owfs-developers@lists.sourceforge.net Subject: Re: [Owfs-developers] Problems   Looks like owtcl problem (and no libusb) If you aren't going to use owtcl, try ./configure --disable-owtcl I'm perplexed by the owserver in background problem. Is it being loaded from the command line, or within the nagios system. Perhaps Nagios doesn't allow owserver to fork into the background? Paul Alfille On 11/4/06, Matt <[EMAIL PROTECTED]> wrote: Hi, I've been trying to integrate owfs with my Nagios (www.nagios.org) installation at work this week and have had a few problems. The system is Debian Sarge, kernel 2.6.8. I run ./configure in the owfs-2.5p5 folder, this seems to complete ok. Ends with : Current configuration:     Deployment location: /opt/owfs Compile-time options:                   Caching is enabled                       USB is DISABLED                       I2C is enabled                    HA7Net is enabled            Multithreading is enabled     Parallel port DS1410E is enabled         TAI8570 barometer is enabled              Thermocouple is enabled              Debug-output is enabled                 Profiling is DISABLED        Zeroconf (Bonjour) is DISABLED Module configuration:         owfs is enabled      owhttpd is enabled       owftpd is enabled     owserver is enabled       owcapi is enabled         swig is enabled       owperl is enabled        owphp is DISABLED     owpython is enabled        owtcl is DISABLED <snip>

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers