CentOS 7 reboot error getting authority?What caused my CentOS 6.4 box to reboot itself?CentOs eth2 wont start...
How could the B-29 bomber back up under its own power?
Does science define life as "beginning at conception"?
(For training purposes) Are there any openings with rook pawns that are more effective than others (and if so, what are they)?
Department head said that group project may be rejected. How to mitigate?
Nunc est bibendum: gerund or gerundive?
amsmath: How can I use the equation numbering and label manually and anywhere?
One word for 'the thing that attracts me'?
Is there a solution to paying high fees when opening and closing lightning channels once we hit a fee only market?
Writing "hahaha" versus describing the laugh
How can I reduce the size of matrix?
How would a physicist explain this starship engine?
Which values for voltage divider
Surface of the 3x3x3 cube as a graph
Why did Nick Fury not hesitate in blowing up the plane he thought was carrying a nuke?
Negative impact of having the launch pad away from the Equator
Can the Conjure Barrage spell stack with the Disarming Attack or Trip Attack Battle Master maneuvers?
Split into three!
Is there a word for pant sleeves?
Make the `diff` command look only for differences from a specified range of lines
csname in newenviroment
Salesforce bug enabled "Modify All"
How to safely discharge oneself
Is there any mention of ghosts who live outside the Hogwarts castle?
Why the work done is positive when bringing 2 opposite charges together?
CentOS 7 reboot error getting authority?
What caused my CentOS 6.4 box to reboot itself?CentOs eth2 wont start on rebootHow to detect the screen is locked or not when the screen saver is active on Redhat 6.6?Getting Error updating CentOS 6.7Error getting authority: Error initializing authority: Could not connect: Resource temporarily unavailable (g-io-error-quark, 27)CentOS cannot mount /home, Error getting authority: Error initializing authority: Could not connect: No such file or directoryCentos: getting this error on Atom editorCentOS 7 fails to reboot my PCkernel error in CentOS 6.9
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm trying to reboot the CentOS 7 after yum update
, and getting the following error when I run sudo reboot
.
Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9)
I also get the same error when I run sudo service dbus start
.
Can anyone help?
centos reboot d-bus
bumped to the homepage by Community♦ 44 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm trying to reboot the CentOS 7 after yum update
, and getting the following error when I run sudo reboot
.
Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9)
I also get the same error when I run sudo service dbus start
.
Can anyone help?
centos reboot d-bus
bumped to the homepage by Community♦ 44 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm trying to reboot the CentOS 7 after yum update
, and getting the following error when I run sudo reboot
.
Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9)
I also get the same error when I run sudo service dbus start
.
Can anyone help?
centos reboot d-bus
I'm trying to reboot the CentOS 7 after yum update
, and getting the following error when I run sudo reboot
.
Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9)
I also get the same error when I run sudo service dbus start
.
Can anyone help?
centos reboot d-bus
centos reboot d-bus
edited Aug 23 '18 at 23:17
slm♦
259k72554703
259k72554703
asked Aug 23 '18 at 23:02
Gihyeon ParkGihyeon Park
612
612
bumped to the homepage by Community♦ 44 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 44 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This issue has to do with SELinux.
An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)"
You can either try and deal with this or disable SELinux. It's generally advisable to NOT disable software that's attempting to make your system more secure, but if it's a desktop or not a production type of system, these are easier approaches to find more accepting.
To disable SELinux and put it into permissive
mode:
$ getenforce
Enforcing
$ setenforce 0
setenforce: SELinux is disabled
To make this permanent you can edit this file, /etc/selinux/config
and change the line SELINUX=
so that it says either permissive
or disabled
. A reboot is required to pick up the change from this file.
/ permissions
Another culprit that may lead to this scenario has to do with the root directory's permissions. There's a "solution" logged on Redhat's main solutions site titled: What is "DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient" ?.
The issue is this:
Permissions on / have been set to 700 ; restoring to 555 solved the issue
The fix:
Ensure permissions on / are 555 ; if not adjust them by chmod 555 /
You can further verify if this is your issue using the abrt
. You'll typically see this message when you log into a system that's suffering from this misconfiguration:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1444824402
Investigating the ABRT failure:
$ abrt-cli list --since 1444824402
id 050f5a46e0749583aaf102958b2ab1cc976133d9
reason: bus.py:122:__new__:DBusException: org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
time: Wed 14 Oct 2015 06:56:16 AM EDT
cmdline: /usr/bin/python -Es /usr/bin/firewall-cmd --zone= --change-interface=eth0
package: firewalld-0.3.9-11.el7
uid: 0 (root)
count: 2
Directory: /var/spool/abrt/Python-2015-10-14-06:56:16-905
Run 'abrt-cli report /var/spool/abrt/Python-2015-10-14-06:56:16-905' for creating a case in Red Hat Customer Portal
The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
systemd also reports this failure state:
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded failed failed Avahi mDNS/DNS-SD Stack
libstoragemgmt.service loaded failed failed libstoragemgmt plug-in server daemon
ovirt-guest-agent.service loaded failed failed oVirt Guest Agent
postfix.service loaded failed failed Postfix Mail Transport Agent
rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
systemd-logind.service loaded failed failed Login Service
tuned.service loaded failed failed Dynamic System Tuning Daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
References
- https://access.redhat.com/solutions/1990203
- 5.4.2. Disabling SELinux
- Disabling SELinux
As posted in the original question, I get the "Error getting authority: Error initializing authority" when I run "sudo reboot" command.
– Gihyeon Park
Aug 23 '18 at 23:49
@GihyeonParksudo shutdown -r now
?
– slm♦
Aug 24 '18 at 0:04
sudo shutdown -r now get the following errors: Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) Could not watch jobs: Connection reset by peer Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.
– Gihyeon Park
Aug 24 '18 at 0:08
I do have /dev/initctl lrwxrwxrwx. 1 root root 25 May 21 15:00 /dev/initctl -> /run/systemd/initctl/fifo
– Gihyeon Park
Aug 24 '18 at 0:11
Permissions on / is already 555. and sudo systemctl --failed gives another error (Failed to list units: Connection reset by peer).
– Gihyeon Park
Aug 24 '18 at 18:52
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f464523%2fcentos-7-reboot-error-getting-authority%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This issue has to do with SELinux.
An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)"
You can either try and deal with this or disable SELinux. It's generally advisable to NOT disable software that's attempting to make your system more secure, but if it's a desktop or not a production type of system, these are easier approaches to find more accepting.
To disable SELinux and put it into permissive
mode:
$ getenforce
Enforcing
$ setenforce 0
setenforce: SELinux is disabled
To make this permanent you can edit this file, /etc/selinux/config
and change the line SELINUX=
so that it says either permissive
or disabled
. A reboot is required to pick up the change from this file.
/ permissions
Another culprit that may lead to this scenario has to do with the root directory's permissions. There's a "solution" logged on Redhat's main solutions site titled: What is "DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient" ?.
The issue is this:
Permissions on / have been set to 700 ; restoring to 555 solved the issue
The fix:
Ensure permissions on / are 555 ; if not adjust them by chmod 555 /
You can further verify if this is your issue using the abrt
. You'll typically see this message when you log into a system that's suffering from this misconfiguration:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1444824402
Investigating the ABRT failure:
$ abrt-cli list --since 1444824402
id 050f5a46e0749583aaf102958b2ab1cc976133d9
reason: bus.py:122:__new__:DBusException: org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
time: Wed 14 Oct 2015 06:56:16 AM EDT
cmdline: /usr/bin/python -Es /usr/bin/firewall-cmd --zone= --change-interface=eth0
package: firewalld-0.3.9-11.el7
uid: 0 (root)
count: 2
Directory: /var/spool/abrt/Python-2015-10-14-06:56:16-905
Run 'abrt-cli report /var/spool/abrt/Python-2015-10-14-06:56:16-905' for creating a case in Red Hat Customer Portal
The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
systemd also reports this failure state:
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded failed failed Avahi mDNS/DNS-SD Stack
libstoragemgmt.service loaded failed failed libstoragemgmt plug-in server daemon
ovirt-guest-agent.service loaded failed failed oVirt Guest Agent
postfix.service loaded failed failed Postfix Mail Transport Agent
rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
systemd-logind.service loaded failed failed Login Service
tuned.service loaded failed failed Dynamic System Tuning Daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
References
- https://access.redhat.com/solutions/1990203
- 5.4.2. Disabling SELinux
- Disabling SELinux
As posted in the original question, I get the "Error getting authority: Error initializing authority" when I run "sudo reboot" command.
– Gihyeon Park
Aug 23 '18 at 23:49
@GihyeonParksudo shutdown -r now
?
– slm♦
Aug 24 '18 at 0:04
sudo shutdown -r now get the following errors: Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) Could not watch jobs: Connection reset by peer Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.
– Gihyeon Park
Aug 24 '18 at 0:08
I do have /dev/initctl lrwxrwxrwx. 1 root root 25 May 21 15:00 /dev/initctl -> /run/systemd/initctl/fifo
– Gihyeon Park
Aug 24 '18 at 0:11
Permissions on / is already 555. and sudo systemctl --failed gives another error (Failed to list units: Connection reset by peer).
– Gihyeon Park
Aug 24 '18 at 18:52
add a comment |
This issue has to do with SELinux.
An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)"
You can either try and deal with this or disable SELinux. It's generally advisable to NOT disable software that's attempting to make your system more secure, but if it's a desktop or not a production type of system, these are easier approaches to find more accepting.
To disable SELinux and put it into permissive
mode:
$ getenforce
Enforcing
$ setenforce 0
setenforce: SELinux is disabled
To make this permanent you can edit this file, /etc/selinux/config
and change the line SELINUX=
so that it says either permissive
or disabled
. A reboot is required to pick up the change from this file.
/ permissions
Another culprit that may lead to this scenario has to do with the root directory's permissions. There's a "solution" logged on Redhat's main solutions site titled: What is "DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient" ?.
The issue is this:
Permissions on / have been set to 700 ; restoring to 555 solved the issue
The fix:
Ensure permissions on / are 555 ; if not adjust them by chmod 555 /
You can further verify if this is your issue using the abrt
. You'll typically see this message when you log into a system that's suffering from this misconfiguration:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1444824402
Investigating the ABRT failure:
$ abrt-cli list --since 1444824402
id 050f5a46e0749583aaf102958b2ab1cc976133d9
reason: bus.py:122:__new__:DBusException: org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
time: Wed 14 Oct 2015 06:56:16 AM EDT
cmdline: /usr/bin/python -Es /usr/bin/firewall-cmd --zone= --change-interface=eth0
package: firewalld-0.3.9-11.el7
uid: 0 (root)
count: 2
Directory: /var/spool/abrt/Python-2015-10-14-06:56:16-905
Run 'abrt-cli report /var/spool/abrt/Python-2015-10-14-06:56:16-905' for creating a case in Red Hat Customer Portal
The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
systemd also reports this failure state:
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded failed failed Avahi mDNS/DNS-SD Stack
libstoragemgmt.service loaded failed failed libstoragemgmt plug-in server daemon
ovirt-guest-agent.service loaded failed failed oVirt Guest Agent
postfix.service loaded failed failed Postfix Mail Transport Agent
rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
systemd-logind.service loaded failed failed Login Service
tuned.service loaded failed failed Dynamic System Tuning Daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
References
- https://access.redhat.com/solutions/1990203
- 5.4.2. Disabling SELinux
- Disabling SELinux
As posted in the original question, I get the "Error getting authority: Error initializing authority" when I run "sudo reboot" command.
– Gihyeon Park
Aug 23 '18 at 23:49
@GihyeonParksudo shutdown -r now
?
– slm♦
Aug 24 '18 at 0:04
sudo shutdown -r now get the following errors: Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) Could not watch jobs: Connection reset by peer Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.
– Gihyeon Park
Aug 24 '18 at 0:08
I do have /dev/initctl lrwxrwxrwx. 1 root root 25 May 21 15:00 /dev/initctl -> /run/systemd/initctl/fifo
– Gihyeon Park
Aug 24 '18 at 0:11
Permissions on / is already 555. and sudo systemctl --failed gives another error (Failed to list units: Connection reset by peer).
– Gihyeon Park
Aug 24 '18 at 18:52
add a comment |
This issue has to do with SELinux.
An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)"
You can either try and deal with this or disable SELinux. It's generally advisable to NOT disable software that's attempting to make your system more secure, but if it's a desktop or not a production type of system, these are easier approaches to find more accepting.
To disable SELinux and put it into permissive
mode:
$ getenforce
Enforcing
$ setenforce 0
setenforce: SELinux is disabled
To make this permanent you can edit this file, /etc/selinux/config
and change the line SELINUX=
so that it says either permissive
or disabled
. A reboot is required to pick up the change from this file.
/ permissions
Another culprit that may lead to this scenario has to do with the root directory's permissions. There's a "solution" logged on Redhat's main solutions site titled: What is "DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient" ?.
The issue is this:
Permissions on / have been set to 700 ; restoring to 555 solved the issue
The fix:
Ensure permissions on / are 555 ; if not adjust them by chmod 555 /
You can further verify if this is your issue using the abrt
. You'll typically see this message when you log into a system that's suffering from this misconfiguration:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1444824402
Investigating the ABRT failure:
$ abrt-cli list --since 1444824402
id 050f5a46e0749583aaf102958b2ab1cc976133d9
reason: bus.py:122:__new__:DBusException: org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
time: Wed 14 Oct 2015 06:56:16 AM EDT
cmdline: /usr/bin/python -Es /usr/bin/firewall-cmd --zone= --change-interface=eth0
package: firewalld-0.3.9-11.el7
uid: 0 (root)
count: 2
Directory: /var/spool/abrt/Python-2015-10-14-06:56:16-905
Run 'abrt-cli report /var/spool/abrt/Python-2015-10-14-06:56:16-905' for creating a case in Red Hat Customer Portal
The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
systemd also reports this failure state:
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded failed failed Avahi mDNS/DNS-SD Stack
libstoragemgmt.service loaded failed failed libstoragemgmt plug-in server daemon
ovirt-guest-agent.service loaded failed failed oVirt Guest Agent
postfix.service loaded failed failed Postfix Mail Transport Agent
rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
systemd-logind.service loaded failed failed Login Service
tuned.service loaded failed failed Dynamic System Tuning Daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
References
- https://access.redhat.com/solutions/1990203
- 5.4.2. Disabling SELinux
- Disabling SELinux
This issue has to do with SELinux.
An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)"
You can either try and deal with this or disable SELinux. It's generally advisable to NOT disable software that's attempting to make your system more secure, but if it's a desktop or not a production type of system, these are easier approaches to find more accepting.
To disable SELinux and put it into permissive
mode:
$ getenforce
Enforcing
$ setenforce 0
setenforce: SELinux is disabled
To make this permanent you can edit this file, /etc/selinux/config
and change the line SELINUX=
so that it says either permissive
or disabled
. A reboot is required to pick up the change from this file.
/ permissions
Another culprit that may lead to this scenario has to do with the root directory's permissions. There's a "solution" logged on Redhat's main solutions site titled: What is "DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient" ?.
The issue is this:
Permissions on / have been set to 700 ; restoring to 555 solved the issue
The fix:
Ensure permissions on / are 555 ; if not adjust them by chmod 555 /
You can further verify if this is your issue using the abrt
. You'll typically see this message when you log into a system that's suffering from this misconfiguration:
ABRT has detected 1 problem(s). For more info run: abrt-cli list --since 1444824402
Investigating the ABRT failure:
$ abrt-cli list --since 1444824402
id 050f5a46e0749583aaf102958b2ab1cc976133d9
reason: bus.py:122:__new__:DBusException: org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)
time: Wed 14 Oct 2015 06:56:16 AM EDT
cmdline: /usr/bin/python -Es /usr/bin/firewall-cmd --zone= --change-interface=eth0
package: firewalld-0.3.9-11.el7
uid: 0 (root)
count: 2
Directory: /var/spool/abrt/Python-2015-10-14-06:56:16-905
Run 'abrt-cli report /var/spool/abrt/Python-2015-10-14-06:56:16-905' for creating a case in Red Hat Customer Portal
The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges
systemd also reports this failure state:
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded failed failed Avahi mDNS/DNS-SD Stack
libstoragemgmt.service loaded failed failed libstoragemgmt plug-in server daemon
ovirt-guest-agent.service loaded failed failed oVirt Guest Agent
postfix.service loaded failed failed Postfix Mail Transport Agent
rngd.service loaded failed failed Hardware RNG Entropy Gatherer Daemon
systemd-logind.service loaded failed failed Login Service
tuned.service loaded failed failed Dynamic System Tuning Daemon
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
7 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
References
- https://access.redhat.com/solutions/1990203
- 5.4.2. Disabling SELinux
- Disabling SELinux
edited Aug 24 '18 at 18:55
answered Aug 23 '18 at 23:17
slm♦slm
259k72554703
259k72554703
As posted in the original question, I get the "Error getting authority: Error initializing authority" when I run "sudo reboot" command.
– Gihyeon Park
Aug 23 '18 at 23:49
@GihyeonParksudo shutdown -r now
?
– slm♦
Aug 24 '18 at 0:04
sudo shutdown -r now get the following errors: Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) Could not watch jobs: Connection reset by peer Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.
– Gihyeon Park
Aug 24 '18 at 0:08
I do have /dev/initctl lrwxrwxrwx. 1 root root 25 May 21 15:00 /dev/initctl -> /run/systemd/initctl/fifo
– Gihyeon Park
Aug 24 '18 at 0:11
Permissions on / is already 555. and sudo systemctl --failed gives another error (Failed to list units: Connection reset by peer).
– Gihyeon Park
Aug 24 '18 at 18:52
add a comment |
As posted in the original question, I get the "Error getting authority: Error initializing authority" when I run "sudo reboot" command.
– Gihyeon Park
Aug 23 '18 at 23:49
@GihyeonParksudo shutdown -r now
?
– slm♦
Aug 24 '18 at 0:04
sudo shutdown -r now get the following errors: Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) Could not watch jobs: Connection reset by peer Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.
– Gihyeon Park
Aug 24 '18 at 0:08
I do have /dev/initctl lrwxrwxrwx. 1 root root 25 May 21 15:00 /dev/initctl -> /run/systemd/initctl/fifo
– Gihyeon Park
Aug 24 '18 at 0:11
Permissions on / is already 555. and sudo systemctl --failed gives another error (Failed to list units: Connection reset by peer).
– Gihyeon Park
Aug 24 '18 at 18:52
As posted in the original question, I get the "Error getting authority: Error initializing authority" when I run "sudo reboot" command.
– Gihyeon Park
Aug 23 '18 at 23:49
As posted in the original question, I get the "Error getting authority: Error initializing authority" when I run "sudo reboot" command.
– Gihyeon Park
Aug 23 '18 at 23:49
@GihyeonPark
sudo shutdown -r now
?– slm♦
Aug 24 '18 at 0:04
@GihyeonPark
sudo shutdown -r now
?– slm♦
Aug 24 '18 at 0:04
sudo shutdown -r now get the following errors: Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) Could not watch jobs: Connection reset by peer Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.
– Gihyeon Park
Aug 24 '18 at 0:08
sudo shutdown -r now get the following errors: Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An SELinux policy prevents this sender from sending this message to this recipient, 0 matched rules; type="method_call", sender="(null)" (inactive) interface="org.freedesktop.DBus" member="Hello" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus) (g-dbus-error-quark, 9) Could not watch jobs: Connection reset by peer Failed to open /dev/initctl: No such device or address Failed to talk to init daemon.
– Gihyeon Park
Aug 24 '18 at 0:08
I do have /dev/initctl lrwxrwxrwx. 1 root root 25 May 21 15:00 /dev/initctl -> /run/systemd/initctl/fifo
– Gihyeon Park
Aug 24 '18 at 0:11
I do have /dev/initctl lrwxrwxrwx. 1 root root 25 May 21 15:00 /dev/initctl -> /run/systemd/initctl/fifo
– Gihyeon Park
Aug 24 '18 at 0:11
Permissions on / is already 555. and sudo systemctl --failed gives another error (Failed to list units: Connection reset by peer).
– Gihyeon Park
Aug 24 '18 at 18:52
Permissions on / is already 555. and sudo systemctl --failed gives another error (Failed to list units: Connection reset by peer).
– Gihyeon Park
Aug 24 '18 at 18:52
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f464523%2fcentos-7-reboot-error-getting-authority%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown