Re: [Nut-upsuser] Support of quot; shutdown.returnquot; on a APC Back-UPS CS 500
Arjen de Korte nut+users at de-korte.org writes: Citeren Ritchie rotarn at gmx.de: I am trying to get a APC Back-UPS CS 500 running on my QNAP 419P Nas. [...] I am missing the command shutdown.return' ? Does the ups not support this command ? It might support it, but not in the USB HID PDC paths that we recognize. If this is supported by this UPS, it is probably in a vendor specific path. Unless someone is able to provide the mapping, we have no idea which one. Search the archives for more information about this issue. It has popped up several times over past few years. Sadly nobody has reported the solution to this and since none of the active NUT developers owns such a device, this likely is going to stay that way. Best regards, Arjen Arjen, I have been using usb APC units (CS 500 and SmartUPS 1000) with nut for some 6 years. I got this to work after extensive trawling of the net and found a fix involving changing the source and recompiling usbhid-ups (or hidups as it used to be). Now the bad news. Although I am still using the recompiled version of hidups and (64 bit) usbhid-ups, I have stupidly lost the source and my notes. :-( Is it any use to you to have the executables? This has been driving me nuts for the last week, as I now have another CS 500 to install, and only a 5 year old version of hidups to do it with! Regards, Kevin. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 01/11/2011 03:38 AM, Arnaud Quette wrote:
Hi Zach,
2011/1/10 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/06/2011 08:06 AM, Arnaud Quette wrote:
2011/1/5 Zach La Celle lace...@roboticresearch.com
mailto:lace...@roboticresearch.com
On 01/04/2011 08:20 AM, Arnaud Quette wrote:
2011/1/4 Charles Lepple clep...@gmail.com
mailto:clep...@gmail.com
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle
lace...@roboticresearch.com
mailto:lace...@roboticresearch.com wrote:
On 12/29/2010 10:00 AM, Zach La Celle wrote:
On 12/29/2010 08:34 AM, Charles Lepple wrote:
On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote:
I ran this in debug mode and captures the backtrace.
root@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0 port 3493
0.000354 Connected to UPS [rack1ups]:
apcsmart-rack1ups
2.550554 User upsmon@127.0.0.1
mailto:upsmon@127.0.0.1 logged into UPS [rack1ups]
*** glibc detected *** upsd: free(): invalid next
size (fast):
0x012c9870 ***
Can you give us some background information about
this system? What OS
and version, who built the package, etc.
Just to be sure, are you running the Ubuntu-provided
package, or
something from another package repository? Which version
of Ubuntu?
Running valgrind might produce similarly opaque results
without debug
symbols (which you can enable if you build from source).
debug syms are available as separate debs.
As an example, for Ubuntu, look here:
https://wiki.kubuntu.org/DebuggingProgramCrash
then look for installing {nut,libupsclient}-dbgsym and
others if needed otherwise...
That is a bit
more involved, though (especially if you want to keep
the installed
files in the same place) so I'd try that after Arjen's
suggestion with
-DDD.
seconded for a first run.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader -
http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
The only extra package I could find is the dev package.
I'm not sure if that contains debugging symbols.
I'm running with the -DDD option now. It hasn't crashed
over the weekend, so we'll see how long it takes to crash
now. I'm getting source to try and rebuild it so that I can
walk through in GDB if necessary.
have you looked at the pointer I've sent, *and* applied the
various mentioned actions (adding key and repository, refresh apt
cache, ...)?
otherwise, you won't see these packages!
I still fail to see what is your exact system (Ubuntu? which
version?) apart from the arch which is x86_64...
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader -
http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
I'm having trouble finding the upsd source code, or maybe I just
don't understand how to run it properly. The source I have for
ubuntu/lucid seems to either be for a different UPSD project, or
to run very differently than the version off of the Ubuntu
repositories. Can you point me to the correct source for upsd?
to get the one for your binary, check that you have a deb-src line
for main in your /etc/apt/sources.list
then apt-get source nut
or get the source here: http://packages.ubuntu.com/maverick/nut
note that upsd package is a completely different project.
cheers,
Arnaud
--
Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
I now have the upsd source package installed and built for debug, but
when I run upsd I get errors connecting to my UPS. I copied all of the
configuration files from my normal config directory (/etc/nut) into the
new directory (/usr/local/ups/etc/), but I get an Error; cannot find
rack1ups; no such file or directory or something along those lines.
I've tried to fix this myself but it just doesn't seem to be working.
Any idea?
Re: [Nut-upsuser] Support of quot; shutdown.returnquot; on a APC Back-UPS CS 500
Citeren Kevin bakd...@gmail.com: I have been using usb APC units (CS 500 and SmartUPS 1000) with nut for some 6 years. I got this to work after extensive trawling of the net and found a fix involving changing the source and recompiling usbhid-ups (or hidups as it used to be). It's sad that you never submitted these changes back to NUT, so that other people might benefit from them. Now the bad news. Although I am still using the recompiled version of hidups and (64 bit) usbhid-ups, I have stupidly lost the source and my notes. :-( Is it any use to you to have the executables? No. This has been driving me nuts for the last week, as I now have another CS 500 to install, and only a 5 year old version of hidups to do it with! Have you tried the latest version (nut-2.6.0) that was released only a couple of days ago? Chances are that it might just work, since we have seen reports about people running the CS 500 in recent years. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] 2.6 and 2.2
I want to upgrade to 2.6 now that it is an official release.
I have one box that is connected to the UPS via the serial port
('master'). I have another box that connects to the master over the
network.
Can I upgrade the master to 2.6, leaving the other box at 2.2, or do I
need to upgrade everything to 2.6 at the same time?
Eventually I want to bring everything up to 2.6, but I want to do it a
step at a time.
Thanks.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] 2.6 and 2.2
On Sun, Jan 16, 2011 at 8:21 PM, Mike. the.li...@mgm51.com wrote:
I want to upgrade to 2.6 now that it is an official release.
I have one box that is connected to the UPS via the serial port
('master'). I have another box that connects to the master over the
network.
Can I upgrade the master to 2.6, leaving the other box at 2.2, or do I
need to upgrade everything to 2.6 at the same time?
As old as this compatibility chart looks, it is still valid for 2.4.x and 2.6.x:
http://www.networkupstools.org/docs/user-manual.chunked/ar01s02.html#_backwards_and_forwards_compatibility
Basically, the network protocol has not changed since 2.0.
If you run into problems with a given driver, it is sometimes possible
to mix and match versions on the same machine (e.g. driver vs. upsd)
but in many cases, it's easier to just upgrade all of each machine's
copy of NUT at the same time (through a package manager, or by
installing to a separate location).
--
- Charles Lepple
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] 2.6 and 2.2
On 1/16/2011 at 8:48 PM Charles Lepple wrote: |As old as this compatibility chart looks, it is still valid for 2.4.x and |2.6.x: | |http://www.networkupstools.org/docs/user-manual.chunked/ar01s02.html#_b ackwards_and_forwards_compatibility | |Basically, the network protocol has not changed since 2.0. | |[snip] = Thanks, I was looking for something like that chart. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
