apcupsd and proxmox ve 2.2

machines

Member
Nov 1, 2006
32
0
6
Hello,

I just tried to install apcupsd on my proxmox ve 2.2 installation in order to get the system cleanly shutdown,
but the daemon will not start.

After the installation I get the following error:

update-rc.d: warning: apcupsd start runlevel arguments (1 2 3 4 5) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: apcupsd stop runlevel arguments (0 6) do not match LSB Default-Stop values (0 1 6)

I found two informations on the web, which are saying that this behaviour is perhaps a bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610429
https://bugs.launchpad.net/ubuntu/+source/apcupsd/+bug/971710

Can someone confirm that and is there a way right now to get it working ?

Thanks for your help.

Greetings Marco.
 
i see not an error, I see just a warning.

Code:
root@proxmox-6-183:~# apt-get install apcupsd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  apcupsd-doc
Suggested packages:
  apcupsd-cgi hal
The following NEW packages will be installed:
  apcupsd apcupsd-doc
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 932 kB of archives.
After this operation, 2,888 kB of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 [URL]http://mirror.maurer-it.com/debian/[/URL] squeeze/main apcupsd amd64 3.14.8-2 [291 kB]
Get:2 [URL]http://mirror.maurer-it.com/debian/[/URL] squeeze/main apcupsd-doc all 3.14.8-2 [641 kB]
Fetched 932 kB in 0s (6,161 kB/s)
Selecting previously deselected package apcupsd.
(Reading database ... 27939 files and directories currently installed.)
Unpacking apcupsd (from .../apcupsd_3.14.8-2_amd64.deb) ...
Selecting previously deselected package apcupsd-doc.
Unpacking apcupsd-doc (from .../apcupsd-doc_3.14.8-2_all.deb) ...
Processing triggers for man-db ...
Setting up apcupsd (3.14.8-2) ...
update-rc.d: warning: apcupsd start runlevel arguments (1 2 3 4 5) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: apcupsd stop runlevel arguments (0 6) do not match LSB Default-Stop values (0 1 6)
Please check your configuration ISCONFIGURED in /etc/default/apcupsd
Setting up apcupsd-doc (3.14.8-2) ...
root@proxmox-6-183:~# service apcupsd status
Please check your configuration ISCONFIGURED in /etc/default/apcupsd
root@proxmox-6-183:~# nano /etc/default/apcupsd
...

so just proceed with the configuration.
 
What is default timeout or timeframe when the KVM machine needs to be turned off if the host receive shutdown command (shutdown -h now)?

For example: Windows VM needs about 3 minutes to shutdown. If there is timeout (i guess it's 1 minute) the VM gets killed by STOP command?

Thanks!
 
Hi Tom,

thanks for your answer. I just did the same:

root@pxtrial22:~# apt-get install apcupsd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
apcupsd-doc
Suggested packages:
apcupsd-cgi hal
The following NEW packages will be installed:
apcupsd apcupsd-doc
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/932 kB of archives.
After this operation, 2,888 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Selecting previously deselected package apcupsd.
(Reading database ... 28358 files and directories currently installed.)
Unpacking apcupsd (from .../apcupsd_3.14.8-2_amd64.deb) ...
Selecting previously deselected package apcupsd-doc.
Unpacking apcupsd-doc (from .../apcupsd-doc_3.14.8-2_all.deb) ...
Processing triggers for man-db ...
Setting up apcupsd (3.14.8-2) ...
update-rc.d: warning: apcupsd start runlevel arguments (1 2 3 4 5) do not match LSB Default-Start values (2 3 4 5)
update-rc.d: warning: apcupsd stop runlevel arguments (0 6) do not match LSB Default-Stop values (0 1 6)
Starting UPS power management: apcupsd.
Setting up apcupsd-doc (3.14.8-2) ...
root@pxtrial22:~# service apcupsd status
Error contacting apcupsd @ localhost:3551: Connection refused
root@pxtrial22:~#

It is just a fresh installation of Proxmox 2.2 and updated with "apt-get update" and
"apt-get dist-upgrade" ... so is there something else I have to configure in Proxmox ?
Perhaps a firewall setting ?

Greetings Marco.
 
Hello again,

I checked again my config and found that I set SNMP for the upstype and then in the device-section I didn´t set the port (xx:161:xx:xxx)! AAARGGHH !

It could be so easy. Sorry for me causing inconvenience.

Greetings Marco.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!