Oracle Linux 7: Failed to start systemd services with "Error initializing authority: Could not connect: Resource temporarily unavailable (g-io-error-quark, 27)"
(Doc ID 2432807.1)
Last updated on APRIL 12, 2024
Applies to:
Linux OS - Version Oracle Linux 7.2 and laterLinux x86-64
Symptoms
systemd services fail to start with the below error:
# systemctl restart <service-name>
Error getting authority: Error initializing authority: Could not connect: Resource temporarily unavailable (g-io-error-quark, 27)
strace shows the following output when run on the pid of the dbus-daemon:
# strace -p <pid of dbus-daemon>
1585 15:47:00.207145 accept4(3, 0x7ffef70885e0, [16], SOCK_CLOEXEC) = -1 EMFILE (Too many open files)
1585 15:47:00.207282 fcntl(-1, F_GETFD) = -1 EBADF (Bad file descriptor)
1585 15:47:00.207326 epoll_wait(4, {{EPOLLIN, {u32=3, u64=12580717580949389315}}}, 64, -1) = 1
1585 15:47:00.207356 accept4(3, 0x7ffef70885e0, [16], SOCK_CLOEXEC) = -1 EMFILE (Too many open files)
1585 15:47:00.207382 fcntl(-1, F_GETFD) = -1 EBADF (Bad file descriptor)
1585 15:47:00.207405 epoll_wait(4, {{EPOLLIN, {u32=3, u64=12580717580949389315}}}, 64, -1) = 1
The following errors are also seen in var/log/secure:
# more /var/log/secure
crond[7744]: pam_systemd(crond:session): Failed to create session: Message did not receive a reply (timeout by message bus)
crond[3892]: pam_systemd(crond:session): Failed to create session: Connection timed out
crond[10321]: pam_systemd(crond:session): Failed to connect to system bus: Resource temporarily unavailable
crond[6916]: pam_systemd(crond:session): Failed to connect to system bus: Resource temporarily unavailable
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |