Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Citeren David C. Rankin drankina...@suddenlinkmail.com:
# Package provides driver for USB HID UPSes, but people can live
with hal addon:
Enhances: %(set -x ; echo %{QUOTE}%{USBDRIVERS}%{QUOTE} | sed -n
s/^HALD-ADDON-USBHID-UPS=//p | tr '%{BACKSLASH}n' ' ')
# Package provides the only avalailable driver for other USB UPSes:
Supplements: %(set -x ; echo %{QUOTE}%{USBDRIVERS}%{QUOTE} | sed
'/^HALD-ADDON-USBHID-UPS=/d;s/^.*=//' | tr '%{BACKSLASH}n' ' ')
I really have no idea what the above is supposed to do. On my
development system, I removed all these lines which seemed to have no
bad side effect.
I would like to build the rpms if possible. Do you have any pointers?
Please contact the person who wrote this .spec file. We no longer
provide .spec files for exactly this kind of problem. It is impossible
for us to keep track of all the packaging stuff that is added to adapt
NUT to a specific distribution.
Furthermore, it doesn't make sense fixing this on your end, if this
isn't fixed upstream as well.
Best regards, Arjen
--
Please keep list traffic on the list
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Arjen de Korte wrote: Citeren David C. Rankin drankina...@suddenlinkmail.com: I would like to build the rpms if possible. Do you have any pointers? Please contact the person who wrote this .spec file. We no longer provide .spec files for exactly this kind of problem. It is impossible for us to keep track of all the packaging stuff that is added to adapt NUT to a specific distribution. Furthermore, it doesn't make sense fixing this on your end, if this isn't fixed upstream as well. Best regards, Arjen Uh... Arjen I have a stupid question -- Where's the ./configure file in r1715? The INSTALL file says: Build and install = 1. Configure the source tree for your system. Add the --with-user and --with-group switch to set the user name and group that you created above. ./configure --with-user=ups --with-group=nut Umm... I can't find a ./configure. I know this is something basic. What do I do to get one or turn the configure.in file into one? Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Arjen, 2009/1/14 Arjen de Korte nut+de...@de-korte.org nut%2bde...@de-korte.org Citeren David C. Rankin drankina...@suddenlinkmail.com: Umm... I can't find a ./configure. I know this is something basic. What do I do to get one or turn the configure.in file into one? Thanks. You seem to have grabbed everything from the SVN trunk, right? In that case, you need to have a bunch of autotools installed and run 'autoreconf --install'. prefer pointing the source pages since these mention it: http://www.networkupstools.org/source.html http://test.networkupstools.org/Documentation/UserManual/SoftwareSource Arnaud ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Arjen de Korte wrote: Citeren David C. Rankin drankina...@suddenlinkmail.com: Umm... I can't find a ./configure. I know this is something basic. What do I do to get one or turn the configure.in file into one? Thanks. You seem to have grabbed everything from the SVN trunk, right? In that case, you need to have a bunch of autotools installed and run 'autoreconf --install'. Best regards, Arjen Arjen: God I hate it when the answer is so simple: 15:47 nirvana:~/linux/apps/nut-2.2.2-trunk autoreconf --install configure.in:14: installing `./missing' configure.in:14: installing `./install-sh' clients/Makefile.am: installing `./depcomp' 15:48 nirvana:~/linux/apps/nut-2.2.2-trunk l total 1928 snip -rwxr-xr-x 1 david dcr 928449 2009-01-14 15:48 configure* -rw-r--r-- 1 david dcr 24641 2009-01-13 18:28 configure.in snip Worked like a charm. Thanks! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
David C. Rankin wrote: Arjen de Korte wrote: Citeren David C. Rankin drankina...@suddenlinkmail.com: Umm... I can't find a ./configure. I know this is something basic. What do I do to get one or turn the configure.in file into one? Thanks. You seem to have grabbed everything from the SVN trunk, right? In that case, you need to have a bunch of autotools installed and run 'autoreconf --install'. Best regards, Arjen Arjen: God I hate it when the answer is so simple: 15:47 nirvana:~/linux/apps/nut-2.2.2-trunk autoreconf --install configure.in:14: installing `./missing' configure.in:14: installing `./install-sh' clients/Makefile.am: installing `./depcomp' 15:48 nirvana:~/linux/apps/nut-2.2.2-trunk l total 1928 snip -rwxr-xr-x 1 david dcr 928449 2009-01-14 15:48 configure* -rw-r--r-- 1 david dcr 24641 2009-01-13 18:28 configure.in snip Worked like a charm. Thanks! Arjen, Arnaud: I seem to be doing something stupid again with the ./configure options. I have compiled r1715 and it starts just fine, but I cannot connect with upsc. I configured nut on opensuse 10.3 like this: ./configure \ --with-user=upsd \ --with-group=daemon \ --with-usb \ --with-snmp \ --with-cgi make, make install went fine and all was installed in /usr/local/bin. I stopped 2.2.2 and then went to start 2.2.2-r1715. Before starting the new version, I wanted to make sure I was using my working config so I moved all the /usr/local/nut/etc/*.sample files to /usr/local/nut/etc/orig and then copied my config and html files from /etc/ups to /usr/local/nut/etc/. Just to make sure I was using my old config, I also set First attempt to start failed because I hadn't created the /var/state/ups directory. No problem, I created it and then tried starting nut again with a successful result: [18:26 nirvana/usr/local/ups] # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.0-pre1-1715 Network UPS Tools - Generic HID driver 0.34 (2.4.0-pre1-1715) USB communication driver 0.30 Using subdriver: CyberPower HID 0.2 All looked good. Then I went to check the values with upsc and: [18:26 nirvana/usr/local/ups] # /usr/local/ups/bin/upsc Nirvana_UPS Error: Connection failure: Connection refused Huh? I checked with ps ax to make sure it was running: 31886 ?Ss 0:00 /usr/local/ups/bin/usbhid-ups -a nirvana_ups I tried one more time to connect and then shutdown and went back to the rpm install of nut: [18:28 nirvana/usr/local/ups] # /usr/local/ups/bin/upsc Nirvana_UPS Error: Connection failure: Connection refused [18:29 nirvana/usr/local/ups] # /usr/local/ups/bin/upsdrvctl stop Network UPS Tools - UPS driver controller 2.4.0-pre1-1715 [18:30 nirvana/usr/local/ups] # rcupsd start Starting NUT UPS drivers done Starting NUT UPS server done Starting NUT UPS monitor done I then shutdown the rpm version and started r1715 in the debug mode calling usbhid-ups directly and everything looks like it is working, [Uh O -- the voltage is still whacko at 20.3...] but I still can't connect? Here is the debug output: [22:54 nirvana/usr/local/ups] # bin/usbhid-ups -DD -a nirvana_ups Network UPS Tools - Generic HID driver 0.34 (2.4.0-pre1-1715) USB communication driver 0.30 debug level is '2' upsdrv_initups... Checking device (/) (002/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (0764/0501) (001/002) - VendorID: 0764 - ProductID: 0501 - Manufacturer: CPS - Product: UPS CP1000AVRLCD - Serial Number: unknown - Bus: 001 Trying to match device Device matches HID descriptor length 387 Report Descriptor size = 387 Using subdriver: CyberPower HID 0.2 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 1.00 Path: UPS.PowerSummary.iSerialNumber, Type: Feature, ReportID: 0x02, Offset: 0, Size: 8, Value: 2.00 Path: UPS.PowerSummary.iDeviceChemistry, Type: Feature, ReportID: 0x03, Offset: 0, Size: 8, Value: 4.00 Path: UPS.PowerSummary.iOEMInformation, Type: Feature, ReportID: 0x04, Offset: 0, Size: 8, Value: 3.00 Path: UPS.PowerSummary.Rechargeable, Type: Feature, ReportID: 0x05, Offset: 0, Size: 8, Value: 1.00 Path: UPS.PowerSummary.CapacityMode, Type: Feature, ReportID: 0x06, Offset: 0, Size: 8, Value: 2.00 Path: UPS.PowerSummary.DesignCapacity, Type: Feature, ReportID: 0x07, Offset: 0, Size: 8, Value: 100.00 Path: UPS.PowerSummary.CapacityGranularity1, Type: Feature, ReportID: 0x07, Offset: 8, Size: 8, Value: 5.00 Path: UPS.PowerSummary.CapacityGranularity2, Type: Feature, ReportID: 0x07, Offset: 16, Size: 8, Value: 10.00 Path: UPS.PowerSummary.WarningCapacityLimit, Type: Feature,
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Arjen de Korte wrote: Citeren David C. Rankin drankina...@suddenlinkmail.com: Any luck yet on the voltage fix for the Cyber Power UPS CP1000AVRLCD? I'm still greeted by 'battery.voltage: 20.3' each time I check. Just thought I'd ask. Thanks. This change was comitted to the trunk on Dec 15 (r1627), so if you upgrade to the development version, this should be OK now. Best regards, Arjen Arjen, Mayday -- We still have voltage issues is 1715: [22:54 nirvana/usr/local/ups] # bin/usbhid-ups -DD -a nirvana_ups Network UPS Tools - Generic HID driver 0.34 (2.4.0-pre1-1715) USB communication driver 0.30 debug level is '2' upsdrv_initups... Checking device (/) (002/001) - VendorID: - ProductID: - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 002 Trying to match device Device does not match - skipping Checking device (0764/0501) (001/002) - VendorID: 0764 - ProductID: 0501 - Manufacturer: CPS - Product: UPS CP1000AVRLCD - Serial Number: unknown - Bus: 001 Trying to match device Device matches HID descriptor length 387 Report Descriptor size = 387 Using subdriver: CyberPower HID 0.2 snip Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 8, Value: 20.30 Looks like the fix in r1627 didn't stay fixed :-( -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Citeren David C. Rankin drankina...@suddenlinkmail.com: snip Path: UPS.PowerSummary.Voltage, Type: Feature, ReportID: 0x0a, Offset: 0, Size: 8, Value: 20.30 Looks like the fix in r1627 didn't stay fixed :-( Not at all. What you're seeing is a debug line that tells us what the UPS is reporting. We can't change that without modifying the firmware in the UPS. We can only adjust the value that is reported in 'battery.voltage' and this is exactly what this patch does. If you really want to check this out without fixing your configuration first, run the driver with debug level 5 (-D) and you'll see what is reported to the socket to which the server connects. Note that it will be very verbose. Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Arjen de Korte wrote:
Citeren David C. Rankin drankina...@suddenlinkmail.com:
Any luck yet on the voltage fix for the Cyber Power UPS CP1000AVRLCD? I'm
still greeted by 'battery.voltage: 20.3' each time I check. Just
thought I'd
ask. Thanks.
This change was comitted to the trunk on Dec 15 (r1627), so if you
upgrade to the development version, this should be OK now.
Best regards, Arjen
Arjen,
I thought I would try building a set of rpms for openSuSE 10.3 with the
development version, but I am running into problems. In installed the latest
src.rpm I could find (sbrabec's) from openSuSE build service.
http://download.opensuse.org/repositories/home:/sbrabec:/backports/openSUSE_10.3/src/nut-2.2.2-67.1.src.rpmI
Then I checked out r1715 and created a source package from it with:
tar -cjf /usr/src/packages/SOURCES/nut-2.2.2-svn-1715.tar.bz2 nut-trunk/
I copied the spec file to: nut-trunk-1715.spec and edited the spec file
as
follows:
Version:2.2.2
Release:1715
Url:http://www.networkupstools.org/
Source: %{name}-%{version}-svn-%{release}.tar.bz2
I then kicked off the build with rpmbuild -bb nut-trunk-1715.spec, but
the
build died really quick with the following error:
snip
MATCH KEY=USB_DEVICE.VENDOR_ID INT=0X-!
ABLEREX 625L USB
-MATCH KEY=USB_DEVICE.PRODUCT_ID INT=0X- APPEND
KEY=INFO.CATEGORY TYPE=STRINGBATTERY/APPEND- MERGE
KEY=INFO.CAPABILITIES TYPE=STRLISTBATTERY/MERGE
PRINT ' 'KEY=USB_DEVICE.VENDOR_ID' 'INT='
sh: line 112: MATCH: No such file or directory
error: line 66: Empty tag: Enhances:
Full build output at:
http://www.3111skyline.com/download/ups/nutrpmbuild-error
I looked at the spec and removed a few spaces on line 66 from between
'Enhances:' and '%(set' which did help the build get through the 'MATCH
KEY...' stuff, but it still died.
Lines 65-67 are:
# Package provides driver for USB HID UPSes, but people can live with hal addon:
Enhances: %(set -x ; echo %{QUOTE}%{USBDRIVERS}%{QUOTE} | sed -n
s/^HALD-ADDON-USBHID-UPS=//p | tr '%{BACKSLASH}n' ' ')
# Package provides the only avalailable driver for other USB UPSes:
Supplements: %(set -x ; echo %{QUOTE}%{USBDRIVERS}%{QUOTE} | sed
'/^HALD-ADDON-USBHID-UPS=/d;s/^.*=//' | tr '%{BACKSLASH}n' ' ')
I would like to build the rpms if possible. Do you have any pointers?
I'll go
just compile it in the mean time, but it seems like I should be able to build
the rpms also. Thanks.
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Citeren David C. Rankin drankina...@suddenlinkmail.com: I know you are busy, but I was curious if you have had the chance to install 11.1 yet and see if you could confirm whether this problem was with me or with the package permissions? No hurry, I was just curious. I just finished upgrading from openSUSE 11.0 to 11.1. No changes needed. So I think we'll have to dig a little deeper to see why this isn't working for you anymore. Here the most important RPM versions are: #rpm -qf /usr/lib/ups/driver/usbhid-ups nut-2.2.2-63.13 #rpm -qf /etc/udev/rules.d/52_nut-usbups.rules nut-classic-2.2.2-63.13 And the processes running #ps u -u upsd USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND upsd 3991 0.1 0.1 4164 808 ?Ss 16:52 0:03 /usr/lib/ups/driver/usbhid-ups -a mge-usb upsd 3993 0.0 0.2 4988 1384 ?Ss 16:52 0:01 /usr/lib/ups/driver/snmp-ups -a mge-snmp upsd 3995 0.0 0.1 4376 928 ?Ss 16:52 0:01 /usr/lib/ups/driver/netxml-ups -a mge-xml upsd 4001 0.0 0.1 4072 632 ?Ss 16:52 0:00 /usr/sbin/upsd -u upsd upsd 4003 0.0 0.1 4288 724 ?S16:52 0:00 /usr/sbin/upsmon These seem to be older than the ones you have now. Could it be that you are running a version from a different source? Something from the openSUSE build service maybe? Or that you have configured a different user somewhere? Best regards, Arjen -- Please keep list traffic on the list ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
Re: [Nut-upsdev] Problems with nut on new openSuSE 11.1 (same ecstasy_ups)
Arjen de Korte wrote: Citeren David C. Rankin drankina...@suddenlinkmail.com: Unable to get HID descriptor (error sending control message: Operation not permitted) This is bad. This means that NUT is shipped with broken permissions, most likely because something changed with udev. I'll install openSUSE later today and let you know if this is something you can fix easily yourself. Best regards, Arjen Hi Arjen, I know you are busy, but I was curious if you have had the chance to install 11.1 yet and see if you could confirm whether this problem was with me or with the package permissions? No hurry, I was just curious. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com ___ Nut-upsdev mailing list Nut-upsdev@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
