Re: [Nut-upsuser] driver looking for MAXIM MXE II

[Walter O. Dari]

El 28/11/12 03:00, Kjell Claesson escribió:

I think Arnaud was referring to the NUT version.
The blazer_usb have been updated so you would need NUT 2.6.4
to make it recognise the ups.



Ops ... sorry!:-(

Then I'll change the version of nut.

Thank you very much!



Regards
Kjell Claesson


Regards,
Walter O. Dari

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] driver looking for MAXIM MXE II

[Kjell Claesson]

On Wednesday 28 November 2012 02.18.37 Walter O. Dari wrote:

Hi Walter:

> Hi Arnaud:
> 
> El 24/11/12 12:49, Arnaud Quette escribió:
> > You will need at least 2.6.4 for this unit, but it's really blazer_usb.
> 
> I installed a newer kernel, the 3.2.0, did not work.
> 

I think Arnaud was referring to the NUT version.
The blazer_usb have been updated so you would need NUT 2.6.4
to make it recognise the ups.

Regards
Kjell Claesson


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] driver looking for MAXIM MXE II

[Walter O. Dari]

Hi Arnaud:

El 24/11/12 12:49, Arnaud Quette escribió:

You will need at least 2.6.4 for this unit, but it's really blazer_usb.


I installed a newer kernel, the 3.2.0, did not work.

Here are some facts that can help ...

wodari@svrsw2:~$ uname -a 

Linux svrsw2 3.2.0-0.bpo.4-amd64 #1 SMP Debian 3.2.32-1~bpo60+1 x86_64 
GNU/Linux


wodari@svrsw2:~$ lsusb -v

...
... 



Bus 002 Device 002: ID 06da:0201 Phoenixtec Power Co., Ltd
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x06da Phoenixtec Power Co., Ltd
  idProduct  0x0201
  bcdDevice0.00
  iManufacturer   3
  iProduct1
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength   34
bNumInterfaces  1
bConfigurationValue 1
iConfiguration  0
bmAttributes 0xa0
  (Bus Powered)
  Remote Wakeup
MaxPower  200mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.11
  bCountryCode0 Not supported
  bNumDescriptors 1
  bDescriptorType34 Report
  wDescriptorLength  27
 Report Descriptors:
   ** UNAVAILABLE **
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval  10
cannot read device status, Operation not permitted (1)

...
...

wodari@svrsw2:/etc/nut$ ls -l
total 52
-rwxr--r-- 1 root root  1072 may 30 19:10 hosts.conf
-rwxr--r-- 1 root root  1428 nov 23 04:56 nut.conf
-rwxr--r-- 1 root nut   3850 nov 28 01:47 ups.conf
-rwxr--r-- 1 root nut   1780 may 30 19:10 upsd.conf
-rwxr--r-- 1 root nut   1970 may 30 19:10 upsd.users
-rwxr--r-- 1 root nut  11913 may 30 19:10 upsmon.conf
-rwxr--r-- 1 root nut   3883 may 30 19:10 upssched.conf
-rwxr--r-- 1 root root  1420 may 30 19:10 upsset.conf
-rwxr--r-- 1 root root  4003 may 30 19:10 upsstats.html
-rwxr--r-- 1 root root  6644 may 30 19:10 upsstats-single.html


ups.conf
--
[maxim]
driver = blazer_usb
bus = "002"
port = auto
vendorid = 06da
productid = 0201
serial = "0"
vendor = "Phoenixtec Power Co., Ltd"
desc = "SW servers"
--


wodari@svrsw2:~$ /sbin/upsdrvctl start 


Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
No supported devices found. Please check your device availability with 
'lsusb'

and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these 
options

(man 8 blazer).

Driver failed to start (exit status=1)


As root...

root@svrsw2:~# /sbin/upsdrvctl start
Network UPS Tools - UPS driver controller 2.4.3
Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3)
No supported devices found. Please check your device availability with 
'lsusb'

and make sure you have an up-to-date version of NUT. If this does not help,
try running the driver with at least 'subdriver', 'vendorid' and 'productid'
options specified. Please refer to the man page for details about these 
options

(man 8 blazer).

Driver failed to start (exit status=1)



I tried running ...

root@svrsw2:~# udevadm control --reload-rules

and

root@svrsw2:~# udevadm trigger

... did not work.


What else I can try?


Regards,
Walter





Cheers,
Arnaud
(sent from my S3... please excuse my brevity)

Le 23 nov. 2012 09:40, "Walter O. Dari" mailto:wlin...@gmail.com>> a écrit :

Results:

wodari@svrsw2:/usr/local/__MonitorSoftware$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 06da:0201 Phoenixtec Power Co., Ltd
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Devi

Re: [Nut-upsuser] NOTIFYCMD

[Charles Lepple]

On Nov 27, 2012, at 9:30 AM, lejeczek wrote:

> I'm looking for pager.txt which upsmon.conf mentions of, but could not find 
> it anywhere including the sources?


It has been incorporated into docs/scheduling.txt - I've updated the 
upsmon.conf sample file and man page.

I haven't used it myself, though.

-- 
Charles Lepple
clepple@gmail




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] Kernel crash when using usbhid-ups driver.

[Arnaud Quette]

2012/11/27 Paul Whittaker 

> Hi,
>

Hi Paul,

I've recently added a UPS (CyberPower CP1300EPFCLCD) to one of our
> servers, and I'm managing it with NUT and the usbhid-ups driver.  I've
> configured it to do what we want, and it all works fine. (upsc displays
> information from upsd correctly, upsmon correctly shuts down both the
> server and the UPS when the battery is low, messages are logged when the
> mains supply to the UPS is cut/restored, and so forth.)
>
> However, in the week since installing NUT the server has suffered four
> kernel crashes (on stock 64-bit Ubuntu kernels, currently
> 3.2.0-33-generic) and has been unable to stay up for longer than 12-36
> hours without crashing hard and requiring manual power cycling; this
> system has never previously crashed.  Googling around the issue brings
> up various things, including
> http://thr3ads.net/nut-upsdev/2011/01/1475908-a-nasty-kernel-oops, which
> make me think this could be an existing issue with the
> kernel/library/USB stack that's being triggered by NUT.  I've tried a
> couple of workarounds (including running the driver with -D), but none
> have prevented these lock-ups.
>
> I'd like to use NUT with usbhid-ups to manage the UPS, but also
> (obviously) need to keep the server stable.  If there's a way to do
> this, I'd like to; if not, I've got some crash logs that someone might
> perhaps find useful.
>
> I'm happy to provide more details, but first I'd like to check a few
> basics since I'm new to the list:
>
>  1. Is this the right mailing list to be asking about this?  I can
> imagine the devs would be interested in this, but I'm primarily here as
> a user.
>

yes

 2. Is the Linux USB subsystem already known to be prone to stability
> issues like this, or am I just having some bad luck on this machine?
>

we have had very few issue, and yours is the 2nd (kernel crash with
production release, such as Alfred Ganz) iirc.
and your issue is probably different from Alfred's one, at least in the
symptoms.


>  3. What's the polite way to supply the list with large attachments,
> such as log extracts (~10kB) and photos of kernel crash screens (~900kB)?
>

please send the log here, in compressed form.
are the photos taken with a still cam?
please put these on your website (or any other public storage) and point
the link

a dump file would be preferable:
https://help.ubuntu.com/12.04/serverguide/kernel-crash-dump.html

cheers,
Arnaud
-- 
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] Kernel crash when using usbhid-ups driver.

[Paul Whittaker]

Hi,

I've recently added a UPS (CyberPower CP1300EPFCLCD) to one of our
servers, and I'm managing it with NUT and the usbhid-ups driver.  I've
configured it to do what we want, and it all works fine. (upsc displays
information from upsd correctly, upsmon correctly shuts down both the
server and the UPS when the battery is low, messages are logged when the
mains supply to the UPS is cut/restored, and so forth.)

However, in the week since installing NUT the server has suffered four
kernel crashes (on stock 64-bit Ubuntu kernels, currently
3.2.0-33-generic) and has been unable to stay up for longer than 12-36
hours without crashing hard and requiring manual power cycling; this
system has never previously crashed.  Googling around the issue brings
up various things, including
http://thr3ads.net/nut-upsdev/2011/01/1475908-a-nasty-kernel-oops, which
make me think this could be an existing issue with the
kernel/library/USB stack that's being triggered by NUT.  I've tried a
couple of workarounds (including running the driver with -D), but none
have prevented these lock-ups.

I'd like to use NUT with usbhid-ups to manage the UPS, but also
(obviously) need to keep the server stable.  If there's a way to do
this, I'd like to; if not, I've got some crash logs that someone might
perhaps find useful.

I'm happy to provide more details, but first I'd like to check a few
basics since I'm new to the list:

 1. Is this the right mailing list to be asking about this?  I can
imagine the devs would be interested in this, but I'm primarily here as
a user.

 2. Is the Linux USB subsystem already known to be prone to stability
issues like this, or am I just having some bad luck on this machine?

 3. What's the polite way to supply the list with large attachments,
such as log extracts (~10kB) and photos of kernel crash screens (~900kB)?


Many thanks in advance,

Paul.


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] NOTIFYCMD

[lejeczek]

hi everybody

I'm looking for pager.txt which upsmon.conf mentions of, but 
could not find it anywhere including the sources?


I'd presume that via NOTIFYCMD I could get the stuff emailed,
does anybody have more experience solving such problem?

regards


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] APC UPS: replacement battery always triggers shutdown

[Michal Soltys]

W dniu 26.11.2012 20:42, Arnaud Quette pisze:

Michal, Kastus, Jack,

I have a similar request sitting in the Features requests for years:
https://alioth.debian.org/tracker/index.php?func=detail&aid=304645&group_id=30602&atid=411545

http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-June/000938.html

would you please unite your efforts and bring a patch for NUT FAQ (or
the driver(s))?



Just checked that method with my ups and it seems to be working fine.

Actually the driver would be nice, though after some brief tinkering - 
ups doesn't bother reporting it in capabilities or supported commands, 
so I'd probably opt for experimental "big warning" instant command. This 
would also avoid adding some weird'o'variable like battery.constant ;)




___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser