not able to start apcupsd daemon

Bug #284180 reported by Shirish Agarwal
2
Affects Status Importance Assigned to Milestone
apcupsd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apcupsd

Hi all,
 I just bought an APC UPS - 800 for my standalone machine and I downloaded apcupsd . If I run cat /proc/bus/usb/devices I get the following entry for the APC usb thing.

Note:- I had to manually do the mount -t usbdevfs none /proc/bus/usb

Later taking information from http://www.apcupsd.org/manual/Linux_Kernel_Info.html#proc_usb_info-2.6

I added the line below in /etc/fstab
none /proc/bus/usb usbfs defaults 0 0

then I could see the following

T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=051d ProdID=0002 Rev= 1.06
S: Manufacturer=American Power Conversion
S: Product=Back-UPS BR 800 FW:9.o4 .I USB FW:o4
S: SerialNumber=BB0100009999
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 24mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 6 Ivl=10ms

dmesg shows the following

shirish@Mugglewille-desktop:~$ dmesg | grep American
[ 6.587353] hiddev96hidraw0: USB HID v1.10 Device [American Power Conversion Back-UPS BR 800 FW:9.o4 .I USB FW:o4 ] on usb-0000:00:1d.1-2

Now if I do either /etc/init.d/apcupsd start or /etc/init.d/apcupsd status I get the following errors :-

Scenario a :-

 /etc/init.d/apcupsd start
Starting UPS power management: Terminating due to configuration file errors.

Scenario b:-

/etc/init.d/apcupsd status
Error contacting apcupsd @ localhost:3551: Connection refused

Attaching my /etc/apcupsd/apcupsd.conf file . Please lemme know if anything if you need any more information.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
Package: apcupsd 3.14.4-1
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
SourcePackage: apcupsd
Uname: Linux 2.6.27-7-generic i686

Tags: apport-bug
Revision history for this message
Shirish Agarwal (shirishag75) wrote :
Revision history for this message
Shirish Agarwal (shirishag75) wrote :

There is something which is in my /var/log/messages which may be connected or not.

Oct 16 10:27:44 Mugglewille-desktop kernel: [ 268.740457] type=1503 audit(1224133064.680:5): operation="inode_per
mission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/5893/net/" pid=5893 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.794849] type=1503 audit(1224133065.732:6): operation="inode_per
mission" requested_mask="r::" denied_mask="r::" fsuid=7 name="/proc/5899/net/" pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.799997] type=1503 audit(1224133065.736:7): operation="socket_cr
eate" family="ax25" sock_type="dgram" protocol=0 pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.803982] type=1503 audit(1224133065.740:8): operation="socket_cr
eate" family="netrom" sock_type="seqpacket" protocol=0 pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.808110] type=1503 audit(1224133065.748:9): operation="socket_cr
eate" family="rose" sock_type="dgram" protocol=0 pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.811809] type=1503 audit(1224133065.748:10): operation="socket_c
reate" family="ipx" sock_type="dgram" protocol=0 pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.815455] type=1503 audit(1224133065.752:11): operation="socket_c
reate" family="appletalk" sock_type="dgram" protocol=0 pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.815480] type=1503 audit(1224133065.752:12): operation="socket_c
reate" family="econet" sock_type="dgram" protocol=0 pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.815493] type=1503 audit(1224133065.752:13): operation="socket_c
reate" family="ash" sock_type="dgram" protocol=0 pid=5899 profile="/usr/sbin/cupsd"
Oct 16 10:27:45 Mugglewille-desktop kernel: [ 269.815505] type=1503 audit(1224133065.752:14): operation="socket_c
reate" family="x25" sock_type="seqpacket" protocol=0 pid=5899 profile="/usr/sbin/cupsd"

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

Hi all,
 Finally getting somewhere, this is the output on my /var/log/apcupsd.events

 cat /var/log/apcupsd.events
Wed Oct 15 13:42:58 IST 2008 apcupsd FATAL ERROR in smartsetup.c at line 171
PANIC! Cannot communicate with UPS via serial port.
Please make sure the port specified on the DEVICE directive is correct,
and that your cable specification on the UPSCABLE directive is correct.
Wed Oct 15 13:42:58 IST 2008 apcupsd error shutdown completed
Wed Oct 15 15:30:46 IST 2008 apcupsd FATAL ERROR in smartsetup.c at line 171
PANIC! Cannot communicate with UPS via serial port.
Please make sure the port specified on the DEVICE directive is correct,
and that your cable specification on the UPSCABLE directive is correct.
Wed Oct 15 15:30:46 IST 2008 apcupsd error shutdown completed

Revision history for this message
Shirish Agarwal (shirishag75) wrote :

now my question would be why does it think that my apcupsd is via serial port?

I am able to get quite a bit of information via gnome-power-manager, any ideas anybody.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.