Nevermind the 2nd question either; I figured out what I did wrong (I specified the libdir s /usr/lib instead of /usr/lib64; this being an x86_64 platform). Seems fine now.
On Wed, Nov 5, 2008 at 4:19 PM, Joseph Borg <[EMAIL PROTECTED]> wrote: > Hi, > An update on this as I've spend all day playing with it: > > 1. It would seem one of the two ups's is bust (i.e. the one for which I got > the output below). I hope to connect it up with windows tomorrow to > confirm/deny this. > > 2. The other UPS seems ok in that the driver recognizes it: > ---snippet--- > Asking for UPS status [Q1]... > get_data_agiler: raw dump: (0 bytes) => > Q1 => OK [(230.0 230.0 302.0 012 50.0 26.2 32.0 00001000] > ---end snippet--- > However, I now have a problem loading upsmon (with 2.2.2) as it tell me the > following: > [EMAIL PROTECTED] bin]# upsmon > upsmon: error while loading shared libraries: libupsclient.so.1: cannot > open shared object file: No such file or directory > [EMAIL PROTECTED] bin]# locate libupsclient.so.1 > /home/joeborg/Download/nut-2.2.2/clients/.libs/libupsclient.so.1 > /home/joeborg/Download/nut-2.2.2/clients/.libs/libupsclient.so.1.0.0 > /usr/lib/libupsclient.so.1 > /usr/lib/libupsclient.so.1.0.0 > > Anyone has an ideas why upsmon is not finding libupsclient.so.1? > > I guess if I solve the above I'd have at least one ups up and running and > then maybe I can use the network to shutdown both pcs? > > Thanks, > > Joe > > > On Wed, Nov 5, 2008 at 10:15 AM, Joseph Borg <[EMAIL PROTECTED]> wrote: > >> Hi Alexander, >> Sorry for the delay in getting back to you on this; I got caught up with >> some work. I've now downloaded and installed nut 2.2.2. Here is the >> output I get when I try to start the driver: >> >> ----------------------------------- >> [EMAIL PROTECTED] bin]# ./megatec_usb -DDDDD -a unial1200 >> Network UPS Tools 2.2.2 - Megatec protocol driver 1.5.14 [megatec_usb] >> Carlos Rodrigues (c) 2003-2008 >> >> Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] >> Andrey Lelikov (c) 2006, Alexander Gordeev (c) 2006-2007, Jon Gough (c) >> 2007 >> >> debug level is '5' >> Checking device (1D6B/0001) (002/001) >> - VendorID: 1d6b >> - ProductID: 0001 >> - Manufacturer: unknown >> - Product: unknown >> - Serial Number: unknown >> - Bus: 002 >> Trying to match device >> Device does not match - skipping >> Checking device (0F03/0001) (001/002) >> - VendorID: 0f03 >> - ProductID: 0001 >> - Manufacturer: Ver 1.0 >> - Product: USB To RS232 Interface (V1.0) BaudRate 2400bps >> - Serial Number: unknown >> - Bus: 001 >> Trying to match device >> Device matches >> get_data_agiler: raw dump: (0 bytes) => >> Starting UPS detection process... >> Asking for UPS status [Q1]... >> get_data_agiler: raw dump: (0 bytes) => >> get_data_agiler: raw dump: (0 bytes) => >> Q1 => FAILED [short read] >> Q1 detail: (0 bytes) => >> Asking for UPS status [Q1]... >> get_data_agiler: raw dump: (0 bytes) => >> get_data_agiler: raw dump: (0 bytes) => >> Q1 => FAILED [short read] >> Q1 detail: (0 bytes) => >> Asking for UPS status [Q1]... >> get_data_agiler: raw dump: (0 bytes) => >> get_data_agiler: raw dump: (0 bytes) => >> Q1 => FAILED [short read] >> Q1 detail: (0 bytes) => >> Asking for UPS status [Q1]... >> get_data_agiler: raw dump: (0 bytes) => >> get_data_agiler: raw dump: (0 bytes) => >> Q1 => FAILED [short read] >> Q1 detail: (0 bytes) => >> Asking for UPS status [Q1]... >> get_data_agiler: raw dump: (0 bytes) => >> get_data_agiler: raw dump: (0 bytes) => >> Q1 => FAILED [short read] >> Q1 detail: (0 bytes) => >> 5 out of 5 detection attempts failed (minimum failures: 2). >> Megatec protocol UPS not detected. >> ----------------------------------- >> >> lsusb lists the device as there: >> >> [EMAIL PROTECTED] bin]# lsusb >> Bus 002 Device 001: ID 1d6b:0001 >> Bus 001 Device 002: ID 0f03:0001 <=== this is it. >> Bus 001 Device 001: ID 1d6b:0001 >> >> You had mentioned stracing? How can we go about doing that? >> >> Many thanks! >> >> Joe >> >> >> On Fri, Oct 10, 2008 at 9:43 AM, Joseph Borg <[EMAIL PROTECTED]> wrote: >> >>> Hi Alexander, >>> sounds like a plan to me. I'll update to 2.2.2 over the weekend (on both >>> machines) and we can take it from there. As for you pointers: >>> >>> - The two UPSs were purchased at the same time (so I have no reason to >>> believe their internal hardware is different). >>> - Both computer are different (i.e. different motherboard etc.) so I >>> don;t think it's a host hardware issue. >>> - They're both running Fedora 8 with the latest kernel, albeit that one >>> is x86_64 and one is i386. >>> >>> That said, I'll upgrade them over the weekend and take it from there. If >>> you could let me know about any specific things you want me to take a note >>> of and how to do stracing etc, I'll do so. >>> >>> Cheers, >>> >>> Joe >>> >>> >>> >>> On Wed, Oct 8, 2008 at 11:00 PM, Alexander I. Gordeev < >>> [EMAIL PROTECTED]> wrote: >>> >>>> Hi Joseph, >>>> >>>> Nice to see you again :) >>>> >>>> On Tuesday 07 October 2008 23:21:32 Joseph Borg wrote: >>>> > Hi, >>>> > Apologies for picking up on this old thread but I never had gotten >>>> this >>>> > issue resolved and I'm now back in the location where the UPSs are so >>>> I was >>>> > hoping we could look into the issue again. >>>> > >>>> > Basically, I had two Unitek Alpha 1200sx UPSs, connected to Fedora >>>> Linux 8. >>>> > The NUT version seems to be: >>>> > >>>> > Network UPS Tools upsd 2.2.0- >>>> > not listening on 0.0.0.0 port 3493 >>>> > >>>> > The driver seems to be the megatec_usb driver. The problem I have is >>>> that >>>> > this only seems to work occasionally (I typically have to restart the >>>> > deamon several times, switch on/off the UPSs etc in order to get it to >>>> > work). Most of the time, the controller seems to fail to start up and >>>> I >>>> > subsequently get the following message: >>>> > >>>> > Broadcast message from nut (Tue Oct 7 21:14:44 2008): >>>> > >>>> > UPS [EMAIL PROTECTED] is unavailable >>>> > >>>> > I'm not quite sure what other information you'd need. That said, I can >>>> > provide any output requested. >>>> > >>>> > Thanks in advance for helping me out. >>>> > >>>> > Joe >>>> > >>>> >>>> First of all I suggest you to update your NUT to the latest version. >>>> There is >>>> at least one reason for that - megatec_usb driver now supports automatic >>>> reconnection after link fail. This is not a fix. >>>> >>>> I have several suspects on this subject: >>>> >>>> 1. hardware. >>>> >>>> Something could not ok in both UPSes (not very likely) or in the USB >>>> host >>>> hardware. Try connecting the UPSes to other machines. >>>> >>>> 2. software >>>> >>>> It could be everything: kernel, udev, NUT... I think strace-ing >>>> megatec_usb >>>> can help. >>>> >>>> -- >>>> Alexander >>>> >>> >>> >> >
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
