search for: raathm

...ale data: After stale data: $ lsusb -d 0665: Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial After stale data: And the gzipped log attached: On 2 January 2015 at 21:56, Charles Lepple <clepple at gmail.com> wrote: > On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > > Not sure what other logs I can provide to try to troubleshoot this? > > > Two things: > > - the output of 'lsusb -d 0665:' before and after the 'stale data' warning > - the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&...

...rv_qx -a apollo-ups -DD 2>&1 command is the same as in the previous attachment. I truncated the "before" log because it just carried on with the same output after the broadcast notification that the UPS became unavailable (at 214.883342). On 2 January 2015 at 22:14, Mike Raath <raathm at gmail.com> wrote: > Ok - before stale data: > > After stale data: > > $ lsusb -d 0665: > > Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > > > After stale data: > > > And the gzipped log attached: > > > > On 2 January...

On Jan 2, 2015, at 3:33 PM, Mike Raath <raathm at gmail.com> wrote: > Sorry, I messed up my reply a bit. > > The output of the lsusb command is the same before and after the data goes stale. > > $ lsusb -d 0665: > Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial > OK. That usually means that the V...

...$ upsc apollo-ups at localhost Init SSL without certificate database Error: Data stale Not sure what other logs I can provide to try to troubleshoot this? Thanks Mike On 2 January 2015 at 21:04, Charles Lepple <clepple at gmail.com> wrote: > On Jan 2, 2015, at 1:07 PM, Mike Raath <raathm at gmail.com> wrote: > > I built a single VM to monitor the UPS (Ubuntu Server 14.04 i386) and > installed NUT on the box from the apt packages. I set it up as per the > previous box with the blazer_usb driver and all goes well, for a while. > Initially, the UPS reports correctly...

On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > Not sure what other logs I can provide to try to troubleshoot this? > Two things: - the output of 'lsusb -d 0665:' before and after the 'stale data' warning - the output of '/lib/nut/nutdrv_qx -a apollo-ups -DD 2>&1 | tee /tmp/nutdrv_q...

On Jan 2, 2015, at 1:07 PM, Mike Raath <raathm at gmail.com> wrote: > I built a single VM to monitor the UPS (Ubuntu Server 14.04 i386) and installed NUT on the box from the apt packages. I set it up as per the previous box with the blazer_usb driver and all goes well, for a while. Initially, the UPS reports correctly via upsc, but after...

Hi Having followed this guide: http://blog.shadypixel.com/monitoring-a-ups-with-nut-on-debian-or-ubuntu-linux/and seeing support for Apollo UPSes mentioned on the compatibility list (genericups, type=4) I tried to set up Nut as follows. OS: Ubuntu Server 12.04 Nut: 2.6.3 (I believe - from Ubuntu repos) ups.conf: > [apollo] > driver = genericups > upstype = 4 > port = /dev/ttyUSB0

A couple of years ago, Arnaud helped me get my Apollo Line Interactive UPS working, using the blazer_usb driver. Now I've run into another problem, having rebuilt my HP Proliant Microserver into an ESXi 5.5 managed hypervisor with various VMs. One of the VMs is a FreeNAS server which manages the storage for the other VMs so graceful shutdowns are important. I built a single VM to monitor the

(sorry about the top-posting) I did a killall on blazer_usb and nutdrv_qx, then did a lsusb, got the following: $ lsusb -d 0665: Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial Then I started the driver in DDD mode, log attached, beyond the point where communication fails (591.465153). Lastly, I did the lsusb again and got this: $ lsusb -d 0665: Bus 002 Device 005: ID

As per request by Arnaud in the users list Device manufacturer: Apollo Device name: 1085VC (Retailer's product page: http://shop.esquire.co.za/ProductDescription.aspx?id=583072) upsc on mains power: > $ upsc apollo > battery.voltage: 13.50 > battery.voltage.nominal: 12.0 > beeper.status: enabled > device.mfr: > device.model: > device.type: ups > driver.name:

On Jan 2, 2015, at 4:27 PM, Mike Raath <raathm at gmail.com> wrote: > Maybe usbpassthrough is something I should look at? I'll do some reading. You may have found this already, but this (plus the followup KB item #1021345) seems to imply that you can bind the USB-to-serial adapter to the NUT VM: http://kb.vmware.com/selfservice/mic...

Thanks Dan and Charles - I've found the usb passthrough will be a non-starter (not supported on my host). Dan - is your recommendation to build Nut from source or just the driver? I'm trying to build the whole project but am obviously missing dependencies... I've come across a configure error syntax error near unexpected token `CPPUNIT,' which I've seen in a previous

> We need to make sure this isn't something vm-related I suspect that this is definitely vm related now. I've tried Ubuntu server 10.10 as you suggested, and also Debian wheezy and both do the same thing. I saw in another thread that the author of the .vib of nut for ESXi is on this mailer - hopefully he can shed some light on what's happening. I would even be happy if I can

> Hope this helps. It did - thanks! I managed to hack around a bit earlier and did produce the driver binary but thought I would try from fresh with your steps and got the binary. Unfortunately the problem is still there... after a while connection is lost, updates stop, and upsc reports stale data. Log attached. What I'm thinking now is that I should run a cron job that regularly