74cmonty via FreeIPA-users freeipa-users@lists.fedorahosted.org writes:

Solved. /var/log was 100% full.

I'm glad to hear it's solved! However, /var/log filling up shouldn't fail authentication (and definitely not with *that* error message). Do you mind filing a bug report?

Thanks, --Robbie

74cmonty via FreeIPA-users freeipa-users@lists.fedorahosted.org writes:

let me share some additional information on this issue before filing a bug.

I checked the log files for errors but didn't detect anything. Then I verified if any service was failing, but everything was running.

After this I tried to restart ipa.service and this failed with an error message that pointed to /var/log. I must admit that I cannot recall the error message in detail, but it was saying something like "cannot write...".

Further investigation showed that file /var/log/dirsrv/slapd-BISZUMBITTERENEN-DE/errors was very large. After ensuring that related service is not running I compressed this file and restarted the service. After this I could start ipa.service and everything is working again.

Ah, it sounds like 389 failing to start because it couldn't write its logfile is the original cause. I guess that's where the bug should be targeted.

Thanks, --Robbie

74cmonty via FreeIPA-users freeipa-users@lists.fedorahosted.org writes:

Do you recommend to file a bug? Can you share some instructions how to do this? I'm not familiar with the process on Fedora.

Fedora uses Red Hat's bugzilla: https://bugzilla.redhat.com/

IPA upstream uses Fedora's pagure: https://pagure.io/freeipa/

Thanks, --Robbie

74cmonty via FreeIPA-users freeipa-users@lists.fedorahosted.org writes:

let me share some additional information on this issue before filing a bug.

I checked the log files for errors but didn't detect anything. Then I verified if any service was failing, but everything was running.

After this I tried to restart ipa.service and this failed with an error message that pointed to /var/log. I must admit that I cannot recall the error message in detail, but it was saying something like "cannot write...".

Further investigation showed that file /var/log/dirsrv/slapd-BISZUMBITTERENEN-DE/errors was very large. After ensuring that related service is not running I compressed this file and restarted the service. After this I could start ipa.service and everything is working again.

Ah, it sounds like 389 failing to start because it couldn't write its logfile is the original cause. I guess that's where the bug should be targeted.

Thanks, --Robbie