similar to: Can Not Get UPS to Turn Off After System Shutdown

Denny: Thank you. Problem solved. I switched SHUTDOWNCMD back to the default and added nut.powerfail to the shutdown runlevel. Now the UPS turns off after the system shutdown, if the shutdown is caused by lack of power going to the UPS. I checked and found the file sys-power:nut-2.7.4-r1:2018...log in /var/log/portage/elog/*. It did contain the message you pointed out. I should have checked

This really isn’t what you want. You should use a normal shutdown command on Gentoo: SHUTDOWNCMD "/sbin/shutdown -h +0” When you emerged the NUT package, you should have seen this message: * Please note that NUT now runs under the 'nut' user. * NUT is in the uucp group for access to RS-232 UPS. * However if you use a USB UPS you may need to look at the udev or * hotplug

Glad you got it working. Denny > On Jul 28, 2018, at 19:02, richjunk at pacbell.net wrote: > > Denny: > > Thank you. Problem solved. > > I switched SHUTDOWNCMD back to the default and added nut.powerfail to > the shutdown runlevel. Now the UPS turns off after the system shutdown, > if the shutdown is caused by lack of power going to the UPS. > > I checked

Hi, Here's the message when I try to stop upsdrv daemon (/etc/init.d/upsdrv stop) * Stopping UPS drivers ... Network UPS Tools - UPS driver controller 2.4.3 Can't open /var/lib/nut/usbhid-ups-auto.pid: No such file or directory Here's the message when I try to start upsdrv daemon (/etc/init.d/upsdrv start) * WARNING: upsdrv has already been started. And finally here's

This issue has been occurring for years on my setup. OS: Gentoo most recent kernel: 4.1.12 UPS: Eaton Powerware 9130 rackmount 2000kVA, connected via USB The upsdrv service dies and must be restarted several times a day. Zero output to dmesg or any other log other than failed reattempts reporting no such file or directory errors. "/lib64/nut/usbhid-ups -DDD -q -a powerware" exited 1

Hi, I'm trying to setup my Mustek 600 with USB (no serial ports on my computer) on Gentoo. The configuration I use is: [Mustek] driver = megatec_usb port = auto desc = "Power Mustek 600 USB" The NUT I use on my x86_64 machine is: sys-power/nut-2.4.3-r2 USE="bash-completion ssl usb xml -cgi -hal -snmp" When I start upsdrv I get: weasel ~ # /etc/init.d/upsdrv start

Nut will monitor the ups and shutdown Linux when the ups goes to low battery as it should. But the UPS is not shut down so the system will restart when the power is restored. If I switch the UPS off , restore power and switch the UPS on the system will restart. I have not been able to get nut to switch the UPS off after it brings the system down. I can get the UPS to switch off with upscmd

On 2/5/2014 8:24 AM, Charles Lepple wrote: > On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > >> NUT will complain endlessly about communication errors and never establish SNMP communication with my APC UPS > Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

Hi, I have a small home-use UPS for my home server from powerwalker (http://powerwalker.com/de/index.php?option=com_content&task=blogcategory&id=63&Itemid=106 sorry I only found a german version). It has a USB and a serial connector. lsusb lists it as "06da:0003 Phoenixtec Power Co., Ltd", in /proc/bus/usb/devices it sais "Manufacturer=OMRON" and

I decided to upgrade from openSuse 10.2 to openSuse 10.3. I installed xen things, but when I boot using xen option the system is blocked. It appears the green window, with little suse logo in the middle, and mouse cursor, but the system crashes. My computer is a Pentium 4 1,5 GHz, 512 MB of RAM. I attached "diff boot.msg boot.omsg" (as diff opensuse-normal-kernel opensuse-xen-kernel)

Hi Charles, thank you for your answer. This was indeed the core of the problem. I have amended the configuration files. It means now the communication works as required. Alas I now have another problem. Just for the record here is the configuration after the changes. The configuration is as follows. #nut.conf MODE=standalone #ups.conf [eaton] driver = usbhid-ups port = auto

Hi Roger, Hi all,   > Does upsmon.conf specify a shutdown on LB? I think so. You mean SHUTDOWNCMD? The relevant parts of my upsmon.conf (notifications removed): MONITOR ups at localhost 1 upsmaster secret master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 2 HOSTSYNC 15 DEADTIME 40 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 1800

> I see upsd and the first upsmon are running as "root". They are often run as user "nut" or "upsd?. Apparently Synology has implemented it standard like this. Upsmon.conf on the Synology NAS: RUN_AS_USER root I suppose this needs to be changed from a security point of view. > I don't know the Synology NAS, but I guess that unless it is shutdown

I've been able to get the latest Windows port installed on my Hyper-V 2012 R2 instance and start the service. But as I'm an absolute beginner I'm not sure how to proceed further. I've browsed the archives, but discussions here tend to assume at least an intermediate level of understanding; thus it's still quite a bit over my head. Your patience and slow explanations are

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200217/b486de30/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid.zip Type: application/zip Size: 4031 bytes Desc: not available URL:

Yes, that was the power off test. However the upssched-cmd script gave absolutely no signs of activity. Even it's logger lines don't show up in journalctl. No any permission error messages - nothing. Only the 2 messages from upsmon - on battery and then on line power. Here is the nut-report: http://www.filehosting.org/file/details/518300/NUT.report --- George Anchev On Tue, Oct 27,

On Jun 20, 2013, at 10:35 AM, Louis Chaillet wrote: > With respect clarification of the documentation (and reference to your question Charles). The documentation does suggest that you can shutdown the ups by the upsdrvclt shutdown [ups] command. Specifically in "http://www.networkupstools.org/docs/man/upsdrvctl.html" in the section commands under warning. In the "Network UPS

Hello happy nuters, Some complementary words about making nut 2.02 successfully run on FreeBSD with MGE Ellipse. With the usefull information Arnaud sent, it's rather obvious that the erratic response of the ups to the shutdown script is linked to its difficulty to handle large traffic on the serial line. These are the final tweak I made to have this configuration satisfyingly

Well it is the season for storms and power outages here in the US PNW. I noticed that today when the power went out, NUT mostly did what I hoped/wanted. But it did not actually turn off the UPS at all. The UPS kept beeping and I had to turn it off manually. I thought that NUT would handle this. But perhaps it cannot for my unit? Or perhaps I have things improperly configured? Any suggestions?