Users cannot login on newer kernels

(Mark Larsen) #1

Nethserver 7.5.1804
Kernel / AD user issue

I have a strange issue for some reason after a certain kernel my user can no longer login. The user is still there but password fails. If I switch back to 3.10.0-693.2.2.el7 .xi6_64 the user works fine. Now the root user works regardless of kernel version. If my server looses power then it boots. With the wrong kernel and the user does not work. I reboot and select the lower version of kernel and it works again.

I thought it was some type of corruption but restoring of data or configs has no effect. Only downgrading the kernel restores the user. I’d like to use the newest kernel but cannot figure out how to resolve this.

Any advise?

Kernel Panic: snd_hdmi_lpe_audio
(Marc) #2

Which account provider do you use?
Do you see the list of users on the server-manager?
Can you post the exact kernel version that is giving troubles?
Related errors on /var/log/messages?

Meanwhile, you can force the system to boot from a kernel of choice:

(Mark Larsen) #3

dnutan - thanks for asking;

The account provider Samba 4.7.8
Kernel: 3.10.0-862.9.1.el7.x86_64

When I try and login via SSH I get the following;
Aug 3 11:49:07 main sshd[3383]: Failed password for invalid user mlarsen from xxx.xxx.xxx.xxx port 60598 ssh2

The user is listed under users and group.

If I attempt to change the password for the user I get the following error in the gui
Error: 404 - Not found mlarsen@example.com 1322148399

If I switch back to the older kernel then all errors are gone and I can login.

(Marc) #4

Are these services running?

systemctl -l status sssd nsdc
(Mark Larsen) #5

sssd failed

systemctl -l status sssd
● sssd.service - System Security Services Daemon
Loaded: loaded (/usr/lib/systemd/system/sssd.service; enabled; vendor preset: disabled)
Active: failed (Result: timeout) since Fri 2018-08-03 13:27:14 MDT; 10min ago
Main PID: 1258 (code=exited, status=0/SUCCESS)

Aug 03 13:25:58 main.example.com sssd[be[example.com]][1388]: Starting up
Aug 03 13:26:03 main.example.com sssd[nss][1427]: Starting up
Aug 03 13:26:03 main.example.com sssd[pam][1430]: Starting up
Aug 03 13:27:14 main.example.com systemd[1]: sssd.service start operation timed out. Terminating.
Aug 03 13:27:14 main.example.com sssd[be[example.com]][1388]: Shutting down
Aug 03 13:27:14 main.example.com sssd[pam][1430]: Shutting down
Aug 03 13:27:14 main.example.com sssd[nss][1427]: Shutting down
Aug 03 13:27:14 main.example.com systemd[1]: Failed to start System Security Services Daemon.
Aug 03 13:27:14 main.example.com systemd[1]: Unit sssd.service entered failed state.
Aug 03 13:27:14 main.example.com systemd[1]: sssd.service failed.

(Marc) #6

You can try to start it manually (from command line or from the Services section at server-manager).
Any other useful error on:

journalctl -u sssd

or in /var/log/sssd/sssd_nss.log?

(Mark Larsen) #7

The service will start manually - and the user is back online.

the /var/log/sssd/sssd_nss.log shows the following;
(Fri Aug 3 12:05:02 2018) [sssd[nss]] [sss_dp_get_reply] (0x0010): The Data Provider returned an error [org.freedesktop.sssd.Error.DataProvider.Offline]
(Fri Aug 3 13:22:03 2018) [sssd[nss]] [orderly_shutdown] (0x0010): SIGTERM: killing children
(Fri Aug 3 13:26:25 2018) [sssd[nss]] [id_callback] (0x0010): The Monitor returned an error [org.freedesktop.DBus.Error.NoReply]

Looks like it is waiting for freedesktop to load - not sure what org.freedesktop.sssd is…

the sssd fails to load due to a timeout waiting for freedesktop to load.

(Mark Larsen) #8

I got to thinking about the sssd timeout waiting for freedesktop and that fact that this machine in virtual. I stopped the machine and added more startup memory and processors and now it loads with out errors or timeouts - !!!

Time will show if this is the solution.

(Mark Larsen) #9

Thanks So much for your help in troubleshooting this!!!

(Marc) #10

3 posts were split to a new topic: Kernel Panic hdmi