I couldn't login to the server (totally freezed) so no logs to show.

It is a kernel problem. the server was running kernel 4.3.4-300. I had to
boot kernel 4.2.6-301 to have a functional server again.

# abrt-cli list
id 29e33b5c96e28619dca309942a505fc8e2ef19e2
reason:         BUG: unable to handle kernel NULL pointer dereference at
0000000000000060
time:           Fri 05 Feb 2016 03:35:14 PM CET
cmdline:        BOOT_IMAGE=/vmlinuz-4.3.4-300.fc23.x86_64
root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root
rhgb quiet LANG=en_US.UTF-8
count:          289
Directory:      /var/spool/abrt/oops-2016-02-05-15:35:10-1606-4
Reported:       cannot be reported

Regards,
F.

On Sat, Feb 6, 2016 at 12:32 PM, Martin Basti <mba...@redhat.com> wrote:

>
>
> On 05.02.2016 16:52, Fujisan wrote:
>
> Hello,
>
> I have a big problem here
> I have rebooted my freeipa server and noticed that no login screen
> appeared after the reboot making it impossible to log in, even through an
> ssh session from my desktop.
> I also rebooted the replica and got the same problem.
>
> I rebooted again the replica in rescue mode and tried to start freeipa
> manually:
>
> # systemctl restart ipa.service
> Error getting authority: Error initializing authority: could not connect:
> No such file or directory
> Welcome to emergency mode! After logging in, type 'journalctl -xb' to view
> system logs. ...
> Try again to boot into default mode.
> Give root password for maintenance
> (or press Control-D to continue)
>
> # systemctl status ipa.service
> ...
> ... active: Inactive (dead)
> ... Stopped Identity, Policy, Audit.
>
> freeipa version is 4.2.3-2 .
>
> What can I do to fix this?
>
> Thank you
>
> Fuji
>
>
>
> hello,
>
> can you inspect journal why system cannot be start in normal mode?
>
> without any logs we cannot help you.
>
> Martin
>
-- 
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project

Reply via email to