Nut upsuser - May 2008 - MGE Ellipse Max 1100 configuration question

Hi,

I bought an Ellipse MAX 1100 a few months ago. First I attached it to my 
desktop and installed mge's personal solution pac. (a graphical 
interface which uses nut). It works. But I want to attach the ups to my 
server which runs without an x-server.
I followed http://opensource.mgeups.com/install/debian.htm. Didn't work.
Then I copied over the configuration files which the personal solution 
pac on my desktop created. But I get the same error as with my manual 
configuration:

May 21 18:56:43 fry upsd[7812]: listening on 0.0.0.0 port 3493
May 21 18:56:43 fry upsd[7812]: Can't connect to UPS [mgeups] 
(usbhid-ups-mgeups): No such file or directory
May 21 18:56:43 fry upsd[7813]: Startup successful
May 21 19:01:43 fry upsd[7813]: Can't connect to UPS [mgeups] 
(usbhid-ups-mgeups): No such file or directory
May 21 19:06:43 fry upsd[7813]: Can't connect to UPS [mgeups] 
(usbhid-ups-mgeups): No such file or directory
May 21 19:11:44 fry upsd[7813]: Can't connect to UPS [mgeups] 
(usbhid-ups-mgeups): No such file or directory

So I started PSPmon my desktopo again and looked into daemon.log. Then I 
noticed that PSP doesn't start nut. So I did. Same error as above.
Why does PSP work and how do I get nut on my server to work with this 
UPS?

-- 
Thank you
Chris

2008/5/21, Chris Cohen <kildau-ml at gmx.de>:
> Hi,
Hi Chris,
> I bought an Ellipse MAX 1100 a few months ago.
excellent choice ;-)
> First I attached it to my
> desktop and installed mge's personal solution pac. (a graphical
> interface which uses nut). It works. But I want to attach the ups to my
> server which runs without an x-server.
> I followed http://opensource.mgeups.com/install/debian.htm. Didn't
work.
these are outdated, and will probably never be updated again.
and I've not yet had time to take care of opensource.mgeops.com
> Then I copied over the configuration files which the personal solution
> pac on my desktop created. But I get the same error as with my manual
> configuration:
>
> May 21 18:56:43 fry upsd[7812]: listening on 0.0.0.0 port 3493
> May 21 18:56:43 fry upsd[7812]: Can't connect to UPS [mgeups]
> (usbhid-ups-mgeups): No such file or directory
> May 21 18:56:43 fry upsd[7813]: Startup successful
> May 21 19:01:43 fry upsd[7813]: Can't connect to UPS [mgeups]
> (usbhid-ups-mgeups): No such file or directory
> May 21 19:06:43 fry upsd[7813]: Can't connect to UPS [mgeups]
> (usbhid-ups-mgeups): No such file or directory
> May 21 19:11:44 fry upsd[7813]: Can't connect to UPS [mgeups]
> (usbhid-ups-mgeups): No such file or directory
>
> So I started PSPmon my desktopo again and looked into daemon.log. Then I
> noticed that PSP doesn't start nut. So I did. Same error as above.
> Why does PSP work and how do I get nut on my server to work with this
> UPS?
to answer your question:
- psp only autodetect your MGE UPS and configure nut.
then the service are started by the system at boot.
- on your master machine (the one running PSP):
   * you have to allow client connection in upsd.conf ("ACL mynetwork
X.X.X.X/Y" and add mynetwork to "ACCEPT")
   * you have to define an "upsmon slave" user in upsd.users
- on your slave machine:
   * you only need upsmon.conf
   * you should only set START_UPSMON to yes in /etc/default/nut
   * you have to point the master machine (the one running PSP) in
upsmon.conf, also using the upsmon slave login/password created above.

For more information: man upsd.conf, upsmon.conf, ... and the online
documentation.

Arnaud
-- 
Linux / Unix Expert R&D - MGE Office Protection Systems -
http://www.mgeops.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
Free Software Developer - http://arnaud.quette.free.fr/

On Thursday 22 May 2008 14:02:06 you wrote:
> > I spent half the night getting this to work... and only got a
> > little further. The only difference I found is:
> >
> > On my Desktop with psp installed, but not running:
> > mrkofee at daisy:~$ sudo /lib/nut/usbhid-ups -a mgeups
> > Network UPS Tools: 0.29 USB communication driver - core 0.32
> > (2.2.1-)
> >
> > Using subdriver: MGE HID 1.01
> >
> > On my Server without psp but exactly the same configuration in
> > /e/n/: mrkofee at fry:~$ sudo /lib/nut/usbhid-ups -a mgeups
> > Network UPS Tools: 0.29 USB communication driver - core 0.32
> > (2.2.1-)
> >
> > No matching HID UPS found
> >
> > Is there anything else I can do? The UPS would be pretty useless
> > without the ability to shut my server down during a blackout.
>
> Try to run the driver with '-u root -DD' to rule out permissions
> problems.
Done. It shut down the UPS and my entire network. :(
But I redirected the output to a file which I attached. (I don't know 
what all this means...)

-- 
Greetings
Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: trace.log
Type: text/x-log
Size: 2505 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080522/79a19fe9/attachment.bin

>> Weird. This is not something the driver can do, unless you
>> specifically tell it to kill the power (-k). I see that you're
using
>> Linux 2.6.24-17-xen.
> I do. (Running Ubuntu Hardy LTS)
The fact that you're able to run this driver on your desktop system
without problems, leads me to believe that the problem is in Xen and not
in either the driver and/or the UPS itself.

A quick search via Google shows that USB support for anything other than a
keyboard and mouse is experimental at best in Xen at the moment, so I
think this may be where the problem is. Since I know crap about Xen (or
any other virtualization software for that matter), I have no idea if and
what can be done to correct this.

One thing that is worth checking, if this system is HAL enabled. In that
case, something like 'hald-addon-hid-ups' might be claiming the UPS and
I
have no idea how well this is handled (if at all).

Best regards, Arjen

Rejected by moderator... had to paste the attachment to 
http://paste.debian.net/3784/

On Thursday 22 May 2008 15:35:28 you wrote:
> >> Try to run the driver with '-u root -DD' to rule out
permissions
> >> problems.
> >
> > Done. It shut down the UPS and my entire network. :(
>
> Weird. This is not something the driver can do, unless you
> specifically tell it to kill the power (-k). I see that you're using
> Linux 2.6.24-17-xen.
I do. (Running Ubuntu Hardy LTS)
> > But I redirected the output to a file which I attached. (I don't
> > know what all this means...)
>
> Well, it appear to detect the UPS all right:
> > Checking device (0463/FFFF) (001/008)
> > - VendorID: 0463
> > - ProductID: ffff
> > - Manufacturer: MGE UPS SYSTEMS
> > - Product: Ellipse MAX
> > - Serial Number: PbAc
> > - Bus: 001
> > Trying to match device
> > Device matches
> > HID descriptor length 882
> > Report Descriptor size = 882
> > Using subdriver: MGE HID 1.01
>
> Short of the weird value reported for the serial number, nothing
> wrong so far. It only looks like it reports the wrong indexed string,
> which is very strange. What does 'lsusb -vvv' report? 
I attached the relevent part as a file since its pretty long.
> I'm not sure if this isn't due to the fact that you seem to be
running
Linux 2.6.24-17-xen. I don't know if the libusb library will work
with
> that.
Hmmm... I could install a non-xen kernel on dom0?

-- 
Thanks
Chris