Error getting authority: Error initializing authority: Could not connect: Resource temporarily unavailable...
up vote
2
down vote
favorite
Every time I restart a service (e.g. service exim restart, run as root), I get the following error message:
Error getting authority: Error initializing authority: Could not connect: Resource temporarily unavailable (g-io-error-quark, 27)
The dbus-daemon also has a 100% CPU usage.
The output of journalctl -r -p err -b shows an extreme amount - 6979 entries - of the following error:
pam_systemd(crond:session): Failed to connect to system bus: Resource temporarily unavailable
There are also 5033 session files. Theses are when a session is made via ssh, these are supposed to be deleted automatically, but I'm hesitant to delete them myself
ls -1 /var/run/systemd/sessions/ | wc -l
5033
What is the cause and how can I prevent this?
- CentOS Linux release 7.2.1511 (Core)
centos systemd d-bus
asked Nov 18 '16 at 11:32
blade19899
2871720
bumped to the homepage by Community♦ yesterday
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 |
up vote
2
down vote
favorite
Every time I restart a service (e.g. service exim restart, run as root), I get the following error message:
Error getting authority: Error initializing authority: Could not connect: Resource temporarily unavailable (g-io-error-quark, 27)
The dbus-daemon also has a 100% CPU usage.
The output of journalctl -r -p err -b shows an extreme amount - 6979 entries - of the following error:
pam_systemd(crond:session): Failed to connect to system bus: Resource temporarily unavailable
There are also 5033 session files. Theses are when a session is made via ssh, these are supposed to be deleted automatically, but I'm hesitant to delete them myself
ls -1 /var/run/systemd/sessions/ | wc -l
5033
What is the cause and how can I prevent this?
- CentOS Linux release 7.2.1511 (Core)
centos systemd d-bus
asked Nov 18 '16 at 11:32
blade19899
2871720
bumped to the homepage by Community♦ yesterday
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 |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
Every time I restart a service (e.g. service exim restart, run as root), I get the following error message:
Error getting authority: Error initializing authority: Could not connect: Resource temporarily unavailable (g-io-error-quark, 27)
The dbus-daemon also has a 100% CPU usage.
The output of journalctl -r -p err -b shows an extreme amount - 6979 entries - of the following error:
pam_systemd(crond:session): Failed to connect to system bus: Resource temporarily unavailable
There are also 5033 session files. Theses are when a session is made via ssh, these are supposed to be deleted automatically, but I'm hesitant to delete them myself
ls -1 /var/run/systemd/sessions/ | wc -l
5033
What is the cause and how can I prevent this?
- CentOS Linux release 7.2.1511 (Core)
centos systemd d-bus
asked Nov 18 '16 at 11:32
blade19899
2871720
Every time I restart a service (e.g. service exim restart, run as root), I get the following error message:
Error getting authority: Error initializing authority: Could not connect: Resource temporarily unavailable (g-io-error-quark, 27)
The dbus-daemon also has a 100% CPU usage.
The output of journalctl -r -p err -b shows an extreme amount - 6979 entries - of the following error:
pam_systemd(crond:session): Failed to connect to system bus: Resource temporarily unavailable
There are also 5033 session files. Theses are when a session is made via ssh, these are supposed to be deleted automatically, but I'm hesitant to delete them myself
ls -1 /var/run/systemd/sessions/ | wc -l
5033
What is the cause and how can I prevent this?
- CentOS Linux release 7.2.1511 (Core)
centos systemd d-bus
centos systemd d-bus
asked Nov 18 '16 at 11:32
blade19899
2871720
asked Nov 18 '16 at 11:32
blade19899
2871720
edited Jan 31 '17 at 9:13
asked Nov 18 '16 at 11:32
blade19899
2871720
asked Nov 18 '16 at 11:32
blade19899
2871720
asked Nov 18 '16 at 11:32
blade19899
2871720
2871720
bumped to the homepage by Community♦ yesterday
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♦ yesterday
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
up vote
0
down vote
this is a bug of systemd-logind && dbus-daemon，relate to https://github.com/systemd/systemd/issues/1961
because crond always call pam_systemd, and pam_systemd always call systemd-logind to create a session scope use dbus-daemon , but sometimes dbus-daemon alway do not work , so we should better make crond do not call systemd-logind
stop systemd-logind also will not influence ssh , just can not use session cgroup
sudo sed -i -e '/^[^#]*pam_systemd.so/ s/^/#&/g' /etc/pam.d/*
sudo systemctl mask systemd-logind
sudo systemctl stop systemd-logind
answered Aug 8 '17 at 12:25
穆阿浩
101114
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',
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%2f324260%2ferror-getting-authority-error-initializing-authority-could-not-connect-resour%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
up vote
0
down vote
this is a bug of systemd-logind && dbus-daemon，relate to https://github.com/systemd/systemd/issues/1961
because crond always call pam_systemd, and pam_systemd always call systemd-logind to create a session scope use dbus-daemon , but sometimes dbus-daemon alway do not work , so we should better make crond do not call systemd-logind
stop systemd-logind also will not influence ssh , just can not use session cgroup
sudo sed -i -e '/^[^#]*pam_systemd.so/ s/^/#&/g' /etc/pam.d/*
sudo systemctl mask systemd-logind
sudo systemctl stop systemd-logind
answered Aug 8 '17 at 12:25
穆阿浩
101114
add a comment |
up vote
0
down vote
this is a bug of systemd-logind && dbus-daemon，relate to https://github.com/systemd/systemd/issues/1961
because crond always call pam_systemd, and pam_systemd always call systemd-logind to create a session scope use dbus-daemon , but sometimes dbus-daemon alway do not work , so we should better make crond do not call systemd-logind
stop systemd-logind also will not influence ssh , just can not use session cgroup
sudo sed -i -e '/^[^#]*pam_systemd.so/ s/^/#&/g' /etc/pam.d/*
sudo systemctl mask systemd-logind
sudo systemctl stop systemd-logind
answered Aug 8 '17 at 12:25
穆阿浩
101114
add a comment |
up vote
0
down vote
up vote
0
down vote
this is a bug of systemd-logind && dbus-daemon，relate to https://github.com/systemd/systemd/issues/1961
because crond always call pam_systemd, and pam_systemd always call systemd-logind to create a session scope use dbus-daemon , but sometimes dbus-daemon alway do not work , so we should better make crond do not call systemd-logind
stop systemd-logind also will not influence ssh , just can not use session cgroup
sudo sed -i -e '/^[^#]*pam_systemd.so/ s/^/#&/g' /etc/pam.d/*
sudo systemctl mask systemd-logind
sudo systemctl stop systemd-logind
answered Aug 8 '17 at 12:25
穆阿浩
101114
this is a bug of systemd-logind && dbus-daemon，relate to https://github.com/systemd/systemd/issues/1961
because crond always call pam_systemd, and pam_systemd always call systemd-logind to create a session scope use dbus-daemon , but sometimes dbus-daemon alway do not work , so we should better make crond do not call systemd-logind
stop systemd-logind also will not influence ssh , just can not use session cgroup
sudo sed -i -e '/^[^#]*pam_systemd.so/ s/^/#&/g' /etc/pam.d/*
sudo systemctl mask systemd-logind
sudo systemctl stop systemd-logind
answered Aug 8 '17 at 12:25
穆阿浩
101114
edited Aug 8 '17 at 12:38
answered Aug 8 '17 at 12:25
穆阿浩
101114
answered Aug 8 '17 at 12:25
穆阿浩
101114
answered Aug 8 '17 at 12:25
穆阿浩
101114
101114
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f324260%2ferror-getting-authority-error-initializing-authority-could-not-connect-resour%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
