Home > Ubuntu Unable > Apcupsd-cgi

Apcupsd-cgi

Contents

For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. UPS running on mains. > > > >Why is my old renamed apcupsd.events-old file updating? Changed in apcupsd (Ubuntu): status: New → Invalid Stephan Henningsen (zta77) wrote on 2016-01-24: #3 This bug report helped me read the output properly too =) See full activity log To This does not # set the EEPROM. #UPSNAME # # UPSCABLE [ simple | smart | ether | usb | # 940-0119A | 940-0127A | 940-0128A | 940-0020B | # 940-0020C

LOCKFILE /var/lock # SCRIPTDIR # Directory in which apccontrol and event scripts are located. You seem to have CSS turned off. This # is particulary useful if you have multiple UPSes. It is mainly defaults.

Apcupsd-cgi

So there is some reason why these installations > are not automatically starting acpupsd. > > The question remains, how can I find out what is happening at startup in > When the file grows beyond this limit, older EVENTS will
# be removed from the beginning of the file (first in first out). the program is sucessfully creating the following file "LCKhiddev[0-15]" in the proper directory with -rw-r--r-- (644) permissions owned by root. seawolf Torna su Vai giù Mostra ultimi messaggi: Tutti i messaggi1 giorno7 giorni2 settimane1 mese3 mesi6 mesi1 anno Ordina per AutoreOra di invioTitolo CrescenteDecrescente Rispondi al messaggio 13 messaggi •

If you don't want to be annoyed by short
# powerfailures, make sure that apccontrol powerout does nothing
# i.e. Attached to driver: usb sharenet.type = DISABLE cable.type = USB_CABLE You are using a USB cable type, so I'm entering USB test mode mode.type = USB_UPS Setting up the port ... Only applicable on slaves.
#MASTER

# SLAVE
# IP address(es) of the slave(s). Apcupsd has never automatically started successfully on either of the distros I have which are KDE based, either Mepis 6.0 or OpenSuse 10.2.

Ahhh! Cannot Init Usb Hid Report. Err=bad File Descriptor I renamed it > so I can start a new log file a few weeks ago! Yet how do I determine if apcupsd >>>> is actually running when I boot into Mepis ? https://help.ubuntu.com/community/apcupsd Not sure what's up. -- "It's like stepping on ants...

They can be used directly # rather than using one of the above aliases. # # UPSTYPE [ dumb | apcsmart | net | usb | snmp | test] # # Please don't fill out this field. But 'ls /var/lock/subsys/apcupsd' exists. I did not see apcupsd started however.

Cannot Init Usb Hid Report. Err=bad File Descriptor

Attached to driver: usb sharenet.type = DISABLE cable.type = USB_CABLE You are using a USB cable type, so I'm entering USB test mode mode.type = USB_UPS Setting up the port ... http://apcupsd-ups-control-software.10985.n7.nabble.com/Error-Unable-to-create-UPS-lock-file-td6191.html or [email protected] ( ) Re: [Apcupsd-users] Valid lock file for pid=14367, but not ours pid=17728? Apcupsd-cgi Evidently the manual startup, '/sbin/apcupsd', works fine but the automatic startup is not happening. Gapcmon For # other UPS types, you must specify an appropriate port or address. # # UPSTYPE DEVICE Description # apcsmart /dev/tty** Newer serial character device, # appropriate for SmartUPS models using

cat /etc/apcupsd/apcupsd.conf ## apcupsd.conf v1.1 ## # # for apcupsd release 3.10.18 (21 July 2005) - debian # # "apcupsd" POSIX config file # # ========= General configuration parameters ============ # Last edited by sidcypher; February 3rd, 2011 at 06:45 AM. Finally I found a /var/log/apcupsd.events. This is how unix files work.

Tango Icons Tango Desktop Project. I'm guessing that this APC model just doesn't have the features that apctest is looking for, eh? apctest FATAL ERROR in device.c at line 68 Unable to create UPS lock file. Shut down apcupsd > first.

I found various references via Google and it seems there's a bug in the apcupsd software that makes it not release a lock file after a power failure. [email protected]:~$ sudo service apctest stop apctest: unrecognized service [email protected]:~$ sudo apctest 2011-02-02 22:58:56 apctest 3.14.4 (18 May 2008) debian Checking configuration ... macagent Linux - Newbie 6 07-08-2007 06:31 PM apcupsd cannot find usb ups on Debian Sarge davelk Linux - Hardware 2 10-14-2006 12:28 PM userdel: unable to lock password file asc3ndant

That worked.

In /var/log/messages there was no mention of >> apcupsd. In /var/log/messages there was no mention of >>>> apcupsd. Warning power loss detected on UPS FooBar Broadcast Message from [email protected] (somewhere) at 6:55 ... Yet how do I determine if apcupsd >>> is actually running when I boot into Mepis ?

Any Ideas? However, it flashes by so quickly on the monitor that I can't say for sure. One other clue is that apcaccess eeprom returns an error: FATAL ERROR in apcaccess.c at line 190 Your model does not support EPROM programming. ...is it possible that this APC model I never ran into that problem before except on MacOS X > 10.2.

First, here's the setup: Dell SC440 Debian Sarge; kernel 2.6.19.1 APC BackUPS 1500VA (XS series); USB cable acpupsd 3.10.17 (installed via sarge deb) Installation appears correct; it appears that the debian Don't pull the plug, you need to keep the ground connected to avoid damage. ------------------------------------- Oooh Shiny: PopularPages Unumquodque potest reparantur. I at least check them to see if they match the other items started at boot time by the OS. You seem to have CSS turned off.

Nothing > fancy either. > > cat /etc/apcupsd/apcupsd.conf > [...] > # > # If you want the last few EVENTS to be available over the network > # by the Attached to driver: usb sharenet.type = DISABLE cable.type = USB_CABLE You are using a USB cable type, so I'm entering USB test mode mode.type = USB_UPS Setting up the port ... Error > repeats. > > What is the solution? > > Thanks, > Dave > > - - - > > " > apcupsd FATAL ERROR in device.c at line 71 Was any of that the case? --Adam Re: [Apcupsd-users] apcupsd doesn't shutdown UPS -- solution From: Stan Kaufman - 2007-02-10 17:38:48 Adam Kropelin wrote: > This implies that either apcupsd

I did not see apcupsd >>>> started however. remained on.. apctest error termination completed [email protected]:~$ Got apctest to work.. The # parameter EVENTSFILEMAX can be set to a different > kilobyte value, or set # to zero to allow the EVENTSFILE to grow > without limit. > EVENTSFILEMAX 10 Ok,

No, thanks SourceForge Browse Enterprise Blog Deals Help Create Log In or Join Solution Centers Go Parallel Resources Newsletters Cloud Storage Providers Business VoIP Providers Call Center Providers Thanks for helping apctest: bad option, I cannot do a killpower ==== This is weird, because apcupsd seems to work properly with all the other power-down tests etc. So there is some reason why these installations are not automatically starting acpupsd.