Re: [Nut-upsuser] Problem with blazer_ser/megatec when upgrading to 2.6.0 from 2.4
What is the output of 'upsd' in the syslog telling you? Note that when running in debug mode, a process will terminate as soon as you close the terminal it is running in or when you kill it with Ctrl-C. Best regards, Arjen Good catch, I looked more in syslog and saw something that I overlooked: Apr 29 09:38:53 krshina3 upsd[8297]: Can't connect to UPS [munja] (megatec-munja): No such file or directory So somehow even as I restarted my PC I somehow messed up and upsd still tried to connect to megatec driver. Then I restarted upsdrv, upsd and upsmon in that order and now it works: Apr 29 09:39:03 krshina3 blazer_ser[12978]: Startup successful Apr 29 09:39:28 krshina3 upsd[8297]: mainloop: Interrupted system call Apr 29 09:39:28 krshina3 upsd[8297]: Signal 15: exiting Apr 29 09:39:29 krshina3 upsd[13062]: listening on 127.0.0.1 port 3493 Apr 29 09:39:29 krshina3 upsd[13062]: Connected to UPS [munja]: blazer_ser-munja Apr 29 09:39:29 krshina3 upsd[13063]: Startup successful Apr 29 09:39:51 krshina3 upsd[13063]: User monuser@127.0.0.1 logged into UPS [munja] Apr 29 09:40:27 krshina3 upsd[13063]: User monuser@127.0.0.1 logged out from UPS [munja] Apr 29 09:40:36 krshina3 upsmon[13135]: Startup successful Apr 29 09:40:36 krshina3 upsd[13063]: User monuser@127.0.0.1 logged into UPS [munja] upsc munja@localhost battery.voltage: 54.00 battery.voltage.nominal: 48.0 beeper.status: disabled device.mfr: device.model: device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.6.0 driver.version.internal: 1.51 input.current.nominal: 0.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 246.5 input.voltage.fault: 140.0 input.voltage.nominal: 230 output.voltage: 246.5 ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: IN03064B ups.load: 4 ups.mfr: ups.model: ups.status: OL ups.temperature: 25.0 temp never changes ups.type: offline / line interactive If you need some more info so you can add this UPS to working list please tell me. Oh and sorry for false alarm :) Have a nice day Dushan ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Problem with blazer_ser/megatec when upgrading to 2.6.0 from 2.4
2011/4/29 Dushan Tcholich dus...@gmail.com What is the output of 'upsd' in the syslog telling you? Note that when running in debug mode, a process will terminate as soon as you close the terminal it is running in or when you kill it with Ctrl-C. Best regards, Arjen Good catch, I looked more in syslog and saw something that I overlooked: Apr 29 09:38:53 krshina3 upsd[8297]: Can't connect to UPS [munja] (megatec-munja): No such file or directory So somehow even as I restarted my PC I somehow messed up and upsd still tried to connect to megatec driver. Then I restarted upsdrv, upsd and upsmon in that order and now it works: Apr 29 09:39:03 krshina3 blazer_ser[12978]: Startup successful Apr 29 09:39:28 krshina3 upsd[8297]: mainloop: Interrupted system call Apr 29 09:39:28 krshina3 upsd[8297]: Signal 15: exiting Apr 29 09:39:29 krshina3 upsd[13062]: listening on 127.0.0.1 port 3493 Apr 29 09:39:29 krshina3 upsd[13062]: Connected to UPS [munja]: blazer_ser-munja Apr 29 09:39:29 krshina3 upsd[13063]: Startup successful Apr 29 09:39:51 krshina3 upsd[13063]: User monuser@127.0.0.1 logged into UPS [munja] Apr 29 09:40:27 krshina3 upsd[13063]: User monuser@127.0.0.1 logged out from UPS [munja] Apr 29 09:40:36 krshina3 upsmon[13135]: Startup successful Apr 29 09:40:36 krshina3 upsd[13063]: User monuser@127.0.0.1 logged into UPS [munja] upsc munja@localhost battery.voltage: 54.00 battery.voltage.nominal: 48.0 beeper.status: disabled device.mfr: device.model: device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.6.0 driver.version.internal: 1.51 input.current.nominal: 0.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 246.5 input.voltage.fault: 140.0 input.voltage.nominal: 230 output.voltage: 246.5 ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: IN03064B ups.load: 4 ups.mfr: ups.model: ups.status: OL ups.temperature: 25.0 temp never changes ups.type: offline / line interactive If you need some more info so you can add this UPS to working list please tell me. as per your information, I've completed the supported VA ratings (Subversion trunk, r2979). cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Problem with blazer_ser/megatec when upgrading to 2.6.0 from 2.4
Hello First things first, thanks for great work with NUT. For years I used Informer compact 3kVA UPS http://www.informups.com/informer_compact.html with nut/megatec serial driver, but it stopped working when I switched to blazer_ser with 2.6.0 upgrade. I'm using 2.6.0 on gentoo. Blazer_ser seems to connect with UPS, but upsmon reports driver not connected. uname -a Linux localhost 2.6.36-gentoo-r7 #3 SMP Tue Feb 8 18:39:54 CET 2011 x86_64 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux Configuration: cat ups.conf | grep # -v [munja] driver = blazer_ser port = /dev/ttyS0 cat upsd.conf | grep # -v LISTEN 127.0.0.1 3493 cat upsd.users | grep # -v [monuser] password = ### cat upsmon.conf | grep # -v MONITOR munja@localhost 1 monuser ## slave MINSUPPLIES 1 SHUTDOWNCMD /sbin/shutdown -h +0 NOTIFYCMD /usr/local/ups/bin/notifyme POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 /lib64/nut/blazer_ser -D -a munja -i 10 Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.6.0) 0.00 send_to_all: SETINFO driver.parameter.port /dev/ttyS0 0.51 debug level is '5' 0.100836 send_to_all: SETINFO device.type ups 0.100860 send_to_all: SETINFO driver.version 2.6.0 0.100870 send_to_all: SETINFO driver.version.internal 1.51 0.100879 send_to_all: SETINFO driver.name blazer_ser 0.100886 Trying megatec protocol... 0.100970 send: Q1 0.326638 read: (246.0 140.0 246.0 004 50.0 54.0 25.0 1000 0.326681 send_to_all: SETINFO input.voltage 246.0 0.326695 send_to_all: SETINFO input.voltage.fault 140.0 0.326707 send_to_all: SETINFO output.voltage 246.0 0.326730 send_to_all: SETINFO ups.load 4 0.326741 send_to_all: SETINFO input.frequency 50.0 0.326752 send_to_all: SETINFO battery.voltage 54.00 0.326763 send_to_all: SETINFO ups.temperature 25.0 0.326772 send_to_all: SETINFO beeper.status disabled 0.326782 send_to_all: SETINFO ups.type offline / line interactive 0.326792 send_to_all: SETINFO ups.status OL 0.326799 Status read in 1 tries 0.326806 Supported UPS detected with megatec protocol 0.326877 send: F 0.446626 read: #230.0 0.0 048.0 50.0 0.446660 send_to_all: SETINFO input.voltage.nominal 230 0.446671 send_to_all: SETINFO input.current.nominal 0.0 0.446683 send_to_all: SETINFO battery.voltage.nominal 48.0 0.446694 send_to_all: SETINFO input.frequency.nominal 50 0.446701 Ratings read in 1 tries 0.446773 send: I 0.634630 read: # IN03064B 0.634659 send_to_all: SETINFO ups.mfr 0.634669 send_to_all: SETINFO ups.model 0.634679 send_to_all: SETINFO ups.firmware IN03064B 0.634686 Vendor information read in 1 tries 0.634693 Battery runtime will not be calculated (runtimecal not set) 0.634702 send_to_all: SETINFO ups.delay.start 180 0.634711 send_to_all: SETINFO ups.delay.shutdown 30 0.634719 send_to_all: ADDCMD beeper.toggle 0.634726 send_to_all: ADDCMD load.off 0.634733 send_to_all: ADDCMD load.on 0.634740 send_to_all: ADDCMD shutdown.return 0.634748 send_to_all: ADDCMD shutdown.stayoff 0.634755 send_to_all: ADDCMD shutdown.stop 0.634763 send_to_all: ADDCMD test.battery.start 0.634776 send_to_all: ADDCMD test.battery.start.deep 0.634785 send_to_all: ADDCMD test.battery.start.quick 0.634793 send_to_all: ADDCMD test.battery.stop 0.634864 send: Q1 0.862632 read: (246.0 140.0 246.0 004 50.0 54.0 25.0 1000 0.862677 send_to_all: DATAOK 0.862793 dstate_init: sock /var/lib/nut/blazer_ser-munja open on fd 5 0.862808 send_to_all: SETINFO driver.parameter.pollinterval 10 0.862818 send_to_all: SETINFO device.mfr 0.862827 send_to_all: SETINFO device.model 0.862900 send: Q1 1.090631 read: (246.0 140.0 246.0 003 50.0 54.0 25.0 1000 1.090670 send_to_all: SETINFO ups.load 3 10.871363 send: Q1 11.098641 read: (246.0 140.0 246.0 005 50.0 54.0 25.0 1000 11.098681 send_to_all: SETINFO ups.load 5 upsmon -D Network UPS Tools upsmon 2.6.0 0.00 UPS: munja@localhost (slave) (power value 1) 0.000153 Using power down flag file /etc/killpower 0.000261 debug level is '5' 0.001301 Trying to connect to UPS [munja@localhost] 0.002166 Logged into UPS munja@localhost 0.002184 pollups: munja@localhost 0.002197 get_var: munja@localhost / status 0.002279 Poll UPS [munja@localhost] failed - Driver not connected 0.002290 do_notify: ntype 0x0005 (COMMBAD) 0.002297 Communications with UPS munja@localhost lost 5.002588 pollups: munja@localhost 5.002617 get_var:
Re: [Nut-upsuser] Problem with blazer_ser/megatec when upgrading to 2.6.0 from 2.4
Citeren Dushan Tcholich dus...@gmail.com: [...] /lib64/nut/blazer_ser -D -a munja -i 10 Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.6.0) 0.00 send_to_all: SETINFO driver.parameter.port /dev/ttyS0 Looks fine. [...] upsmon -D Network UPS Tools upsmon 2.6.0 0.00 UPS: munja@localhost (slave) (power value 1) 0.000153 Using power down flag file /etc/killpower 0.000261 debug level is '5' 0.001301 Trying to connect to UPS [munja@localhost] 0.002166 Logged into UPS munja@localhost 0.002184 pollups: munja@localhost 0.002197 get_var: munja@localhost / status 0.002279 Poll UPS [munja@localhost] failed - Driver not connected 0.002290 do_notify: ntype 0x0005 (COMMBAD) 0.002297 Communications with UPS munja@localhost lost 5.002588 pollups: munja@localhost 5.002617 get_var: munja@localhost / status 5.002758 Poll UPS [munja@localhost] failed - Driver not connected 5.002771 do_notify: ntype 0x0008 (NOCOMM) 5.002781 UPS munja@localhost is unavailable 10.003015 pollups: munja@localhost 10.003048 get_var: munja@localhost / status 10.003191 Poll UPS [munja@localhost] failed - Driver not connected 15.003280 pollups: munja@localhost 15.003309 get_var: munja@localhost / status 15.003450 Poll UPS [munja@localhost] failed - Driver not connected What am I missing? What is the output of 'upsd' in the syslog telling you? Note that when running in debug mode, a process will terminate as soon as you close the terminal it is running in or when you kill it with Ctrl-C. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
