Hhm. OK, but it doesn't work. The ups goes offline and starts back immediately. Even if ups.delay.start is set 0. I will try another test circuit after using the upsrw command. -----Ursprüngliche Nachricht----- Von: Nut-upsuser Im Auftrag von Roger Price Gesendet: Sonntag, 27. Oktober 2019 11:11 An: Nut-upsuser at alioth-lists.debian.net Betreff: Re: [Nut-upsuser] Problems with NUT on Raspberry Pi On Sun, 27 Oct 2019, EP wrote:> it was set by ups.conf. Should I use the upsr-command?Setting the value in ups.conf is correct, since that is the value which will be used the next time upsd starts. Roger _______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
On Sun, 27 Oct 2019, EP wrote:> I can't imagine that's the way cyberpower wants their unit to work. With this > behavior the unit does exactly the opposite of what it is built for. It > doesn't protect your equipment. It will destroy it because the server which > was just shutted down cleanly will boot again on a battery-powererd ups. What > a crap. > > But I am not finished at all because I can't believe there is no solution for > this problem.Perhaps it's time to borrow a Windows PC and try the software that comes with the UPS. Roger
Same behavior here. I tested it by executing the usrw-command (bash) as well. UPS turns off and on again. It even seems to ignore the ups.delay.shutdown (was set to 120 seconds but shutted down faster). Afterwards I set the ups.delay.start to -1. That makes the ups staying off. But - and that is the big mistake - it doesn't turn on when power returns with this setting. I can't imagine that's the way cyberpower wants their unit to work. With this behavior the unit does exactly the opposite of what it is built for. It doesn't protect your equipment. It will destroy it because the server which was just shutted down cleanly will boot again on a battery-powererd ups. What a crap. But I am not finished at all because I can't believe there is no solution for this problem. -----Ursprüngliche Nachricht----- Von: Nut-upsuser Im Auftrag von EP Gesendet: Sonntag, 27. Oktober 2019 11:14 An: Nut-upsuser at alioth-lists.debian.net Betreff: Re: [Nut-upsuser] Problems with NUT on Raspberry Pi Hhm. OK, but it doesn't work. The ups goes offline and starts back immediately. Even if ups.delay.start is set 0. I will try another test circuit after using the upsrw command.> it was set by ups.conf. Should I use the upsr-command?Setting the value in ups.conf is correct, since that is the value which will be used the next time upsd starts. Roger _______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser _______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser