Re: [Nut-upsuser] Problem with blazer_ser/megatec when upgrading to 2.6.0 from 2.4
2011/4/29 Dushan Tcholich > > > > 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 R&D - 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
Re: [Nut-upsuser] Richcomm Serial driver
Thanks for your instruction. I tried the portman under XP. The log file is attached with the mail. Please check that out and let me know what you think or any further instruction. Thanks for your time. Take care, Manzoor Portmon.log Description: Binary data ___ 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
> > 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
