Authorization not available. Check if polkit service is running or see debug message for more information.
-
- Posts: 32
- Joined: 2019/04/01 17:29:22
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
Do you see any resolution on my issue.
-
- Posts: 32
- Joined: 2019/04/01 17:29:22
Polkit service hasn't comeup
Hi Team,
I am unable to run polkit service on centos7 & kernel info 3.10.0-957.10.1.el7.x86_64 .
In systemctl status i could see, "Lost the name org.freedesktop.PolicyKit1 - exiting".
Please help me in finding this.
I am unable to run polkit service on centos7 & kernel info 3.10.0-957.10.1.el7.x86_64 .
In systemctl status i could see, "Lost the name org.freedesktop.PolicyKit1 - exiting".
Please help me in finding this.
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
Please don't make duplicate posts. I have merged this into the existing topic.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 32
- Joined: 2019/04/01 17:29:22
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
Sure.
Do you get chance to look at my issue.
Do you get chance to look at my issue.
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
You mention that the problem started after installing or configuring nscd.
I have seen an issue where polkit was not running and an error message that the Authorization Manager could not be started. By consequence several other services could not be started.
In our case, it turned out that this was caused by an incomplete/incorrect nis configuration. Nis had been added in /etc/nsswitch.conf. This was not a problem until named was installed. After named was installed, sealert showed messages and suggested to "setsebool -P nis_enabled 1" and this suggestion was followed. We did not see any problem immediately after setting nis_enabled in SELinux. However, after a reboot of the machine a couple of days later, we got a failing polkit.
You may have a number of error messages in /var/log/messages that relate to this issue, maybe already pre-dating the first time you got issues with polkit. Check this carefully for anything that relates to nis, ldap, dns or other things that are involved in authorization information or services provided by other hosts.
When you make changes to your system in order to solve these issues, the Authorization Manager service and by consequence polkit may not start to work properly until after you reboot the machine.
Also, note that the reboot command may fail when the Authorization Manager is not available, so you may have to power-cycle the machine in order to reboot.
I have seen an issue where polkit was not running and an error message that the Authorization Manager could not be started. By consequence several other services could not be started.
In our case, it turned out that this was caused by an incomplete/incorrect nis configuration. Nis had been added in /etc/nsswitch.conf. This was not a problem until named was installed. After named was installed, sealert showed messages and suggested to "setsebool -P nis_enabled 1" and this suggestion was followed. We did not see any problem immediately after setting nis_enabled in SELinux. However, after a reboot of the machine a couple of days later, we got a failing polkit.
You may have a number of error messages in /var/log/messages that relate to this issue, maybe already pre-dating the first time you got issues with polkit. Check this carefully for anything that relates to nis, ldap, dns or other things that are involved in authorization information or services provided by other hosts.
When you make changes to your system in order to solve these issues, the Authorization Manager service and by consequence polkit may not start to work properly until after you reboot the machine.
Also, note that the reboot command may fail when the Authorization Manager is not available, so you may have to power-cycle the machine in order to reboot.
-
- Posts: 32
- Joined: 2019/04/01 17:29:22
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
I have below logs from /var/log/messages
Apr 2 13:24:01 winbindd[7046]: [2019/04/02 13:24:01.395542, 0] ../source3/librpc/crypto/gse.c:212(gse_context_init)
Apr 2 13:24:01 winbindd[7046]: Failed to initialize kerberos context! (Included profile directory could not be read)
Apr 2 13:24:01 winbindd[7046]: [2019/04/02 13:24:01.418592, 0] ../source3/librpc/crypto/gse.c:212(gse_context_init)
Apr 2 13:24:01 winbindd[7046]: Failed to initialize kerberos context! (Included profile directory could not be read)
Apr 2 13:24:01 winbindd[7046]: [2019/04/02 13:24:01.440237, 0] ../source3/librpc/crypto/gse.c:212(gse_context_init)
Apr 2 13:24:01 winbindd[7046]: Failed to initialize kerberos context! (Included profile directory could not be read)
Apr 2 13:24:03 NetworkManager[26918]: <info> [1554236643.7809] bus-manager: could not connect to the system bus (Could not connect: No such file or directory); only the private D-Bus socket will be available
Apr 2 13:24:01 winbindd[7046]: [2019/04/02 13:24:01.395542, 0] ../source3/librpc/crypto/gse.c:212(gse_context_init)
Apr 2 13:24:01 winbindd[7046]: Failed to initialize kerberos context! (Included profile directory could not be read)
Apr 2 13:24:01 winbindd[7046]: [2019/04/02 13:24:01.418592, 0] ../source3/librpc/crypto/gse.c:212(gse_context_init)
Apr 2 13:24:01 winbindd[7046]: Failed to initialize kerberos context! (Included profile directory could not be read)
Apr 2 13:24:01 winbindd[7046]: [2019/04/02 13:24:01.440237, 0] ../source3/librpc/crypto/gse.c:212(gse_context_init)
Apr 2 13:24:01 winbindd[7046]: Failed to initialize kerberos context! (Included profile directory could not be read)
Apr 2 13:24:03 NetworkManager[26918]: <info> [1554236643.7809] bus-manager: could not connect to the system bus (Could not connect: No such file or directory); only the private D-Bus socket will be available
- Attachments
-
- org 04022019.PNG (97.73 KiB) Viewed 19487 times
-
- Posts: 32
- Joined: 2019/04/01 17:29:22
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
Hi,
Do you get chance to look into my logs.
Do you get chance to look into my logs.
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
What's the output from systemctl status dbus
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 32
- Joined: 2019/04/01 17:29:22
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
dbus is running. But i do see some failed status in brief.
Please look into attachment.
Please look into attachment.
- Attachments
-
- org 04022019.PNG (4.58 KiB) Viewed 19421 times
Re: Authorization not available. Check if polkit service is running or see debug message for more information.
Should have been systemctl status dbus -l
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke