Login WebUI fails

[74cmonty]

Hi,
starting today I cannot login to WebUI anymore.
This is not a password authentication issue because I can switch to user "admin"
in console.

When I enter 'kinit list' as root I get this response:
kinit: general error (see e-text) for Initial credentials will be fetched.

The same error is shown for 'kinit admin'.

How can I fix this issue?

THX

[74cmonty]

Solved.
/var/log was 100% full.

[Robbie Harwood]

74cmonty  via FreeIPA-users <freeipa-users(a)lists.fedorahosted.org&gt;
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]

Hi Robbie,

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.

THX

[Robbie Harwood]

74cmonty  via FreeIPA-users <freeipa-users(a)lists.fedorahosted.org&gt;
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]

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.

[Robbie Harwood]

74cmonty  via FreeIPA-users <freeipa-users(a)lists.fedorahosted.org&gt;
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

[Robbie Harwood]

74cmonty  via FreeIPA-users <freeipa-users(a)lists.fedorahosted.org&gt;
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

[Robbie Harwood]

74cmonty  via FreeIPA-users <freeipa-users(a)lists.fedorahosted.org&gt;
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