Bug 1349362 - Can't chdir to /var/run/nut: No such file or directory
Summary: Can't chdir to /var/run/nut: No such file or directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nut
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Hlavinka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-23 10:26 UTC by Harald Reindl
Modified: 2016-11-01 16:22 UTC (History)
1 user (show)

Fixed In Version: nut-2.7.4-3.fc23 nut-2.7.4-4.fc25 nut-2.7.4-3.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-23 16:25:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Harald Reindl 2016-06-23 10:26:07 UTC Comment hidden (abuse)
Comment 1 Michal Hlavinka 2016-06-23 12:22:48 UTC
(In reply to Harald Reindl from comment #0)
> Jun 23 12:07:06 srv-rhsoft upsdrvctl: Can't chdir to /var/run/nut: No such
> file or directory
> 
> [root@srv-rhsoft:~]$ cat /etc/tmpfiles.d/nut-client.conf
> D    /var/run/nut 0750 nut nut -
> 
> you are aware that this only works after a reboot 

wrong, service file takes care of that:
[Service]
ExecStartPre=-/usr/bin/systemd-tmpfiles --create /etc/tmpfiles.d/nut-run.conf
ExecStart=/usr/sbin/upsmon -F
Type=simple

you must have some other problem, how did you configure and start nut?

> port
> 
> Required. This is the serial port where the UPS is connected. On a Linux
> system, the first serial port usually is /dev/ttyS0. On FreeBSD and similar
> systems, it probably will be /dev/cuaa0
> 
> what a nonsense - USB - find it youself idiotic tool

RTFM man usbhid-ups
"""The driver ignores the "port" value in ups.conf."""
For usb ups:
[myups]
    driver = usbhid-ups
    port = auto

Comment 2 Harald Reindl 2016-06-23 12:31:55 UTC
not wrong - nut-driver.service don't create the folder and in general tmpfiles is used to ensure they are created at boot, but typically rpm-scriptlets make sure anything is present right after install

i did read the FM - "driver = usbhid-ups" said no device found, yes apcupsd was stopped at that time

Comment 3 Michal Hlavinka 2016-06-23 13:28:47 UTC
I will need more data.

1) what ups do you have?

2) what is your configuration?

3) output of lsusb

4) what are permissions on your system?
ls -lZ /dev/bus/usb/BUS_NUMBER_FROM_LSUSB/DEVICE_NUMBER_FROM_LSUSB

5) Do you have selinux enabled? If so, could you try it with selinux in permissive mode?

Comment 4 Michal Hlavinka 2016-08-11 16:36:11 UTC
/var/run/nut creation fixed

Comment 5 Fedora Update System 2016-08-12 09:14:14 UTC
nut-2.7.4-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-1c864f40a5

Comment 6 Fedora Update System 2016-08-12 09:14:21 UTC
nut-2.7.4-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-0d2525e306

Comment 7 Fedora Update System 2016-08-12 09:14:28 UTC
nut-2.7.4-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8f17c643d3

Comment 8 Fedora Update System 2016-08-12 14:27:01 UTC
nut-2.7.4-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8f17c643d3

Comment 9 Fedora Update System 2016-08-12 20:51:59 UTC
nut-2.7.4-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-1c864f40a5

Comment 10 Fedora Update System 2016-08-12 20:52:03 UTC
nut-2.7.4-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-0d2525e306

Comment 11 Fedora Update System 2016-09-17 07:23:23 UTC
nut-2.7.4-4.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8c02066db5

Comment 12 Fedora Update System 2016-09-18 07:23:21 UTC
nut-2.7.4-4.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8c02066db5

Comment 13 Fedora Update System 2016-09-23 16:25:51 UTC
nut-2.7.4-4.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 14 Fedora Update System 2016-11-01 13:21:33 UTC
nut-2.7.4-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.

Comment 15 Fedora Update System 2016-11-01 16:22:26 UTC
nut-2.7.4-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.