On 03/08/2012 02:37 PM, Arnaud Quette wrote:
2012/3/7 Zach La Celle lace...@roboticresearch.com:
On 3/7/2012 11:53 AM, Arnaud Quette wrote:
2012/3/5 Zach La Cellelace...@roboticresearch.com:
Still getting the usbhid-ups Report 89 / Report 90 issues...output below.
hem, there was a bug
On 3/7/2012 11:53 AM, Arnaud Quette wrote:
2012/3/5 Zach La Cellelace...@roboticresearch.com:
Still getting the usbhid-ups Report 89 / Report 90 issues...output below.
hem, there was a bug in the developer, mixing hexa and decimal :-/
the reportIDs are really hexa!
a better patch is attached,
/git, or should I just download it manually?
-Zach
On 03/05/2012 09:58 AM, Arnaud Quette wrote:
Hi Zach,
2012/2/29 Zach La Celle lace...@roboticresearch.com:
On 02/27/2012 06:38 AM, Arnaud Quette wrote:
2012/2/21 Zach La Celle lace...@roboticresearch.com:
I figured out the cause
wrote:
2012/3/5 Zach La Celle lace...@roboticresearch.com:
Yes, I can test on trunk or on a patched version, but I cannot shut down
or restart this particular UPS during the day. Hopefully we won't need
to do that to figure out the Report 89 / Report 90 stuff.
perfect.
indeed, I just need
On 02/27/2012 06:38 AM, Arnaud Quette wrote:
2012/2/21 Zach La Celle lace...@roboticresearch.com:
I figured out the cause of this problem: incorrect permissions on the
USB device. At least, this seemed to fix the problem I had when I
manually tried to run upsdrvctl and got a permission denied
On 02/13/2012 11:41 AM, Arnaud Quette wrote:
2012/2/13 Zach La Celle lace...@roboticresearch.com:
On 02/07/2012 10:58 AM, Zach La Celle wrote:
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
that's what I was suspecting.
I've never seen that one before, though!
a driver debug output, Ie
On 02/07/2012 10:58 AM, Zach La Celle wrote:
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
that's what I was suspecting.
I've never seen that one before, though!
a driver debug output, Ie:
$ /lib/nut/usbhid-ups -D -a rack1ups
please, compress the result or sent in a reference
On 02/07/2012 10:41 AM, Arnaud Quette wrote:
2012/2/6 Zach La Celle lace...@roboticresearch.com:
On 02/03/2012 08:51 PM, Charles Lepple wrote:
On Feb 3, 2012, at 3:10 PM, Arnaud Quette wrote:
On the USB side of things, something seems fishy with the APC usb
connection: it's been incrementing
On 02/03/2012 08:51 PM, Charles Lepple wrote:
On Feb 3, 2012, at 3:10 PM, Arnaud Quette wrote:
On the USB side of things, something seems fishy with the APC usb
connection: it's been incrementing the Device ID, up to 124 from 004.
this is not a big issue, and probably due to the 2.4.3
Thank you guys for your responses.
- The Nut version I have installed (from the Ubuntu repositories) is
2.4.3-1ubuntu3.1.
- The OS is Ubuntu server 10.04 LTS x64 with the 2.6.35-std210-amd64 kernel.
- Driver output:
root@www:/etc/nut# /lib/nut/apcsmart -D -a rack1ups
Network UPS Tools - APC
Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
It's now device 006 on bus 005! It seems to change every time I chmod it.
-Zach
On 2/3/2012 10:07 AM, Zach La Celle wrote:
Thank you guys
We recently had to replace an old APC SmartUPS 3000 with a newer 3000VA
(the 2U one). It has both serial and USB in the back (with an RJ-45 on
the end of the serial cable).
I can't get the apcsmart driver to connect. I figured it should work
the exact same as the old UPS, with /dev/ttyS0 as
On 02/15/2011 03:48 PM, Zach La Celle wrote:
On 02/15/2011 03:27 PM, Arjen de Korte wrote:
Citeren Zach La Celle lace...@roboticresearch.com:
You can see where the problem happens in parseconf.c, on line 125
with the code:
/* resize the lists */
ctx-arglist = realloc(ctx-arglist
On 02/16/2011 10:16 AM, Arjen de Korte wrote:
Citeren Zach La Celle lace...@roboticresearch.com:
On the Dell server, the MpMemory testing all passed. It doesn't seem
to be a physical problem with the memory on the machine. I also ran
some other basic diagnostics on the disk drives, cache
Resurrecting this problem, because I finally caught it in the debugger...
Here's the trace, with some GDB prints. Please excuse the length.
-
...
545815.397326 mainloop: polling 4 filedescriptors
*** glibc detected *** /sbin/upsd: malloc(): memory
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/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
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.
r...@*:/etc/nut# upsd -D
Network UPS Tools upsd 2.4.3
0.00 listening on 0.0.0.0
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.
r...@*:/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
:32 PM, Zach La Celle wrote:
In /var/log/syslog
Dec 23 13:04:50 ** upsmon[2010]: Poll UPS
[rack1...@localhost] failed - Write error: Broken pipe
After this, there is no longer a upsd daemon running.
Error messages follow:
Dec 23 13:04:50 ** upsmon[2010]: Communications
In /var/log/syslog
Dec 23 13:04:50 ** upsmon[2010]: Poll UPS
[rack1...@localhost] failed - Write error: Broken pipe
After this, there is no longer a upsd daemon running.
Error messages follow:
Dec 23 13:04:50 ** upsmon[2010]: Communications with UPS
I can run upsdrvctl start and it starts fine. On computer boot,
however, it doesn't start properly.
I'm trying to find the logs which would give more detail, but I'm not
sure where they are. I see no logs in /etc/nut or /var/log.
I don't know if this helps, but it looks like there's a
22 matches
Mail list logo