Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: SoftDux on February 04, 2008, 10:43:29 PM
-
Hi all
I'm trying to get a MGE Nova 1000 USB UPS working with sme, but have had no luck. From this list (http://www.networkupstools.org/compat/stable.html) I can see I need to use the usbhid-ups driver, which I presume in sme is usbhid.
I have actually tried usbhid-ups, usbhid & newhidups - but they all tell me "Driver not connected"
Feb 4 23:41:15 sme upsmon[3734]: UPS UPS@localhost is unavailable
Feb 4 23:41:15 sme wall[7790]: wall: user nut broadcasted 1 lines (34 chars)
Feb 4 23:41:20 sme upsmon[3734]: Poll UPS [UPS@localhost] failed - Driver not connected
Feb 4 23:41:55 sme last message repeated 7 times
Feb 4 23:43:00 sme last message repeated 13 times
Feb 4 23:43:10 sme last message repeated 2 times
Feb 4 23:43:14 sme upsd[3729]: Can't connect to UPS [UPS] (usbhid-UPS): No such file or directory
Feb 4 23:43:15 sme upsmon[3734]: Poll UPS [UPS@localhost] failed - Driver not connected
So, what other drivers can I use? Or how do I get sme to talk to this UPS?
-
I'm trying to get a MGE Nova 1000 USB UPS working with sme, but have had no luck.
As it says every time you post here:
Don't report problems here - Please report bugs and potential bugs in the bug tracker
-
So, what other drivers can I use? Or how do I get sme to talk to this UPS?
Have you looked at the man page.
man usbhid-ups
-
As it says every time you post here:
Don't report problems here - Please report bugs and potential bugs in the bug tracker
I'm sorry to say this, but I find you very rude. WHO SAID ANYTHING ABOUT A BUG????? If I knew it doesn't work, then why would I bother spending thousands buying new UPS's for the company????? Please, if you can't give constructive advice, then rather don't
-
Have you looked at the man page.
man usbhid-ups
Thank you, william_syd. I didn't know that usbhid-ups is a command, and had a man page :) I have searched the forums looking for an answer to this, and a lot dates back more than 6 months ago, with little to no exact resolution to the problem. ..... checking it now :)
-
I'm sorry to say this, but I find you very rude. WHO SAID ANYTHING ABOUT A BUG????? If I knew it doesn't work, then why would I bother spending thousands buying new UPS's for the company????? Please, if you can't give constructive advice, then rather don't
Hello Steve,
Please do not take offence at Charlie's comment. It is short and to the point (an occupational hazard for most developpers) chiefly because of the need to manage the significant workload carried out on a voluntary basis by the Development Team in general, and Charlie in particular. The SME server has been designed to work "out of the box" unconditionally. If something does not work, i.e. the interface to a UPS as it appears to be the case here, something is potentially amiss and need to be investigated. The best place to carry this sort of investigation for the Development Team is at Bugzilla, not in the Forum. Filling a Bug Report will not only identify the problem you are now experiencing, it will also allow some documentation to take place in the Wikis if applicable. Hope this helps.
-
Thank you, william_syd. I didn't know that usbhid-ups is a command, and had a man page :) I have searched the forums looking for an answer to this, and a lot dates back more than 6 months ago, with little to no exact resolution to the problem. ..... checking it now :)
Did you look at the wiki?
nutty info (http://wiki.contribs.org/SME_Server:Documentation:Technical_Manual:Chapter4#Nut_UPS_.E2.80.93_Uninterruptable_Power_Supply)
What is the output of
config show nut
and
cat /etc/ups/ups.conf
Oh, and don't bite the hand that feeds you.
-
Hello Steve,
Please do not take offence at Charlie's comment. It is short and to the point (an occupational hazard for most developpers) chiefly because of the need to manage the significant workload carried out on a voluntary basis by the Development Team in general, and Charlie in particular. The SME server has been designed to work "out of the box" unconditionally. If something does not work, i.e. the interface to a UPS as it appears to be the case here, something is potentially amiss and need to be investigated. The best place to carry this sort of investigation for the Development Team is at Bugzilla, not in the Forum. Filling a Bug Report will not only identify the problem you are now experiencing, it will also allow some documentation to take place in the Wikis if applicable. Hope this helps.
Hi burnat
I fully understand the purpose of bugzilla, and also that this whole project is run freely, and I understand all the main guys involvement & contribution towards it. But, I never said there's a problem with sme, if you re-read my 1st post. I'm either doing something wrong, or my UPS is not working properly (which I'm starting to believe right now). If I had a code / product / sme problem, I would have filled it in bugzilla, but since I felt it's something that someone else with either a similar UPS, or knowledge of NUT could help me. I could have used the wrong drivers, or missed a step somewhere. That's not a bug.
And my experience from the bugzilla stuff wasn't very good. It's only being used by people who have serious problems and want a fix, and it can only be fixed if the team feels like it / know it can be fixed / have time for it / there's enoug interest, etc. But on the forums, my question have more exposure, and someone not on the team might have a solution for me.
william_syd:
I have look through that nutty info page, and it didn't help much. I also searched & read through every forum post with USB & UPS in it (I skipped those relating to other USB devices like HDD's)
Here's the output of those commands:
[root@sme ~]# config show nut
nut=service
Device=/dev/hiddev0
MasterPass=794420176403932
Model=usbhid
SlavePass=751336777253836
status=enabled
[root@sme ~]# cat /etc/ups/ups.conf
Broadcast message from nut (Tue Feb 5 10:09:47 2008):
UPS UPS@localhost is unavailable
#------------------------------------------------------------
# !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at http://www.contribs.org/development/
#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------
[UPS]
driver = usbhid
port = /dev/hiddev0
Here's some recent output from /var/log/messages:
Feb 5 10:08:08 sme last message repeated 4 times
Feb 5 10:08:09 sme upsmon[7046]: Signal 15: exiting
Feb 5 10:08:09 sme upsd[7041]: Client upsmaster@127.0.0.1 logged out
Feb 5 10:08:09 sme upsmon[7045]: upsmon parent: read
Feb 5 10:08:09 sme ups: upsmon shutdown succeeded
Feb 5 10:08:09 sme upsd[7041]: Signal 15: exiting
Feb 5 10:08:09 sme ups: upsd shutdown succeeded
Feb 5 10:08:09 sme upsdrvctl: Network UPS Tools - UPS driver controller 2.2.0-
Feb 5 10:08:09 sme upsdrvctl: Can't start /sbin/usbhid: No such file or directory
Feb 5 10:08:09 sme ups: upsdrvctl startup failed
Feb 5 10:08:09 sme upsd[7105]: listening on 0.0.0.0 port 3493
Feb 5 10:08:09 sme upsd[7105]: Can't connect to UPS [UPS] (usbhid-UPS): No such file or directory
Feb 5 10:08:09 sme upsd[7106]: Startup successful
Feb 5 10:08:09 sme upsd: listening on 0.0.0.0 port 3493
Feb 5 10:08:09 sme upsd: Can't connect to UPS [UPS] (usbhid-UPS): No such file or directory
Feb 5 10:08:09 sme ups: upsd startup succeeded
Feb 5 10:08:09 sme upsmon[7110]: Startup successful
Feb 5 10:08:09 sme upsmon: UPS: UPS@localhost (master) (power value 1)
Feb 5 10:08:09 sme upsmon: Using power down flag file /etc/killpower
Feb 5 10:08:09 sme upsmon:
Feb 5 10:08:09 sme ups: upsmon startup succeeded
Feb 5 10:08:09 sme upsd[7106]: Connection from 127.0.0.1
Feb 5 10:08:09 sme upsd[7106]: Client upsmaster@127.0.0.1 logged into UPS [UPS]
Feb 5 10:08:09 sme upsmon[7111]: Poll UPS [UPS@localhost] failed - Driver not connected
Feb 5 10:08:09 sme upsmon[7111]: Communications with UPS UPS@localhost lost
Feb 5 10:08:09 sme wall[7115]: wall: user nut broadcasted 1 lines (44 chars)
Broadcast message from nut (Tue Feb 5 10:08:14 2008):
UPS UPS@localhost is unavailable
Feb 5 10:08:14 sme upsmon[7111]: Poll UPS [UPS@localhost] failed - Driver not connected
Feb 5 10:08:14 sme upsmon[7111]: UPS UPS@localhost is unavailable
Feb 5 10:08:14 sme wall[7133]: wall: user nut broadcasted 1 lines (34 chars)
-
Is your device setting correct and your model ?
[root@tiger ~]# config show nut
nut=service
MasterPass=916298637955101
Model=usbhid-ups
SlavePass=315852908080234
status=disabled
[root@tiger ~]#
Out of the box I have /var/lib/ups/hiddev0
[root@tiger ~]# cat /etc/ups/ups.conf
#------------------------------------------------------------
# !!DO NOT MODIFY THIS FILE!!
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at http://www.contribs.org/development/
#
# Copyright (C) 1999-2006 Mitel Networks Corporation
#------------------------------------------------------------
[UPS]
driver = usbhid-ups
port = /var/lib/ups/hiddev0
[root@tiger ~]#
It must be the default when no Device is set in the db property. The template would confirm this.
Oh, I don't use a USB UPS.
Any errors from
[root@tiger ~]# /etc/rc7.d/S38nut start
-
[root@sme ~]# config show nut
nut=service
Device=/dev/hiddev0
MasterPass=794420176403932
Model=usbhid
SlavePass=751336777253836
status=enabled
These settings won't work with a USB UPS. Try
config delprop nut Device <<<NOTICE that says "delprop", you need to delete that property.
config setprop nut Model upshid-ups
expand-template /etc/ups/ups.conf
Now show the output of:
/etc/rc7.d/S38nut stop
wait 5 seconds
/etc/rc7.d/S38nut start
-
It seems the UPS itself was faulty after all. I took it in for repairs, and they swapped it out for another one, but this is a different brand, aparently a blazer (which I don't like, since one can't silence them), and it has a serial port. I'll try and set it up soon