Bug 1835880 - systemd failed to add dependency on ods-enforcerd
Summary: systemd failed to add dependency on ods-enforcerd
Keywords:
Status: CLOSED DUPLICATE of bug 1833718
Alias: None
Product: Fedora
Classification: Fedora
Component: opendnssec
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-14 16:43 UTC by pavel.strzinek@gmail.com
Modified: 2020-05-28 17:37 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-28 17:37:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description pavel.strzinek@gmail.com 2020-05-14 16:43:33 UTC
Description of problem:

/usr/lib/systemd/system/ods-signerd.service:3: Failed to add dependency on ods-enforcerd, ignoring: Invalid argument
CODE_FILE	src/core/load-fragment.c
CODE_FUNC	config_parse_unit_deps
CODE_LINE	180
CONFIG_FILE	/usr/lib/systemd/system/ods-signerd.service
CONFIG_LINE	3
MESSAGE_ID	xxx
PRIORITY	3
SYSLOG_FACILITY	3
SYSLOG_IDENTIFIER	systemd
UNIT	ods-signerd.service
_BOOT_ID	xxx
_CAP_EFFECTIVE	3fffffffff
_CMDLINE	/usr/lib/systemd/systemd --switched-root --system --deserialize 30
_COMM	systemd
_EXE	/usr/lib/systemd/systemd
_GID	0
_HOSTNAME	xxx
_MACHINE_ID	xxx
_PID	1
_SELINUX_CONTEXT	system_u:system_r:init_t:s0
_SOURCE_REALTIME_TIMESTAMP	1588789847985641
_SYSTEMD_CGROUP	/init.scope
_SYSTEMD_SLICE	-.slice
_SYSTEMD_UNIT	init.scope
_TRANSPORT	journal
_UID	0
__CURSOR	s=517d9a7bd3f648009a2001f9a32c357f;i=34513;b=17833959c4e441568afda1164f06a550;m=d2db8184;t=5a4fef6830dff;x=5d6143fa35acbb4a
__MONOTONIC_TIMESTAMP	3537600900
__REALTIME_TIMESTAMP	1588789847985663


Actual results:
Above error in system log

Expected results:
No errors reported

Additional info:

How to fix:
add ".service" to "After" line in file /usr/lib/systemd/system/ods-signerd.service

Present, failing line:
After=syslog.target network.target ods-enforcerd

Fixed line:
After=syslog.target network.target ods-enforcerd.service

Comment 1 Paul Wouters 2020-05-15 00:57:20 UTC
these are supposed to be somewhat independant. the ods-enforcer could be run via cron instead of via a daemon. At least in the original design.

Comment 2 Paul Wouters 2020-05-28 17:37:23 UTC

*** This bug has been marked as a duplicate of bug 1833718 ***


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