Re: [Nut-upsuser] Zigor Ebro 650 compatibility
On 08/09/2012, at 5:01, Martyn Hill wrote: >> Windows may be connecting to the UPS using a service automatically. I am not >> sure how you would stop it but at a guess I would trying looking for a >> likely service and stop it. > > Yes, thought of that and stopped and reconfigured for manual startup the > Upsilon USB service and even removed the UPS USB driver, but still hit the > same 'busy' error when trying to attch the USB device to VirtualBox. OK, I'm not sure how you could fix that :( Sounds like a VirtualBox bug. >> What does pkg-config --cflags libusb say on your system? > 'Not found' - probably because I didn't/couldn't install the libusb-0.1.12 > port - even after disabling the FreeBSD version check in the Makefile that > would otherwise skip the port install. I'l try that again, however and try to > get make install to complete. I just double checked my system and there is a stub port which installs a libusb-config script and /usr/local/libdata/pkgconfig/libusb*.pc to point to the base library (which has shims for libusb 0.1 and 1.0 APIs). If you install /usr/ports/devel/libusb_base then pkg-config should find libusb (and so should NUTs configure script). -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Zigor Ebro 650 compatibility
Hi Daniel Thank you for that. On 07/09/2012 01:15, Daniel O'Connor wrote: On 07/09/2012, at 5:01, Martyn Hill wrote: Unfortunately, VirtualBox refused to allow me to attach the UPS USB port to the guest OS (saying 'busy with a previous request'), so that came to nothing - and after several night's effort::-( Windows may be connecting to the UPS using a service automatically. I am not sure how you would stop it but at a guess I would trying looking for a likely service and stop it. Yes, thought of that and stopped and reconfigured for manual startup the Upsilon USB service and even removed the UPS USB driver, but still hit the same 'busy' error when trying to attch the USB device to VirtualBox. So, do you (or anyone else here) have any guidance on how to force NUT to link against libusb-0.1 at compile time ??? I think you'd have to mangle the configure script. I'll take a look. What does pkg-config --cflags libusb say on your system? 'Not found' - probably because I didn't/couldn't install the libusb-0.1.12 port - even after disabling the FreeBSD version check in the Makefile that would otherwise skip the port install. I'l try that again, however and try to get make install to complete. I'm still not convinced that the FreeBSD implementation of libusb v2 is fully compatible with v0.1 - the available documentation is confusing... I believe it is compatible although 0.1 was evolved rather than designed :) -- Daniel O'Connor software and network engineer I'll keep trying! Thanks! -- "There are 10 types of people in this world. Those who understand binary and those who don't." ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Communications with UPS lost: No status from UPS
The expected behavior is fine :) I updated again becouse with 2.6.4 i found a bug about upssched so now with 2.6.5 all is working great. Thank you again. Happy to use NUT. From: Arnaud Quette Sent: Friday, September 07, 2012 5:15 PM To: Fabio Cecamore Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Communications with UPS lost: No status from UPS 2012/9/6 Fabio Cecamore Updated to the last (in the testing debian repository) available: 2.6.4 This time using blazer_ser in debug i find: 363.373978read: '(233.9 140.0 233.9 006 49.8 13.7 30.7 1001' 365.162745send: 'Q1' 366.163904read: timeout 366.163991blazer_status: short reply 366.164013Communications with UPS lost: status read failed! 367.163804send: 'Q1' 367.378009read: '(234.3 140.0 234.3 006 49.4 13.7 30.7 1001' But this time in syslogd.log no error.. i’ll check more and will let you know. so the expected behavior is fine? (to be confirmed) (nice to see an other android user) they are everywhere ;) cheers, Arnaud ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] ERR ACCESS-DENIED in upsrw
Oh nice, with offdelay i can do the same think so.. Thankyou :) Fabio From: Arnaud Quette Sent: Friday, September 07, 2012 3:44 PM To: Fabio Cecamore Cc: Charles Lepple ; nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] ERR ACCESS-DENIED in upsrw 2012/9/7 Fabio Cecamore I've done what you said but now.. root@ProLiant:/home/fabio# upsrw -u admin -p mypass -s ups.delay.shutdown=180 ups Unexpected response from upsd: ERR READONLY root@ProLiant:/home/fabio# I hope this not mean this variable is readonly.. hem Fabio, I'm sure you're actually kiding with your comment ;) To get the list of variables that can be set, use "upsrw ". You will see that ups.delay.shutdown is not present. What you probably want is to configure the delay before powering off the UPS, at the end of the shutdown sequence. Just use "offdelay = " in ups.conf, as described in the blazer manpage: http://www.networkupstools.org/docs/man/blazer.html cheers, Arnaud -- Linux / Unix / Opensource Engineering Expert - Eaton - http://opensource.eaton.com Network UPS Tools (NUT) 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
Re: [Nut-upsuser] Communications with UPS lost: No status from UPS
2012/9/6 Fabio Cecamore > Updated to the last (in the testing debian repository) available: 2.6.4 > This time using blazer_ser in debug i find: > > 363.373978read: '(233.9 140.0 233.9 006 49.8 13.7 30.7 1001' > 365.162745send: 'Q1' > 366.163904read: timeout > 366.163991blazer_status: short reply > 366.164013Communications with UPS lost: status read failed! > 367.163804send: 'Q1' > 367.378009read: '(234.3 140.0 234.3 006 49.4 13.7 30.7 1001' > > But this time in syslogd.log no error.. i’ll check more and will let you > know. > so the expected behavior is fine? (to be confirmed) > (nice to see an other android user) > they are everywhere ;) cheers, Arnaud ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] ERR ACCESS-DENIED in upsrw
2012/9/7 Fabio Cecamore > I've done what you said but now.. > > root@ProLiant:/home/fabio# upsrw -u admin -p mypass -s > ups.delay.shutdown=180 ups > Unexpected response from upsd: ERR READONLY > root@ProLiant:/home/fabio# > > I hope this not mean this variable is readonly.. > hem Fabio, I'm sure you're actually kiding with your comment ;) To get the list of variables that can be set, use "upsrw ". You will see that ups.delay.shutdown is not present. What you probably want is to configure the delay before powering off the UPS, at the end of the shutdown sequence. Just use "offdelay = " in ups.conf, as described in the blazer manpage: http://www.networkupstools.org/docs/man/blazer.html cheers, Arnaud -- Linux / Unix / Opensource Engineering Expert - Eaton - http://opensource.eaton.com Network UPS Tools (NUT) 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
Re: [Nut-upsuser] ERR ACCESS-DENIED in upsrw
I've done what you said but now.. root@ProLiant:/home/fabio# upsrw -u admin -p mypass -s ups.delay.shutdown=180 ups Unexpected response from upsd: ERR READONLY root@ProLiant:/home/fabio# I hope this not mean this variable is readonly.. -Messaggio originale- From: Charles Lepple Sent: Friday, September 07, 2012 12:55 PM To: Fabio Cecamore Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] ERR ACCESS-DENIED in upsrw On Sep 7, 2012, at 3:22 AM, Fabio Cecamore wrote: Hi all, i've a problem with only a command in all suite: upsrw. root@ProLiant:/etc/nut# upsrw -u monmaster -p p455w0rd -s ups.delay.shutdown=180 ups Unexpected response from upsd: ERR ACCESS-DENIED root@ProLiant:/etc/nut# upsc and upsmon work greatly. This is in my /etc/host.allow: upsd : localhost, LOCAL, 127.0.0.1,[::1] : ALLOW In upsd.users, you need a user entry which allows the "SET" action. I'd recommend not using the "monmaster" user, but you could add to that entry temporarily. The upsd.users man page has an example "admin" user which would work: http://www.networkupstools.org/docs/man/upsd.users.html -- 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] ERR ACCESS-DENIED in upsrw
On Sep 7, 2012, at 3:22 AM, Fabio Cecamore wrote: > Hi all, > i've a problem with only a command in all suite: upsrw. > > root@ProLiant:/etc/nut# upsrw -u monmaster -p p455w0rd -s > ups.delay.shutdown=180 ups > Unexpected response from upsd: ERR ACCESS-DENIED > root@ProLiant:/etc/nut# > > upsc and upsmon work greatly. > > This is in my /etc/host.allow: > upsd : localhost, LOCAL, 127.0.0.1,[::1] : ALLOW In upsd.users, you need a user entry which allows the "SET" action. I'd recommend not using the "monmaster" user, but you could add to that entry temporarily. The upsd.users man page has an example "admin" user which would work: http://www.networkupstools.org/docs/man/upsd.users.html -- 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
[Nut-upsuser] ERR ACCESS-DENIED in upsrw
Hi all, i've a problem with only a command in all suite: upsrw. root@ProLiant:/etc/nut# upsrw -u monmaster -p p455w0rd -s ups.delay.shutdown=180 ups Unexpected response from upsd: ERR ACCESS-DENIED root@ProLiant:/etc/nut# upsc and upsmon work greatly. This is in my /etc/host.allow: upsd : localhost, LOCAL, 127.0.0.1,[::1] : ALLOW What miss ? Thank you! ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
