Re: [Nut-upsuser] How do I configure NUT?
On Thu, 3 Aug 2017, Roger Price wrote: On Thu, 3 Aug 2017, Tomas Larsson wrote: Hi there. I need some advise on how to configure NUT, if it is possible to do it. My UPS, a Compaq R3000 I thought the Compaq R3000 Line was a Series of laptops designed and built by Hewlett-Packard Corporation, not a UPS? My mistake, "R3000" can also refer to the HP UPS R3000, a 2U rackmount design offering up to 2700 watts. See http://h18000.www1.hp.com/products/quickspecs/archives_Canada/10671_ca_v20/10671_ca.PDF http://www.hp-r3000.etrk.info/HP-R3000-XR-NA-MANUAL.pdf Roger ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] How do I configure NUT?
On Thu, 3 Aug 2017, Tomas Larsson wrote: Hi there. I need some advise on how to configure NUT, if it is possible to do it. My UPS, a Compaq R3000 I thought the Compaq R3000 Line was a Series of laptops designed and built by Hewlett-Packard Corporation, not a UPS? has three individual power segments. I want NUT to: When mains is interrupted. Shut down all serves immediately. I'm not sure of your topology, but it looks as if it would be easier to separate the problem into pieces. 1. The servers. Make one of the servers the master, and all the others slaves. This then becomes a well known NUT setup for master + slaves, in which the master begins the shutdown operation as soon as status [OB] is seen. All the servers need to have upsd and upsmon running. The server master does not shut down the UPS. When all servers are completely down, in sequence with time delay shut down two of the power segments. 2. Later, based on a upssched timer, some other system "S" running upsd and upsmon shuts down the power segments. When batteries is about to be depleted shut down itself and the last power segment. 3. When system "S" detects the [OB LB] status it shuts down itself and calls for a delayed shutdown of the UPS. When power returns, start up the power segments in sequence. This supposes that the power outlets of the UPS have been disconnected, and are reconnected when wall power returns. Roger ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] Återkalla meddelande: How do I configure NUT?
Tomas Larsson skulle vilja återkalla meddelandet, How do I configure NUT?. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] How do I configure NUT?
Hi there. I need some advise on how to configure NUT, if it is possible to do it. My UPS, a Compaq R3000 has three individual power segments. I want NUT to: When mains is interrupted. Shut down all serves immediately. When all servers are completely down, in sequence with time delay shut down two of the power segments. When batteries is about to be depleted shut down itself and the last power segment. When power returns, start up the power segments in sequence. With best regards Tomas Larsson <>___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2
On Aug 3, 2017, at 5:35 AM, Song Teckwrote: > > That package is supposed to install both server and client (according to the > description at https://packages.debian.org/stretch/nut anyway). I'll try both > server and client individually later and see if that helps. > Right, but only if you install it via apt. If you install the 2.7.4 .deb with dpkg, and you have the 2.6.4 nut-client and nut-server .debs installed, the dependencies are satisfied. (The nut metapackage does not depend on specific versions.) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT not recognising Mini-box OpenUPS 2
Hi Charles, That package is supposed to install both server and client (according to the description at https://packages.debian.org/stretch/nut anyway). I'll try both server and client individually later and see if that helps. Cheers, ST On 3 Aug 2017 7:26 a.m., "Charles Lepple"wrote: > On Aug 2, 2017, at 12:09 PM, Song Teck wrote: > > > > sudo dpkg -i nut_2.7.4-5_all.deb > > (Reading database ... 103447 files and directories currently installed.) > > Preparing to replace nut 2.6.4-2.3+deb7u1 (using nut_2.7.4-5_all.deb) ... > > Unpacking replacement nut ... > > Setting up nut (2.7.4-5) ... > > > > which doesn't return an error but starting upsdrvctl after still shows > v2.6.4 so that didn't work. > > > The "nut" package only depends on "nut-client" and "nut-server", so you > would need .debs for those as well. Those are the ones that I think would > be likely to have issues. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser