Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: imcintyre on April 09, 2007, 09:42:06 PM
-
I'd like to know if anybody has had a similar problem and if so, they think that excess heat might be my problem.
This morning I received the following email message from my test server
Communications with UPS UPS@localhost lost
followed by this email every 5 minutes
UPS UPS@localhost is unavailable
When I went to the room where the server, and a bunch of other equipment, is located I found that it was 32 degrees C. The APC website says up to 40C. I rebooted everything and opened the door to the room.
My next emails were one right after the other; Communications with UPS UPS@localhost established
and then
Communications with UPS UPS@localhost lost
However, it did not repeat itself.
I log in as root and run the following code and get the following answer, so everything looks ok.
[root@mailbox1 ~]# upsc UPS@192.168.1.***
battery.charge: 100
battery.chemistry: PbAc
battery.runtime: 2827
battery.voltage: 1.2
driver.name: hidups
driver.parameter.port: /var/lib/ups/hiddev0
driver.version: 2.0.5
ups.delay.shutdown: -1
ups.load: 18
ups.mfr: American Power Conversion
ups.model: Back-UPS RS 1000 FW:7.g8 .D USB FW:g8
ups.serial: JB0406007106
ups.status: OL
[root@mailbox1 ~]#
-
I log in as root and run the following code and get the following answer, so everything looks ok.
[root@mailbox1 ~]# upsc UPS@192.168.1.***
battery.charge: 100
battery.chemistry: PbAc
battery.runtime: 2827
battery.voltage: 1.2
driver.name: hidups
driver.parameter.port: /var/lib/ups/hiddev0
driver.version: 2.0.5
ups.delay.shutdown: -1
ups.load: 18
ups.mfr: American Power Conversion
ups.model: Back-UPS RS 1000 FW:7.g8 .D USB FW:g8
ups.serial: JB0406007106
ups.status: OL
[root@mailbox1 ~]#
That does not look OK.
-driver.name: hidups <This is an old depreciated driver, you shouldn't use it. Use newhidups instead.
-There should be more information (My RS 1500 has 30 lines).
-battery.voltage: 1.2 <This is not correct, AFAIK all RS model use a 24 volt battery setup.
Did you change the default configuration? What does this show (remove your passwords please)?
config show nut
-
Thanks for your help
As requested:
[root@myserver ~]# config show nut
nut=service
Model=hidups
status=enabled
[root@myserver ~]#
I also ran the uspc command to see if anything changed:
[root@myserver ~]# upsc UPS@192.168.1.***
battery.charge: 100
battery.chemistry: PbAc
battery.runtime: 2745
battery.voltage: 1.2
driver.name: hidups
driver.parameter.port: /var/lib/ups/hiddev0
driver.version: 2.0.5
ups.delay.shutdown: -1
ups.load: 19
ups.mfr: American Power Conversion
ups.model: Back-UPS RS 1000 FW:7.g8 .D USB FW:g8
ups.serial: JB0406007106
ups.status: OL
[root@mailbox1 ~]#
As an aside, what are those passwords doing there? and what are they the passwords for?
-
As recommended, I changed the driver with the following result.
[root@myserver ~]# config setprop nut status disable
[root@myserver ~]# config setprop nut Model newhidups
[root@myserver ~]# config setprop nut status enabled
[root@myserver ~]# config show nut
nut=service
Model=newhidups
status=enabled
[root@myserver ~]# expand-template /etc/sysconfig/ups
[root@myserver ~]# expand-template /etc/ups/ups.conf
[root@myserver ~]# expand-template /etc/ups/upssched.conf
[root@myserver ~]# expand-template /etc/ups/upsmon.conf
[root@myserver ~]# expand-template /etc/ups/upsd.users
[root@myserver ~]# expand-template /etc/ups/upsd.conf
[root@myserver ~]# /etc/rc7.d/S15nut restart
Stopping UPS monitor: [ OK ]
Stopping upsd: [ OK ]
Shutting down upsdrvctl: Network UPS Tools - UPS driver controller 2.0.5
Can't open /var/run/nut/newhidups-UPS.pid: No such file or directory
Starting upsdrvctl: [ OK ]
Starting upsd: [ OK ]
Starting UPS monitor (master): [ OK ]
[root@myserver ~]# config show nut
nut=service
Model=newhidups
status=enabled
[root@myserver ~]# upsc UPS@192.168.1.***
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.date: 2001/09/25
battery.mfr.date: 2004/02/03
battery.runtime: 2745
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 26.9
battery.voltage.nominal: 24.0
driver.name: newhidups
driver.parameter.port: /var/lib/ups/hiddev0
driver.version: 2.0.5
driver.version.data: APC/CyberPower HID 0.9
driver.version.internal: 0.30
input.transfer.high: 138
input.transfer.low: 97
input.voltage: 120.0
input.voltage.nominal: 120
ups.beeper.status: disabled
ups.delay.shutdown: -1
ups.firmware: 7.g8 .D
ups.firmware.aux: g8
ups.load: 19
ups.mfr: American Power Conversion
ups.mfr.date: 2004/02/03
ups.model: Back-UPS RS 1000
ups.serial: JB0406007106
ups.status: OL
ups.test.result: No test initiated
[root@myserver ~]#
Given your comments about the voltage, this looks better, although I am uncertain about the line: Can't open /var/run/nut/newhidups-UPS.pid: No such file or directory
I can look around for this line but is it something you recognize as legit?
Edit: Zaro boogs found
Thx again
-
As an aside, what are those passwords doing there? and what are they the passwords for?
Those are there so you can configure master/slave servers connected to the same UPS if you want.
Can't open /var/run/nut/newhidups-UPS.pid: No such file or directory
This is caused because the driver stops and starts too fast. There is/was a bug on the issue but I beleive it has been fixed but not yet released. You can avoid the error by issuing a "stop" wait 5 seconds and then "start" instead of restart.
-
Great, I really appreciate your help. It seems to be working perfectly. I unplugged the device, waited a minute then plugged it back in and received emails telling me that it was on battery and then back on line.
I did read a post that stated a "signal event post upgrade and a signal post event reboot" was required, but that would seem to not be the case.
Is this the case or not?
Thx in advance.
-
Great, I really appreciate your help. It seems to be working perfectly. I unplugged the device, waited a minute then plugged it back in and received emails telling me that it was on battery and then back on line.
I did read a post that stated a "signal event post upgrade and a signal post event reboot" was required, but that would seem to not be the case.
Is this the case or not?
Thx in advance.
post-upgrade/reboot required for what?
It is required for certian things but not *usually* for configuration changes (there are a few exceptions). It is usually required for software installs/updates, especially if the package starts with "smeserver-" or "e-smith-".
When in doubt, you can safely post-upgrade/reboot any time.