Thanks for suggetions and keep me indumb about making of Debian packages:D I will try this package "nut_2.2.0-2_i386.deb" One little questionm, shoud I use newmge-shut driver? - my ups is quite old - more then 3 years, connected through serial cable.>> PS: Arjen de Korte suspected something was wrong around my "heater" load, >> for now I have used two 150W lamps and it cause load 52% in case >> "ONBATTERY". When battery is charged over 95% the nut is working as >> suspected, but after first shutdown - switch up cycle the charge is about >> 86% and sequence does not work (usp shutdown early).> well, this is a know behavior of the old Pulsar Ellipse. When > restarting after a shutoff, the battery level is set to 85 %, even if > the actual level is nearby 0, which was dumb and dangerous.Special thanks to Arnaud for this, I suspected something like this (I have seen what is inside my ups - one rpocessor like thing connected through 4 pins to the power module, the small plate also includes a famous 555 analog timer, such a seriouse hardware can not do much). This is again a reason to shutdown the box(es) as quick as possible, keep it ups load switch off as long as possible. Thanks tovis PS: I necer have so good support for any sw at all - include my own:)
> Thanks for suggetions and keep me indumb about making of Debian packages:D > I will try this package "nut_2.2.0-2_i386.deb" > One little questionm, shoud I use newmge-shut driver? - my ups is quite > old - more then 3 years, connected through serial cable.Yes. The 'mge-shut' driver is scheduled to be replaced by that one. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57
newmge-shut ??? Shutdown, switch of ups does not work. Using command #upsmon -c fsd -u monmaster shutdown the boxes but the ups leave untached - I plugged back online manually. Using ups-cgi (old version found in etch) not reports ONBATTERY. No message to all connected users ONBATTERY No changes in battery charge level After reboot web status show "LOWBATTERY" as low as 26% (I doesnt check upsc)!!! I do not recognize "stale" situation - but I do not know that I should be happy or not. What to do now? A Rolling Stones frontembere sz?l?karrierj?nek legjobb dalai egy lemezre ?sszegy?jtve! T?ltsd le Te is! ________________________________________________________ http://zenearuhaz.t-online.hu/index.php?m=info&albumid=49346&sty=15 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20071025/4414c5dc/attachment.htm
I'm confused! I make some more settings in upsmon.conf - more NOTIFYFLAG and restart the hole nut! Through the cgi it is signaled the ONBATTERY and charge level also indicate well, when it reaches 30% shutdown procedure starts on boxes - hurra! But the UPS does not switch off at all:( OK I go back to mge-shut! Thanks Tovis A Rolling Stones frontembere sz?l?karrierj?nek legjobb dalai egy lemezre ?sszegy?jtve! T?ltsd le Te is! ________________________________________________________ http://zenearuhaz.t-online.hu/index.php?m=info&albumid=49346&sty=15 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20071025/df1a09e6/attachment.htm
Yes, I have almost forget! After reboot the charge of batteries (cgi) shows only 13%! Are you sure, it is a bug in tzhe driver? Thanks for patient tovis A Rolling Stones frontembere sz?l?karrierj?nek legjobb dalai egy lemezre ?sszegy?jtve! T?ltsd le Te is! ________________________________________________________ http://zenearuhaz.t-online.hu/index.php?m=info&albumid=49346&sty=15 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20071025/3a752b41/attachment.htm
I have wait for UPS - it goeas to the low battery, down to 17% - and retest. It is a same but in hurr? I forget some settings - especially to give the monmaster privilege to send "ALL" commands:) After an hour the charge was upto 70%, plug out my ups (with load of two 150W lamps), everything is goes well upto a moment, when driver signal staled and can not get back - boxes start shutdown. Again the UPS does not switch off:( I will try "old" mge-shut again, and come back with results. Hi tovis
On 10/25/07 16:01, tovis wrote:> I have wait for UPS - it goeas to the low battery, down to 17% - and retest. > It is a same but in hurr? I forget some settings - especially to give the > monmaster privilege to send "ALL" commands:) > After an hour the charge was upto 70%, plug out my ups (with load of two > 150W lamps), everything is goes well upto a moment, when driver signal > staled and can not get back - boxes start shutdown. Again the UPS does not > switch off:(Read the "shutdown.txt" file in the nut sources. There is an extra step you must take before the UPS will switch off the power to the PC (the load). It goes like this: You lose the line power; The UPS switches to battery; Once the UPS gets to the "low battery" point, it sends a command to the PC to shut down; Once the PC is "almost" shutdown, it sends a command to the UPS to switch off the power to the PC - this will result in the PC going the rest of the way off. Then, when the line power is restored to the UPS, the UPS restores power to the PC, and the PC reboots. Hope this helps,
>> I go back to mge-shut! >> ... >> Yes, I have almost forget! After reboot the charge of batteries (cgi) >> shows only 13%! >> Are you sure, it is a bug in tzhe driver?> I'm not sure to understand! > I don't recall the whole thread, but with a shutdown at 30% and a good > load, you reach such a restart level...I'm waiting for ups switch OFF the load, 1..2 minutes to be sure, with "virtual" load is on (2x150W). But nothing was happen, I need to plug the line manually (and unplug ther "load"). Mark E. Hansen wrote:> Once the PC is "almost" shutdown, it sends a command to the UPS to > switch off the power to the PC - this will result in the PC going > the rest of the way off.Really I do not know! Debian package of nut 2.0.4 version do it without any problem - more I suspected (some times on testings) that this SWITCH OFF (I prefer this word because shutdonw is more useful for the box) unsolicited and early. Unfortunately the MGE protocoll not only binary but to verbouse also. Additionally this part of the job is not logged by syslog, because the whole filesystem is readonly:( Usuallly I'm using for this kind of controll strongly ASCII coding, at least intel hexa (simple memory dump), but when so small amount of information in could be more readable, not only for "beauty" but debugging purposes. In this case you can use a simple terminal application such as minicom or on windows I have some free two channel serial communication observing applications, which allow to see everything as it happens! - here is not this situation, you need to write something for check the communication:( Also there is another problems, you need give some delay to fifnish the shutdown procedure before ups OFF the load,and you need some delay, after back the line power to have some charge in the batteries (at least to support for one more shutdown cycle) - this also does not work with new version. Summerize this "final touch" need more close check! - you right Mark. Thanks tovis
Its became more difficult! #upsdrvctl shutdown myups - does not work for me!? #upsrw -s ups.delay.shutdown=5 -u monmaster -p blah myups - working well, ups switch off after 5 sec of the command:) #upsdrv -s ups.delay.start=5 -u monmaster -?p blah myups - also working, but it is switch on after about 50 sec:) What to do now? May be change "upsdrvctl shutdown" to "upsrw -s ups ---" (it is sounds strange but it is working - at least for me)> The protocol your UPS uses is essentially USB-over-serial, so the above is > not an option.I fed up with USB, so many problems ... this was why the protocoll was so strange and familiar:( Thanks tovis V?S?ROLJON ONLINE! Ezzel a k?rty?val nem h?zz?k le! ________________________________________________________ http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.klikkbank.hu%2Flakossagi%2Ftermekek%2Fvirtualis_kartya%2Findex.html%3Flevelalja -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20071026/8224f1ad/attachment.htm
Hi! I have prepared the configuration, and succesfull(!) shutdown schedule, riched using old "mge-shut" driver. Unfortunatelly thi smessage became too big - about 60k - what to do? Thanks tovis
On 10/27/07, tovis <mailer.tovis at freemail.hu> wrote:> Hi! > I have prepared the configuration, and succesfull(!) shutdown schedule, > riched using old "mge-shut" driver. Unfortunatelly thi smessage became too > big - about 60k - what to do?Use gzip or bzip, or upload it somewhere and post a link. -- - Charles Lepple
This is repeat my message which was not allowed because of the length.> Its became more difficult! > #upsdrvctl shutdown myups - does not work for me!?I'm sorry, I does not realize, that this command also starting the driver, what mean if driver is already running that it would not work of course! I think the "old style" mge-shut work for me better, at least do nat stale in most important situation (on battery and low battery), this was the reason of the good result, and large charge level of my UPS - abut 100%. I make a shutdown test using "mge-shut" driver, 2x150W lamps and I have neer to excellent work. My configuration and excerpt from syslog also a track of UPS state (using a small bash script to compare state of the UPS and report the change in every 10 second) I have attach to this email. As you can observe in my UPS state track, after reboot it is reported that the charge of the batteries about 86% - what is of course inpossible. I think I need set "ondelay" in ups.conf to get more battery charge when line is back. Is this can help me? Thanks tovis PS: I have too many other troubles before repeat this - sorry. -------------- next part -------------- A non-text attachment was scrubbed... Name: nut-report-000.tar.bz2 Type: application/octet-stream Size: 8632 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20071028/2418de5d/attachment.obj
Hi folks! At last I have managed nut to work as I think need for me. Using notify facility and a small script I starting shutdown as UPS switch to battery. Finally I have decided install sudo - here I should make some more work to do - limiting as possible. Using "ondelay = 30" in ups.conf I have managed to wait more time after the line power is back - other question why this so unreliable:( I have measured time at 16 min upto 32 min (ondelay = 30 should give 30x10sec = 5 min) - but I do not care it is not so important for me. Also using some script to manage start of driver more reliable - I experienced two times that it is failed from about 40 times of restart. I decided this because ups with 2x150W lamps could work with inner limit 30% charge work only once, if charge was at least 95%!? Because of the communication problems it also could fail on first time . as I experienced it frequently happend at around when battery is near to his limit. After all I will wait for a new, production strong "newmge-shut" driver! Thanks tovis