search for: melvincall979

On Jan 30, 2015, at 4:22 PM, Melvin Call <melvincall979 at gmail.com> wrote: > At this point I unplugged the UPS and plugged it into a different USP port, but > that did not change the above. Figuring this was likely a udev problem, I > created the following /etc/udev/rules.d/52-nut-usbups.rules (based on an example > on our database ser...

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 9:17 AM, Melvin Call <melvincall979 at gmail.com> wrote: > >> There is no other information provided, and there is nothing in the log to >> help >> either. Can anyone tell me what I need to do to make this output some >> useful >> information that I can use to further trouble-shoot the problem? &gt...

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > >> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG) >> is >> set to /etc/killpower, but I changed that to /tmp and modified my >> umountroot >> script to mount it read only too, because I know it get...

On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > One last question if you don't mind. I noticed the "default" POWERDOWNFLAG is > set to /etc/killpower, but I changed that to /tmp and modified my umountroot > script to mount it read only too, because I know it gets wiped on reboot. Is > there an...

On Jan 31, 2015, at 9:17 AM, Melvin Call <melvincall979 at gmail.com> wrote: > There is no other information provided, and there is nothing in the log to help > either. Can anyone tell me what I need to do to make this output some useful > information that I can use to further trouble-shoot the problem? In general, if a startup script isn&...

On Feb 1, 2015, at 7:04 AM, Melvin Call <melvincall979 at gmail.com> wrote: > Thank you Charles, for the assistance and the information. Everything is > completely functional here now. Not sure if the APC BackUPS ES550 is on the > list of compatible devices, but it works just fine with the usbhid-ups driver, > and supports several basic...

Hello list, I am configuring NUT on a Dell workstation that is connected to an APC Back UPS Pro 1300, and I am running into an issue where starting everything manually seems to be successful, but fails when using the init.d scripts. The short story is that I get the following error when trying to check the status of the UPS: [root at mypc:/etc/nut]# upsc apc_pro1300 at localhost Error:

Good morning all. I am on a different system with a different UPS, and I am fighting a similar problem to the one I posted about yesterday, and again making little headway. This system is running Debian Wheezy and connected to an APC BackUPS ES550. Starting things manually seems to go well, but my startup script fails, and nothing is logged anywhere. This may not be a NUT question per se, but I