similar to: Things seem to be working but upscmd does nothing

Here is the output root at nutpi:/etc/nut# ps -elf | grep -E '[n]ut|ups[dms]' 4 S avahi 246 1 0 80 0 - 1472 poll_s Jan26 ? 00:00:31 avahi-daemon: running [nutpi.local] 1 S nut 451 1 0 80 0 - 678 poll_s Jan26 ? 00:03:41 /lib/nut/upscode2 -a deltec-PRA1500 1 S nut 454 1 0 80 0 - 1173 poll_s Jan26 ? 00:00:28 /lib/nut/upsd 1

Here are my permissions and user info. Let me know if there is anything else I should check pi at nutpi:~ $ ls -alt /etc/nut total 56 drwxr-xr-x 87 root root 4096 Jan 26 15:22 .. drwxr-xr-x 2 root nut 4096 Jan 26 13:53 . -rw-r----- 1 root nut 4719 Jan 26 13:15 upssched.conf -rw-r----- 1 root nut 15347 Jan 26 11:25 upsmon.conf -rw-r----- 1 root nut 1543 Jan 26 10:02 nut.conf -rw-r-----

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

I only pasted a subset of my upsmon.conf. NOTIFYCMD is in my upsmon.conf AFA nutmon user. I was trying different things I had the directory as nutmon nut but changed it to nutmon nutmon to see if that worked. It didn't make a difference. Sorry about the digest this. I needed to hit a line in gmail web client to see the subject line. Know I know. Thanks for the heads up.. [root at donner

If you look closer at: > pi at nutpi:~ $ sudo ls -alt /home/nutmon > total 32 > -rw------- 1 nutmon nutmon 172 Jan 26 12:32 .bash_history > drwxrwx--- 2 nutmon nutmon 4096 Jan 26 12:32 upssched there is a d in the first position of the upssched permissions showing this is a directory. This is the directory location for PIPEFN and LOCKFN as defined in

One last update. I needed to log out and in to get the group add of my user nutmon to be recognized. My permissions are now root:nut on upssched.conf and it works. On Tue, Jan 28, 2020 at 7:00 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to > nut-upsuser at alioth-lists.debian.net > > To subscribe or unsubscribe

The time and upssched-cmd are now working. Here are the issues I had: 1) Did not define NOTIFYCMD in upsmon.conf Added NOTIFYCMD /sbin/upssched 2) Added +EXEC to NOTIFYMSG rules I am using 3) Change ownership of upssched.conf to my nut user nutmom. I had added nutmon to the group nut but it didn't work. Thanks again for all your guidance On Tue, Jan 28, 2020 at 7:00 AM

Hi. I have an improvement suggestion. Say that a careless user starts editing upsmon.conf before having read the complete documentation (not that I know of any such users of course) and starts by adding "RUN_AS_USER = nutmon" and then creates this user. Later he discovers that the rpm package already has created a "nut" user and therefore deletes the nutmon user but forgets to

Hello all, I'm having problems with what I'm told should be a straightforward issue. The message in /var/log/daemon is: <quote> Feb 13 10:37:57 lupin upsmon[31324]: Master privileges unavailable on UPS [lupin1500AVR@localhost]

Hi. I'm having trouble mapping network drives from a Samba server when I login to my machine using the Cygwin SSH daemon and am hoping it may be something people here have seen before. I am able to map Samba shares with no problem from the Windows Explorer, or a Cygwin bash shell started from my desktop, but when I login remotely via ssh and try and mount something with "NET

I have a Raspberry PI that I have connected to a Deltec UPS via serial (upscode2 driver). I had an older version of Rasbian running. The nut configuration worked fine but I had mail issues I couldn't resolve when gmail changed how it handled MTAs. Plus it was running an old version of Deb that is no longer supported. It was broken enough I could not upgrade to a never version so I started from

This will sound a bit odd. I have a current server running with a UPS. I'm in the process of replacing that server with another and obviously want Nut to monitor the new server. The new/old servers are in different locations, so I don't have access to the UPS while configuring the replacement server. I think I have the config ok, but what errors would you expect to see? Typically I'm

Ok rebooted All running ok now. Great thanks a lot! In system.log Jun 15 21:38:54 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon): Unknown key for Boolean: SuccessfulExit Jun 15 21:38:54 c01 com.apple.xpc.launchd[1] (org.networkupstools.upsmon): This service is defined to be constantly running and is inherently inefficient. What is the purpose of Boolean: SuccessfulExit?

[As posted as Ubuntu Question #184284 on Launchpad] Hi, I try to set up nut (2.4.3) on my Lucid (10.04.3 LTS) to make use of my old but very trusty UPS (Best Power Fortress 660 LI). Yes, this UPS is old (about 16 years), but with its third battery pack last week it is as good as new. It runs perfectly well with Windows XP, Vista and even Windows 7. But not so with Ubuntu and nut. After

Dear Steve, Thanks. Until today I could not install the nut in my raspberry. All installation good, but with my ups " Ovislink Chrome 1000VA" and "nutdrv_atcl_usb" driver, it inform me the following error details. I can startup nut but nutmon don't receive anything only (lost conection). My setup: root at pi1:/nut# lsusb Bus 001 Device 002: ID 0424:9512 Standard

I've been wanting to build the trunk since Arjen added the powerpanel driver... been having a little trouble... after running these commands: /usr/local/libexec/automake19/aclocal -I m4 /usr/local/libexec/autoconf259/autoheader /usr/local/libexec/automake19/automake -ac /usr/local/libexec/autoconf259/autoconf ./configure --with-cgi --with-user=nutmon

Hello all, Some time ago, you all were very helpful in getting nut running on an OpenBSD system, using--for what it's worth--a CyberPower 1500AVR. So I finally got my FreeBSD system's UPS, also a CyberPower 1500AVR, within reach of its serial cable and I'm trying to get nut running here. I'm going nuts. Basically, I copied the OpenBSD configuration over to the FreeBSD system

---> On 15/03/2009 8:00 AM, nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 1 > Date: Sat, 14 Mar 2009 21:47:08 +0100 > From: Arjen de Korte <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Weird Load and Battery Temp Readings > To: nut-upsuser at lists.alioth.debian.org > Message-ID: <20090314214708.37122w00w79l6u9s at mail.de-korte.org>

Good morning all. I am on a different system with a different UPS, and I am fighting a similar problem to the one I posted about yesterday, and again making little headway. This system is running Debian Wheezy and connected to an APC BackUPS ES550. Starting things manually seems to go well, but my startup script fails, and nothing is logged anywhere. This may not be a NUT question per se, but I

I got a bunch of configfiles that look like this: mgmt-dev:/etc/nut# grep -v 'niets' * ups.conf:[ups] ups.conf:driver=newhidups ups.conf:port=auto upsd.conf:ACL all 0.0.0.0/0 upsd.conf:ACL localhost 127.0.0.1/32 upsd.conf:ACL remote 192.168.110.0/24 upsd.conf:ACCEPT remote upsd.conf:ACCEPT localhost upsd.conf:REJECT all upsd.users:[monuser] upsd.users:password = mypass upsd.users:allowfrom