Bug 1184960 - "systemctl enable messagebus.service" fails
Summary: "systemctl enable messagebus.service" fails
Keywords:
Status: CLOSED DUPLICATE of bug 1014311
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-22 15:05 UTC by Miroslav Suchý
Modified: 2015-01-31 20:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-31 20:05:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1001607 0 unspecified CLOSED RFE: provide better error when attempting to enable/disable generated units 2021-02-22 00:41:40 UTC

Internal Links: 1001607

Description Miroslav Suchý 2015-01-22 15:05:05 UTC
Description of problem:
When running:
  systemctl enable messagebus.service
I got this message:
  Failed to execute operation: No such file or directory
I am able to enable/disable all other services but this on.
It is enabled by default, so it is not really problem for me. It is just weird.

Version-Release number of selected component (if applicable):
# rpm -qf /bin/systemctl /usr/lib/systemd/system/messagebus.service
systemd-216-14.fc21.x86_64
dbus-1.8.14-1.fc21.x86_64

How reproducible:
always
I was able to reproduce this on RHEL7 too.

Steps to Reproduce:
1. systemctl enable messagebus.service

Actual results:
  Failed to execute operation: No such file or directory

Expected results:
  no errors

Additional info:
Tail of strace:
access("/etc/systemd/system/messagebus.service", F_OK) = -1 ENOENT (No such file or directory)
access("/run/systemd/system/messagebus.service", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/local/lib/systemd/system/messagebus.service", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/systemd/system/messagebus.service", F_OK) = 0
stat("/proc/1/root", {st_mode=S_IFDIR|0555, st_size=4096, ...}) = 0
stat("/", {st_mode=S_IFDIR|0555, st_size=4096, ...}) = 0
lstat("/run/systemd/system/", {st_mode=S_IFDIR|0755, st_size=140, ...}) = 0
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"OK f97d44f4b5fb434f9dbab13f57730"..., 256}], msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=1, uid=0, gid=0}}, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 52
sendmsg(3, {msg_name(0)=NULL, msg_iov(2)=[{"l\1\4\1$\0\0\0\1\0\0\0\242\0\0\0\1\1o\0\31\0\0\0/org/fre"..., 184}, {"\27\0\0\0\22\0\0\0messagebus.service\0\0\0\0\0\0"..., 36}], msg_controllen=0, msg_flags=0}, MSG_DONTWAIT|MSG_NOSIGNAL) = 220
recvmsg(3, 0x7fff2e0d48e0, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=3, events=POLLIN}], 1, {24, 999970000}, NULL, 8) = 1 ([{fd=3, revents=POLLIN}], left {24, 999480933})
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"l\3\1\1\36\0\0\0\1\0\0\0?\0\0\0\5\1u\0\1\0\0\0", 24}], msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=1, uid=0, gid=0}}, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 24
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\4\1s\0'\0\0\0org.freedesktop.DBus.Err"..., 86}], msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=1, uid=0, gid=0}}, msg_flags=MSG_CMSG_CLOEXEC}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 86
writev(2, [{"Failed to execute operation: No "..., 54}, {"\n", 1}], 2Failed to execute operation: No such file or directory
) = 55
close(3)                                = 0
exit_group(1)                           = ?
+++ exited with 1 +++


Selinux is disabled (not sure if this matters).

Comment 1 Zbigniew Jędrzejewski-Szmek 2015-01-31 20:05:13 UTC
It's because messagebus.service is a symlink to dbus.service. We do not properly support enablement by alias. But a nicer error message would be in order, or preferable, redirection to the target of the symlink.

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


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