[Nut-upsuser] nut vs ups fail

Sam Varshavchik mrsam at courier-mta.com
Thu May 9 02:03:17 BST 2019


Stuart D. Gathman writes:

> 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.

It's worth noting that Fedora's package installs the following in  
/usr/lib/tmpfiles.d/nut-client.conf:

D    /var/run/nut 0770 root nut -

And Fedora's /usr/lib/systemd/system/nut-driver.service has the following  
entry in [Service]:

ExecStartPre=-/usr/bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/nut-client.conf





More information about the Nut-upsuser mailing list