similar to: still no nut at reboot

Greetings; Nut pull & build from about two weeks ago, 2.4.3 I believe. Belkin UPS. I have everything working but a proper shutdown of upsd when I reboot, it hangs there and needs the hdwe reset button to reset it. That may be related to my finding more than 1 K##upsd and more than one K##upsmon, in /etc/rc5.d and which I have now nuked. However, while its working well enough to monitor,

On Tuesday 07 May 2019 09:49:47 am Charles Lepple wrote: > On May 7, 2019, at 9:09 AM, Gene Heskett wrote: > > On Tuesday 07 May 2019 08:38:44 am Charles Lepple wrote: > >> On May 7, 2019, at 5:06 AM, Gene Heskett wrote: > >>> New testing install(stretch) > >>> pulled in nut stuff from repo. > >>> copied old wheezy configs to /etc/nut,

Greetings people; The section of drakeconf that pclos uses has two problems. First is several screens full of complaints about deprecated syntax in "/etc/udev/rules.d/70-nut-usbups.rules" at each reboot. So I pulled the current 2.5 svn trunk, then found I was missing quite a few build tools needed here that aren't used when building a kernel, currently running a 32 bit

On Sunday 19 October 2014 22:03:23 Charles Lepple did opine And Gene did reply: > Hi Gene, > > On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > Greetings; > > > > I found pdf user manual which explains a few things that might help. > > > > However, for a ubuntu flavor, the various .conf etc files seem to be > > in

Hi Gene, On Oct 18, 2014, at 7:35 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Greetings; > > I found pdf user manual which explains a few things that might help. > > However, for a ubuntu flavor, the various .conf etc files seem to be in > /etc/nut. We have an open ticket about that[*]; basically, the official NUT documentation needs to be a bit more explicit

Greetings; I found pdf user manual which explains a few things that might help. However, for a ubuntu flavor, the various .conf etc files seem to be in /etc/nut. But this pdf says they are in /usr/local/ups/etc, and yes indeed there are some there, with the .sample files being owned by root, and the rest are user 503, whoever he may be. Are these just a sample storage in case one needs to

Hi Charles; Had a fire on the mobo of my old server, replaced it all with about 10x the hardware. dmesg now says this: 71068.842780] usb 1-9: new full-speed USB device number 10 using xhci_hcd [71069.012577] usb 1-9: New USB device found, idVendor=051d, idProduct=0003 [71069.012579] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [71069.012579] usb 1-9: Product:

Greetings Charles; I eventually gave up making it work on ubuntu-10.04.4 LTS, and that drive is slowly curling up its toes, so I am running wheezy on a fresher drive now. I have installed all the nut stuffs from the repo, and now have two more scripts in /etc/init.d called nut-client and nut-server. dmesg |grep Belkin - : root at coyote:/etc/nut# dmesg|grep Belkin [ 4.242066] usb 2-3:

On Sun, Mar 1, 2015 at 2:23 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hi Charles; I hope this finds you well. Hi Gene, > Here is dmesg output: > gene at coyote:~$ dmesg |grep Belkin > [ 3.315667] usb 2-3: Product: Belkin UPS > [ 3.315669] usb 2-3: Manufacturer: Belkin > [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device

Hi Charles; I hope this finds you well. Here is dmesg output: gene at coyote:~$ dmesg |grep Belkin [ 3.315667] usb 2-3: Product: Belkin UPS [ 3.315669] usb 2-3: Manufacturer: Belkin [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device [Belkin Belkin UPS] on usb-0000:00:02.0-3/input I have configured it to use this generic-usb, and probably made it less

On Wednesday 08 May 2019 05:39:22 pm Stuart D. Gathman wrote: > On Tue, 7 May 2019, Gene Heskett wrote: > > May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No > > such file or directory > > Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs > filesystem. Thus, any subdirectories must be created afresh each > boot. The packager for

On Monday 03 April 2017 16:39:30 Stuart D. Gathman wrote: > On Mon, 3 Apr 2017, Gene Heskett wrote: > >>> Nut, IIRC, can do a periodic battery test by putting it offline, > >>> using the battery, for a predetermined length of time, weekly, > >>> monthly etc, > >> > >> We definitely don't want that in this instance either! > > >

[I had a look through the mail archives before sending this, but I didn't find anyone else having this issue.] Has anyone seen this before? I'm almost 100% certain I tested this nut correctly detected OB LB in the past, but when I happened to look at it today, I see it refusing to work -- apparently because the NUT client knows how to ask for RFC1628 OIDs, but not what to do with the

Hi Charles; I think its not working yet even though I seem to be getting only one error, but I cannot seem to get upsmon to output the current ups status. So, since I cannot find any manpages (is that a separate package, if so I did not see it in the repo.) about the only error I can get out of it is that it is not listening on localhost:3493. Yet that is specified in the conf files: ene

Dir list! I'm using nut for many years on my home "server" without problems running on Debian 6.x nut version 2.4.3 Now I have decided to move to Debian 10. I have started from zero and install new system on a different disk. I have successfully installed new nut version 2.7.4 I've found one issue, that new version see always "low battery" state. Excerpt from syslog:

On Sep 5, 2020, at 5:23 AM, Roger Price wrote: > > On Sat, 5 Sep 2020, Gene Heskett wrote: > >> But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? > > Hello Gene, By "auto start" I assume you mean the automatic power on of a box when wall power returns after a power failure. For this to work,

I am trying to get a TrippLite SU1500RTXL2Ua working with nut on Mandriva 2007.1, is there a particular version of nut needed to get this to work? At first I tried nut 2.0.5 (which came with 2007.1) but it wouldn't work, and then research showed it was an older version of nut. So nut-2.2.1-2 src rpm was pulled from Mandriva 2008.1, the binary rpm built, and nut and nut-server installed from

O.S. Ubuntu 10.10, Maverick Meerkat 32 bit. NUT 2.4.3-1ubuntu5, package installed Belkin F6C1500-TW-RK I am having trouble starting uspd whenever I add a client from my lan to uspd.conf: LISTEN 127.0.0.1 3493 LISTEN 192.168.36.106 3493 naknight at nak-server:~$ sudo upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added 127.0.0.1:3493 0.000093 listen_add:

On Tue, 7 May 2019, Gene Heskett wrote: > May 07 10:40:21 coyote upsd[12110]: fopen /var/run/nut/upsd.pid: No such > file or directory Some time ago, Fedora made /var/run a symlink to /run which is a tmpfs filesystem. Thus, any subdirectories must be created afresh each boot. The packager for nut may have neglected this. Try creating the /var/run/nut directory, make it writable but nut.

On 12/03/2016 10:08 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 11:01 AM, Jack McGee <jack at greendesk.net> wrote: >> >> I did restart those services, no change. >> > $ ps auxww|grep [/]nut > root 13074 0.0 0.0 37844 2628 ? Ss 08:42 0:00 /lib/nut/upsmon > nut 13076 0.0 0.0 45632 5148 ? S 08:42 0:00 /lib/nut/upsmon