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 nut may have neglected this. Try creating the > /var/run/nut directory, make it writable but nut. If that lets you > start nut-server properly, then it is made permanent by adding a file > to /etc/tmpfiles.d > Then create a bug report for the nut package.This is debian stretch. The directory exists. root at coyote:amanda-master$ ls -l /var/run/nut total 8 -rw-r--r-- 1 nut nut 6 May 7 10:40 upsd.pid -rw-r--r-- 1 root root 6 May 7 10:43 upsmon.pid The real problem as I recall from a couple days back, is that the usbhid-ups driver was left out of this kernel build. Since this is pretty close to an rt kernel, I don't know if the LCNC folks will build another kernel with it, and issue the update. I have made them aware of it however. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
On May 8, 2019, at 8:19 PM, Gene Heskett wrote:> > The real problem as I recall from a couple days back, is that the > usbhid-ups driver was left out of this kernel build. Since this is > pretty close to an rt kernel, I don't know if the LCNC folks will build > another kernel with it, and issue the update.Since you mentioned this in the other thread, I just want to clarify again that "usbhid-ups" is *not* a kernel driver. There is a possibility that the LCNC folks have changed their kernel configuration, but they won't see any mention of the NUT user-space programs like usbhid-ups in the config files. What does "systemctl status nut-driver" return?
On Sunday 12 May 2019 12:07:13 pm Charles Lepple wrote:> systemctl status nut-driver● nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2019-05-10 02:35:09 EDT; 2 days ago Ok, I'll byte, the only usnhid-ups on the system is on the old wheezy drive, and its a 32 bit so won't run on a 64 bit install. ?? Thanks Charles Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>