Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43483 - [apcupsd] 3.14.12-3 daemon fails to start because /run/apcupsd is missing
Attached to Project:
Community Packages
Opened by Roland Eckert (romax) - Saturday, 17 January 2015, 02:57 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 17 January 2015, 04:16 GMT
Opened by Roland Eckert (romax) - Saturday, 17 January 2015, 02:57 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 17 January 2015, 04:16 GMT
|
DetailsDescription:
After installation of the package apcupsd, the apcupsd daemon fails to start. Additional info: * package version 3.14.12-3 The log contains: Jan 17 03:29:26 myhost systemd[1]: Starting APC UPS Monitor... Jan 17 03:29:26 myhost systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument Jan 17 03:29:26 myhost systemd[1]: Started APC UPS Monitor. Jan 17 03:29:26 myhost apcupsd[191]: Cannot create /run/apcupsd/LCK.. serial port lock file: ERR=No such file or directory Jan 17 03:29:26 myhost apcupsd[191]: apcupsd FATAL ERROR in apcupsd.c at line 283 Unable to create UPS lock file. If apcupsd or apctest is already running, please stop it and run this program again. Jan 17 03:29:26 myhost apcupsd[191]: apcupsd error shutdown completed Jan 17 03:29:26 myhost apcupsd[191]: apcupsd FATAL ERROR in apcupsd.c at line 283 Jan 17 03:29:26 myhost apcupsd[191]: Unable to create UPS lock file. Jan 17 03:29:26 myhost apcupsd[191]: If apcupsd or apctest is already running, Jan 17 03:29:26 myhost apcupsd[191]: please stop it and run this program again. Jan 17 03:29:26 myhost systemd[1]: apcupsd.service: main process exited, code=exited, status=1/FAILURE Jan 17 03:29:26 myhost systemd[1]: Unit apcupsd.service entered failed state. Jan 17 03:29:26 myhost systemd[1]: apcupsd.service failed. Steps to reproduce: pacman -S community/apcupsd systemctl start apcupsd.service journalctl -b Fixing this is possible by creating the folder manually: mkdir /run/apcupsd |
This task depends upon
Closed by Doug Newgard (Scimmia)
Saturday, 17 January 2015, 04:16 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: This behaviour has been experienced on the ARMv6l (Raspberry Pi B) platform. I've just verified on i686, the folder isn't there after installation either, but the damon starts nevertheless, creating the lock file in /run instead of /run/apcupsd/. Sorry for reporting, I was not familiar with the PC architecture only policy.
Saturday, 17 January 2015, 04:16 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: This behaviour has been experienced on the ARMv6l (Raspberry Pi B) platform. I've just verified on i686, the folder isn't there after installation either, but the damon starts nevertheless, creating the lock file in /run instead of /run/apcupsd/. Sorry for reporting, I was not familiar with the PC architecture only policy.