FS#76829 - [apcupsd] service won't start when no network
Attached to Project:
Community Packages
Opened by Dmytro Bagrii (dimich) - Thursday, 15 December 2022, 00:11 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:05 GMT
Opened by Dmytro Bagrii (dimich) - Thursday, 15 December 2022, 00:11 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:05 GMT
|
Details
apcupsd.service depends on network-online.target for some
reason.
If network interface is configured to use DHCP and network is unavailable (e.g. remote equipment is powered off) apcupsd.service won't start and apcupsd will not shutdown/hibernate system on timeout or battery level threshold. apcupsd 3.14.14-7 |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:05 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/apcupsd/issues/2
Saturday, 25 November 2023, 20:05 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/apcupsd/issues/2
FS#73607to support snmp. Not sure if both scenarios can be supported. I'd just work around the issue and not use DHCP.Actually "sendto: Network is unreachable" is not a failure. Host with SNMP server may be unreachable for many reasons.
Maybe separate service units for local and network configurations as a compromise?