Harald Dunkel wrote:
Hi Robert,
On 6/26/18 4:45 PM, Rob Crittenden via FreeIPA-users wrote:
Harald Dunkel wrote:
I see several files with a key_pin or Key_pin_file inside. I would prefer to send you these files in an encrypted EMail. What would you suggest? Do you have PGP?
Except for the pin the rest of the content is generally safe. My key is available in the MIT keyserver if you want to send it out of band.
I don't see anything obviously wrong. I'd try launching certmonger from a shell to see what you get:
# certmonger -d 9
rob
On 6/27/18 5:59 PM, Rob Crittenden via FreeIPA-users wrote:
I don't see anything obviously wrong. I'd try launching certmonger from a shell to see what you get:
# certmonger -d 9
certmonger works fine on the command line, AFAICT. I think this is the problem:
# systemctl status certmonger Failed to get D-Bus connection: Connection refused # systemctl status Failed to get D-Bus connection: Connection refused # ps -ef | grep -i b[u]s dbus 58 1 0 Jun23 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
Dbus is running, but it doesn't work. There is no error message on the console at boot time, but journalctl -b shows
: Jun 28 08:28:36 ipa1.example.de systemd[1]: Reached target Basic System. Jun 28 08:28:36 ipa1.example.de systemd[1]: Starting Basic System. Jun 28 08:28:36 ipa1.example.de systemd[1]: Started D-Bus System Message Bus. Jun 28 08:28:36 ipa1.example.de systemd[1]: Failed to connect to system bus: Connection refused Jun 28 08:28:36 ipa1.example.de systemd[1]: Failed to initialize D-Bus connection: Connection refused Jun 28 08:28:36 ipa1.example.de systemd[1]: Starting D-Bus System Message Bus... Jun 28 08:28:36 ipa1.example.de systemd[1]: Starting System Security Services Daemon... Jun 28 08:28:36 ipa1.example.de systemd[1]: Starting Resets System Activity Logs... Jun 28 08:28:36 ipa1.example.de systemd[1]: Started irqbalance daemon. Jun 28 08:28:36 ipa1.example.de systemd[1]: Starting irqbalance daemon... :
Maybe this is OT here?
Regards Harri
On 6/28/18 9:08 AM, Harald Dunkel wrote:
certmonger works fine on the command line, AFAICT. I think this is the problem:
# systemctl status certmonger Failed to get D-Bus connection: Connection refused # systemctl status Failed to get D-Bus connection: Connection refused # ps -ef | grep -i b[u]s dbus 58 1 0 Jun23 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
The dbus problem has been resolved by reinstalling the dbus RPMs. journalctl still shows a lot of "Connection refused" messages for dbus, see attachment.
certmonger appears to be running when started on the command line (does it?), but it cannot be started by systemd at boot time, still. Attached you will also find the output of "certmonger -d 9".
Hope this helps. Every insightful comment is highly appreciated Harri
On 6/28/18 2:19 PM, Harald Dunkel via FreeIPA-users wrote:
The dbus problem has been resolved by reinstalling the dbus RPMs. journalctl still shows a lot of "Connection refused" messages for dbus, see attachment.
certmonger appears to be running when started on the command line (does it?), but it cannot be started by systemd at boot time, still. Attached you will also find the output of "certmonger -d 9".
Hope this helps. Every insightful comment is highly appreciated Harri
Anybody to the rescue?
Regards Harri
Hi folks,
On 6/28/18 9:08 AM, Harald Dunkel via FreeIPA-users wrote:
On 6/27/18 5:59 PM, Rob Crittenden via FreeIPA-users wrote:
I don't see anything obviously wrong. I'd try launching certmonger from a shell to see what you get:
# certmonger -d 9
certmonger works fine on the command line, AFAICT. I think this is the problem:
# systemctl status certmonger Failed to get D-Bus connection: Connection refused # systemctl status Failed to get D-Bus connection: Connection refused # ps -ef | grep -i b[u]s dbus 58 1 0 Jun23 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
I found the problem. Obviously dbus started to use /run/dbus/system_bus_socket instead of /var/run/dbus/system_bus_socket, forcing everybody else to either change the path in their code (nobody did) or to establish a symlink for /var/run pointing to /run *before* the upgrade to 7.5 (nobody did, either).
Thanx for your help and support Harri
freeipa-users@lists.fedorahosted.org
-
Harald Dunkel -
Rob Crittenden