Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
krb5 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
After having managed to have a 1024x768 lightdm screen displayed begging to login, I've tried and being prompted with "You where logged in with cached credentials".
Not really: I am logged in, but immediately thrown out again. It is impossible to work!
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.2-0ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 24 19:32:58 2016
InstallationDate: Installed on 2014-02-10 (1017 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
IpRoute:
default via 10.160.0.1 dev eth1
10.160.0.0/16 dev eth1 proto kernel scope link src 10.160.2.45
169.254.0.0/16 dev eth0 scope link metric 1000
172.18.8.0/24 dev eth0 proto kernel scope link src 172.18.8.141
IwConfig:
lo no wireless extensions.
eth1 no wireless extensions.
eth0 no wireless extensions.
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
RfKill:
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago)
ftp_proxy: http://
http_proxy: http://
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-
Kabelnetzwerkv
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
eth0 ethernet unmanaged /org/freedeskto
eth1 ethernet unmanaged /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.2.2 connected started none enabled enabled enabled enabled enabled
no_proxy: 127.0.0.1, localhost
affects: | network-manager (Ubuntu) → ubuntu |
affects: | ubuntu → krb5 (Ubuntu) |
It looks like sssd is not running (see "connection refused" error below): login:auth) : check pass; user unknown login:auth) : Request to sssd failed. Connection refused login:account) : could not identify user (from getpwnam(sct-muc))
Nov 24 19:31:08 hostname login[1686]: pam_unix(
Nov 24 19:31:08 hostname login[1686]: pam_sss(
Nov 24 19:31:08 hostname login[1686]: Libgcrypt warning: missing initialization - please fix the application
Nov 24 19:31:08 hostname login[1686]: pam_unix(
Nov 24 19:31:08 hostname login[1686]: Authentication failure
I suggest you inspect the sssd logs and try to figure out why it hasn't started properly. There are other services that failed to start, like smartd, so maybe something went really wrong with the release upgrade.