similar to: NUT 2.7.2.3 on CentOS 7.2 doesn't cut power to the host after shutdown

Hello, I'm configuring the NUT package which comes with CentOS 7.X: nut.x86_64 2.7.2-3.el7 @epel nut-client.x86_64 2.7.2-3.el7 @epel I've configured NUT based on the instructions found on this page: https://www.luzem.com/2015/01/25/install-ups-in-centos-7/ which worked, except for one

1. Does variable FSB block sizing extend to files larger than record size, concerning the last FSB allocated? In other words, for files larger than 128KB, that utilize more than one full recordsize FSB, will the LAST FSB allocated be ''right-sized'' to fit the remaining data, or will ZFS allocate a full recordsize FSB for the last ''chunk'' of the file? (This is

My environment is a little different, but I'm seeing at least the client working without issue on CentOS 7. On CentOS 7.2 I also used the epel repository and installed nut-client; currently nut-client-2.7.2-3.el7.x86_64 The only configuration change was to update the /etc/ups/upsmon.conf file with the appropriate MONITOR statement. Other than that, normal enabling and starting the service

On Fri, 11 Sep 2020, Bartosz wrote: > Could you please recommend me a UPS with 100% support of the ondelay parameter > and NUT compatibility? 850 or 1000 VA I have the EATON 5E850iUSBDIN UPS and it > does not support this parameter so I would like to buy another UPS that for > sure will support it. I have an Eaton Ellipse Eco 1600 bought in 2016 which has a delayed start feature.

On 12/25/2016 9:25 AM, Larry Fahnoe wrote: > My environment is a little different, but I'm seeing at least the client > working without issue on CentOS 7. > > On CentOS 7.2 I also used the epel repository and installed nut-client; > currently nut-client-2.7.2-3.el7.x86_64 The only configuration change was > to update the /etc/ups/upsmon.conf file with the appropriate

I'm looking at deploying a new set of servers based around Intel P4 800MHZ FSB processors. Currently I'm looking at the following 2 motherboards and I'm wondering how well supported they are under -STABLE (specificaly the ATA and LAN as well as text mode video) Model Chipset ASUS P4P8X Intel 865P ASUS P4P800 Intel 865PE Also I'm looking for recommendations on Dual Xeon

Hi all, I have a following problem: - Remus network buffering doesn''t work. It seems to be because of no vif is reported by the function server.xend.domain on line 29 of /usr/local/lib/python2.7/dist-packages/xen/remus/vm.py (seen using pdb) : 27 if domid: 28 try: 29 self.dominfo = server.xend.domain(domid, ''all'') >

On Fri, Sep 11, 2020, at 4:05 PM, Bartosz wrote: > Dear All, > > Could you please recommend me a UPS with 100% support of the ondelay parameter and NUT compatibility? > > 850 or 1000 VA > > I have the EATON 5E850iUSBDIN UPS and it does not support this parameter so I would like to buy another UPS that for sure will support it. > > Thank you, > Bart Can you tell

This is more an Outlook issue than Dovecot, but given that it is connected to Dovecot I figured there would be a good pool of knowledge here that increases the likelihood that somebody knows the answer :) I have a Dovecot server setup with a public folder and keep getting complaints that Outlook users don't see new folders created by other people. In Thunderbird it is simply a case of

On 12/25/2013 12:16 AM, Kris Jordan wrote: > Angel Tsankov wrote, On 12/24/2013 1:22 AM: [...] >> I can see that my UPS (MGE Protection Center 675) has a parameter >> ups.timer.start (currently holding the strange value of -10). Any idea >> if this could help and how this parameter can be changed? > > in upsrw? In upsc only. Here's the complete output:

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Just spended ~ hour googling - all boards are based on GC-XX or I750X Chipsets - all for Xeons. There also some boards for Pentium 3. Can someone point me to a board with 64Bit 3.3v PCI for ordinary P4 with 800Mhz FSB. Thanks

Hello, I am having difficulty using NUT to shut down my Netgate SG-1100 (a pfSense router) when the power level of the UPS gets critically low. Here is some relevant information: - OS: pfSense 2.4.5-RELEASE-p1 (FreeBSD 11.3-STABLE) - NUT version: 2.7.4 - Installed from: pfSense package 2.7.4_7 - UPS: AVR750U (Device release number 2) - I have included my config files, output from `upsc`, and

Hi all, First of all thanks for the great work on nut ! (despite it's not fully functional yet overhere). Everything seemed to go fine until the final test : shutdown the UPS ! The system is running FreeBSD 5.3, the UPS is MGE Ellipse 800 USBS both linked with the MGE serial cable. The system is a remote server, only running some file services and large disks. The porting,

> On Dec 24, 2016, at 3:14 AM, Roger Price <roger at rogerprice.org> wrote: > > On Sat, 24 Dec 2016, Spike wrote: > >> ... from reading the docs it seems the UPS should power off, is that the case? > > Yes, The UPS should be sent a "delayed shutdown" command, upsdrvctl shutdown, to tell it to shut down _after_ the box. The amount of the delay can be set

Hello, my Atlantis UPS (model on "subject" line) fails to cycle off the outlet power after a power failure on the mains followed by an automatic shutdown of the computer. The UPS simply remains always on, preventing the computer from restarting. ** Setup: ** Nut version 2.7.2 Nut driver blazer_usb Linux 4.1.1 The config files are pretty default; the peculiar customization is

On Dec 20, 2017, at 10:32 AM, Ken Olum wrote: > > 0.090564 find_nut_info: unknown info type: load.on.delay > 0.090577 find_nut_info: unknown info type: load.on.delay > 0.090585 Initiating UPS shutdown > 0.090593 upsdrv_shutdown... > 0.090601 instcmd(shutdown.return, [NULL]) > 0.090614 find_nut_info: unknown info type: shutdown.return > 0.090624

Hi, I have a CyberPower UPS connected to a Ubuntu karmic machine. All functions are working well. I can use upsc to see all the UPS parameters, power loss and battery low events are correctly detected, and shutdown is correctly initiated. If I run upsdrvctl shutdown, the UPS cuts power immediately. However, if I simulate a shutdown with upsmon -c fsd, the UPS fails to cut power. The

When running 'sudo upsmon -c fsd' UPS turns off then back on after a delay as expected. But when power is disconnected and the command is ran, the UPS turns off but still turns back on again. Changing 'ondelay' to -1 or 0 does not change the behavior. How can I get the UPS load to stay turned off if there is no power? Or am I misunderstanding how to test this functionality?