similar to: NUT in a Master / Slave Environment - How things work

I have the latest version of the Windows port of NUT installed on my Windows?7?machine. The UPS is connected via serial cable to the Windows machine. I also have my Synology NAS (which uses NUT) connected over the local network as a slave to the Windows NUT master. The Synology slave is configured to immediately go into "safe mode" whenever an FSD or OB+LB indication is received from the

Hello, I have a UPS unit attached to the "D-Link 320 ShareCenter", a SOHO 2-bay NAS. I set up the UPS in "Master Mode". Unfortunately it doesn't supply any kind of useful info in the web interface, so I had to connect via ?nc' to port 3493 to get the proper UPS name. I manage to to issue a successful ?upsc? command: root at galois:~# upsc megatec at 192.168.3.6

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto

Hello, I have a UPS unit attached to the "D-Link 320 ShareCenter", a SOHO 2-bay NAS. I set up the UPS in "Master Mode". Unfortunately it doesn't supply any kind of useful info in the web interface, so I had to connect via ?nc' to port 3493 to get the proper UPS name. I manage to to issue a successful ?upsc? command: root at galois:~# upsc megatec at 192.168.3.6

Roger, The topology is: UPS TOPAPC, Data link to master, Power supply to master, slave1 and slave2 UPS MIDAPC, Data link to master, Power supply to master, slave1 and slave2 UPS BOTAPC, Data link to master, Power supply to master, slave1 and slave2 Shutdown plan: When wall power fails for any of the three UPS units, they continue powering the master and the two slaves. When two of the UPS

On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > The posting at https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 references ups.delay.start and suggests setting it to -1. > > upsrw -l pve1 at localhost listed this as modifiable but any attempt at modifying the value failed. I used the override.ups.delay.start = -1 in nut.conf and this is now being

On Jan 9, 2014, at 4:00 PM, Lonnie Abelbeck wrote: > Hi, > > I'd like to better understand the merits of NUT clients (slaves) properly authenticating with the NUT server (master). > > NUT allows clients to retrieve UPS status (upsc ups at 10.10.10.1) without authenticating, shutdowns are properly trigger via polling. > > From testing one apparent benefit of

Hi Philip, I've updated NUT to 2.7.3 and finally found the root cause for the unexpected shutdown: It is recommended to increase pollinterval to 10 seconds in ups.conf for usbhid-ups driver due to a known issue: http://www.networkupstools.org/docs/man/usbhid-ups.html Default DEADTIME=15 in upsmon.conf was triggering shutdown. Increasing the value to 30 seconds resolved the issue. Now when

Here are the results from the output of upsc under different conditions from my Debian Test system with NUT 2.7.2 : Normal: ups.status: OL No wall power: ups.status: OB Runtime calibration (started from AP9630 web interface): ups.status: OB CAL So at this stage there is a difference! I then connected to my QNAP and set the UPS settings on the web interface to "Shutdown server if power

I have pfsense set as the NUT master and my Synology NAS as a slave client. I tried recreating a shutdown sequence by issuing a /usr/local/sbin/upsmon -c fsd command in pfsense (so as to preserve battery lifetime while testing all these) but the weird thing is that my Syno doesn't seem to get a hold of the FSD event. My pfsense master and UPS shuts down properly though. As soon as I issue the

Thanks Charles for the clarification. If NUT cannot control it then removing it would, IMO add value. On Sun, 10 Mar 2024 at 00:14, Charles Lepple < clepple_at_gmail.com_chribonn at duck.com> wrote: > On Mar 9, 2024, at 5:16?PM, chribonn at duck.com wrote: > > > > The posting at > https://github.com/networkupstools/nut/issues/432#issuecomment-405371395 > references

On Wed, 18 Oct 2017, Drew Plaster wrote: > MASTER SYSTEM > > nut.conf > MODE=netserver > > ups.conf > [TOPAPC] > driver = usbhid-ups > port = auto > pollonly > serial = "IS1309002707" > desc = "TOPAPC" > [MIDAPC] > driver = usbhid-ups > port = auto > pollonly > serial =

Hi Charles, Ok, will try the ignore lb flag later. How do I go about capturing the log? I might as well do it while testing the flag... Cheers, ST On 15 August 2017 at 20:42, Charles Lepple <clepple at gmail.com> wrote: > On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > > > Hi Charles, > > > > Have managed to make some progress

On 12/03/2016 11:46 AM, Charles Lepple wrote: > > If you don't mind sending the full output of "upsc" and "upsrw", we can update the DDL page (it only has "upsc" output for an older version of NUT). This UPS provides some sort of serial number (doesn't match the label) in the device.model (and mirrored at ups.model) variables, so if you want to mask off

On Aug 15, 2017, at 5:24 AM, Song Teck <songteck at gmail.com> wrote: > > Hi Charles, > > Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the

Hi thanks for all the help with this. I may have now resolved this and got things working... All I've ended up doing is making the slave the master and the master the slave! They now connect! What is strange though is that one machine is Ubuntu and one is Debian - with Debian as the Master things work no problem, without needing anything in hosts.allow at all. And Ubuntu is quite happy as

> On 9 Jun 2019, at 21:19, Roger Price <roger at rogerprice.org> wrote: > Using upssched and a upssched-cmd script to shut down the system is an alternative to using the builtin upsmon SHUTDOWNCMD on status [OB LB]. A upssched-cmd script can provide a managed shutdown well before [OB LB] is reached, but should the UPS reach that status upsmon's SHUTDOWNCMD will take over and

Hi Charles, Have managed to make some progress after a fashion. Got the unit to work on the jessie version of NUT (2.7.2). upsc does output the unit parameters, along with the mis-scaled voltage readings described at http://networkupstools.org/ddl/Mini-Box.com/OpenUPS2.html. Am now trying to get the shutdown sequence to work properly. Have been following this:

Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here:

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >