similar to: Can't connect to UPS [mustek] (megatec-mustek): No such file or directory

O.S. Ubuntu 10.10, Maverick Meerkat 32 bit. NUT 2.4.3-1ubuntu5, package installed Belkin F6C1500-TW-RK I am having trouble starting uspd whenever I add a client from my lan to uspd.conf: LISTEN 127.0.0.1 3493 LISTEN 192.168.36.106 3493 naknight at nak-server:~$ sudo upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added 127.0.0.1:3493 0.000093 listen_add:

$ sudo /usr/sbin/upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added ::1:3493 0.000084 listen_add: added 127.0.0.1:3493 0.000102 setuptcp: try to bind to 127.0.0.1 port 3493 0.000185 listening on 127.0.0.1 port 3493 0.000204 setuptcp: try to bind to ::1 port 3493 0.001328 setuptcp: socket: Address family not supported by protocol 0.001381

hi, I recently upgraded my Debian Lenny system to Squeeze, and have been happily running nut as a MODE=standalone system talking to my Cyberpower 1500 avr lcd via the usbhid-ups driver for a couple of weeks or so. No problems. Now I'm trying to hang another machine off the same ups as a slave, and it isn't working. The problem I'm getting is best illustrated by what

Hello, I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. The attached UPS is an APC xs1500 (model bx1500g). The connection is an RJ45 to USB cable. Here is my ups.conf: [xs1500] driver = usbhid-ups port = auto desc = "APC Back-UPS xs1500" The problem I am encountering is upsd crashing with an 'Out of memory' error. I can

Hi Arjen, in server/upsd.c r731, you moved the call conf_load() from after check_perms() (~ l.1020) to before setupsignals() (~ l.989). The problem is that conf_load() needs to open the ups driver socket, and it assumes that STATEPATH is the current working directory. The directory is only set in l.1016. Therefore, the first attempt to open a socket will always fail. From the user's point of

On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> wrote: > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. I am not sure why they are not listed on the main download page, but there are actually three Windows MSI releases after that: http://www.networkupstools.org/package/windows/ I

I finally got some free time and uploaded 1.0alpha4. It will arrive in the archive by tomorrow afternoon. Together with the most recent libssl0.9.8 upgrade I think this will fix the SSL problems users have been facing. -- Jaldhar H. Vyas <jaldhar at debian.org> La Salle Debain - http://www.braincells.com/debian/

Hi, a few days ago, I bought some of those Mustek UPSes that have both a serial and a USB connector. Currently only the serial port is supported by the megatec driver. This works fine so far. Now I have seen there is a megatec_usb driver, which currently only supports 2 other UPSes. How can I help to find out whether the PowerMust might actually work with the megatec_usb driver? -- Regards,

Good day I?m trying to get NUT working on Server 2012 64-bit. I can start the ntpd but as soon as I connect with upsc, the NTPD process exits with the following debug output: c:\Program Files (x86)\NUT\sbin>upsd -DDDD Network UPS Tools upsd 2.6.5-3780M 0.000000 listen_add: added 127.0.0.1:3493 0.000000 listen_add: added ::1:3493 0.015599 setuptcp: try to bind to ::1 port

My apologies, I don't know why my brain is stuck on NTPD, I meant UPSD. Regards Ge-org Brohammer -----Original Message----- From: Nut-upsuser [mailto:nut-upsuser-bounces+ge-org=kingbro.co.za at lists.alioth.debian.org] On Behalf Of Ge-org Brohammer Sent: 28 June 2013 01:06 PM To: nut-upsuser at lists.alioth.debian.org Subject: [Nut-upsuser] Server 2012 - 64bit NTPD Crash Good day I?m

Disclaimer: I've setup APC UPS monitoring and it works... ... but when it comes to mustek powermust 600usb (connected via com-port), I can't make it work. Got NUT installed via aptitude in ubuntu feisty and a basic setup, exactly the same as for the apc, except for the name of the ups and the corresponding section of ups.conf -- [mustek] driver = megatec port = /dev/ttyS1

Hello guys, Please help me to resolve the issue. I bought 'SVEN Power Pro+ 500 USB' UPS few days ago and tried to setup NUT 2.6.0 to work with it. blazer_ups driver doesn't recognize the UPS :( The Manufacturer provides 'PowerD' software for linux with installation instractions on a CD (see example below). --------===------- Welcom to PowerManager System!

Hello ! first off, thank you all for making this piece of software. from what i have seen so far this seems to be a really mature and advanced tool for all sorts of UPS models ! I`d like to tell that I own a UPS which isn`t listed on the compatibility list, but seems to be compatible. It is a PowerWalker - see this at

Hello ! first off, thank you all for making this piece of software. from what i have seen so far this seems to be a really mature and advanced tool for all sorts of UPS models ! I`d like to tell that I own a UPS which isn`t listed on the compatibility list, but seems to be compatible. It is a PowerWalker - see this at

On Tue, Jan 27, 2015 at 5:53 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jan 24, 2015, at 12:45 AM, Ryan Sizemore <ryan.sizemore at gmail.com> > wrote: > > Hello, > > I am trying to get nut running on a Windows 2012 R2 server (x64). I am > using the MSI release of 2.6.5-3. > > > I am not sure why they are not listed on the main download page,

On Jan 2, 2012, at 10:51 AM, Vladimir Micovic wrote: >> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > Unfortunately, this device ID is used by several different vendors. What does "lsusb -vvv -d 0665:5161" show? > Also, what OS and kernel are you using? (I thought certain kernels had USB-to-serial drivers for that chip.) > -- > Charles

Hi, I'm trying to setup my Mustek 600 with USB (no serial ports on my computer) on Gentoo. The configuration I use is: [Mustek] driver = megatec_usb port = auto desc = "Power Mustek 600 USB" The NUT I use on my x86_64 machine is: sys-power/nut-2.4.3-r2 USE="bash-completion ssl usb xml -cgi -hal -snmp" When I start upsdrv I get: weasel ~ # /etc/init.d/upsdrv start

"mustek" is all but deprecated, so the effort should be to get powermust/megatec working. Since you have the latest development code installed, can you please run "/path/to/megatec -DDDD -a the_name_for_your_ups" (this without starting NUT normally - i.e. without upsd, upsmon, etc) and send me the output? The output should help me figure out why you are getting data stale

Hello, fisrt, you should subscribe to the NUT user mailing list to get a good support, since I've personaly no knowledges about such units: http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser Next, you should try the latest nut release (2.0.5 currently, but 2.2.0 soon) and most of all the new megatec driver. 2007/6/10, esva2 at inbox.lv <esva2 at inbox.lv>: > Dear

Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less