Skousel jsem aktualizovat fedoru 10 pres yum, pote co jsem restartoval PC, nemohu se prihlasit (ani jako root). lze to vyresit jinak nez reinstalaci?
Vetsinou lze. Chce to ale podstatne detailnejsi popis toho co jsi delal - co delas - a co na to linux.
tip: nabootuj starsi kernel - nebo nabootuj do textoveho rezimu - nebo precti si zdejsi prirucku - …
delal sem: yum update rpm
yum -y update
yum clean all
yum install preupgrade
pak mi vyskocilo: aktualni verze uz je na vasem pocitaci.
ted se mi podarilo nabootovat stary kernel, ale porad se nemuzu prihlasit. dale sem skusil nabootovat bez rhgb quiet (nic) . pak sem skusil selinux=0 (nic). Zmohl sem se ale dostat do Single Mode ale nevim co mam delat.
Prikazy, ktere pises provadi prostou aktualizaci systemu, ktera by rozhodne nemela mit na svedomi nemoznost se prihlasit. V single user modu je potreba umet ovladat prikazovy radek. Otazka ovsem je proc se nejde prihlasit. Po spusteni single user modu si pust (resp. doinstaluj) mc a podivej se do /var/log/messages na zpravy systemu z predchozich startu a hledej nejake zpravy o prihlaseni.
sem se asi spatne vyjadril. Jakoby se prihlasit muzu akorat Fedora po prihlaseni dal nenabiha. Zatim co v konsoli se prihlasit opravdu nemuzu. porad dokolacka zadavam localhost login a passworld. Omlouvam se!
V kazdem pripade se musis dostat k tem logum a precist z nich, kde je problem.
Mamm pocit, ze budes mit nacutle Gnome(Kde, …) konfiguracni soubory.
Nejjednodussi bude se prihlasit do prikazove radky a bud zalozit novy ucet nebo smazat gnome konfiguraky, aby si je vytvoril znovu.
no doufam ze je to ono: Jul 16 15:17:33 localhost nm-dispatcher.action: Error in get_property: Message did not receive a reply (timeout by message bus)
Jul 16 15:17:34 localhost nm-system-settings: disconnected from the system bus, exiting.
Jul 16 15:17:34 localhost nm-dispatcher.action: Disconnected from the system bus, exiting.
Jul 16 15:17:34 localhost rpc.statd[1889]: Caught signal 15, un-registering and exiting.
Jul 16 15:17:34 localhost rpcbind: rpcbind terminating on signal. Restart with “rpcbind -w”
Jul 16 15:17:35 localhost auditd[1831]: The audit daemon is exiting.
Jul 16 15:17:35 localhost kernel: audit(1247746655.083:12): audit_pid=0 old=1831 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1
Jul 16 15:17:35 localhost kernel: Kernel logging (proc) stopped.
nebo mam poslat cely vypis??
slune napsal(a):
Mamm pocit, ze budes mit nacutle Gnome(Kde,
…) konfiguracni soubory.
Nejjednodussi bude se prihlasit do prikazove radky
a bud zalozit novy ucet nebo smazat gnome
konfiguraky, aby si je vytvoril znovu.
no jestli muzete popiste co bych mel delat Step By Step v tomhle sem “Like Virgin”. diky
No to nevypada jako ono. To je spise kousek logu o vypinani pocitace. Podivej se na hodinky, zkus se prihlasit a pak hledej v logu ten cas ±.
jedine co se ± priblizuje, je tohle:
Jul 17 00:44:39 localhost NetworkManager: (wlan0): supplicant interface state: starting -> ready
Jul 17 00:45:16 localhost init: tty4 main process (2216) killed by TERM signal
Jul 17 00:45:16 localhost init: tty5 main process (2217) killed by TERM signal
Jul 17 00:45:16 localhost init: tty2 main process (2218) killed by TERM signal
Jul 17 00:45:16 localhost init: tty3 main process (2219) killed by TERM signal
Jul 17 00:45:16 localhost init: tty6 main process (2220) killed by TERM signal
a zpredcoziho dne
I tohle nic nerika. Jsou tam i jine logy, securetty, Xorg, dmesg … prohledni vsechny a posli toho treba vice.
neco od secure…:
Jul 17 00:44:49 localhost gdm-session-worker[2401]: PAM (gdm) no module name supplied
Jul 17 00:45:00 localhost gdm-session-worker[2401]: gnome-keyring-daemon: couldn’t lookup keyring component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn’t lookup ssh component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)gnome-keyring-daemon: couldn’t lookup pkcs11 component setting: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Not running within active session)
Jul 17 00:45:00 localhost gdm-session-worker[2401]: pam_unix(gdm:session): session opened for user dacko by (uid=0)
Jul 17 00:45:00 localhost gdm-session-worker[2401]: pam_unix(gdm:session): session opened for user dacko by (uid=0)
Jul 17 00:45:16 localhost sshd[2134]: Received signal 15; terminating.
rsyslogd: [origin software=“rsyslogd” swVersion=“3.21.10” x-pid=“1863” x-info=“http://www.rsyslog.com”] exiting on signal 15.
neco od audit.log: type=DAEMON_START msg=audit(1247780657.804:1573): auditd start, ver=1.7.13 format=raw kernel=2.6.27.25-170.2.72.fc10.i686 auid=4294967295 pid=1837 subj=system_u:system_r:auditd_t:s0 res=success
type=CONFIG_CHANGE msg=audit(1247780657.938:3): audit_backlog_limit=320 old=64 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditctl_t:s0 res=1
type=USER_AUTH msg=audit(1247780700.550:4): user pid=2401 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg=‘op=PAM:authentication acct=“dacko” exe="/usr/libexec/gdm-session-worker" (hostname=?, addr=?, terminal=:0 res=success)’
type=USER_ACCT msg=audit(1247780700.555:5): user pid=2401 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg=‘op=PAM:accounting acct=“dacko” exe="/usr/libexec/gdm-session-worker" (hostname=?, addr=?, terminal=:0 res=success)’
type=CRED_ACQ msg=audit(1247780700.560:6): user pid=2401 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg=‘op=PAM:setcred acct=“dacko” exe="/usr/libexec/gdm-session-worker" (hostname=?, addr=?, terminal=:0 res=success)’
type=LOGIN msg=audit(1247780700.658:7): login pid=2401 uid=0 old auid=4294967295 new auid=500 old ses=4294967295 new ses=1
type=USER_ROLE_CHANGE msg=audit(1247780700.722:8): user pid=2401 uid=0 auid=500 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg=‘pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0 selected-context=unconfined_u:unconfined_r:unconfined_t:s0: exe="/usr/libexec/gdm-session-worker" (hostname=?, addr=?, terminal=? res=success)’
type=USER_START msg=audit(1247780700.977:9): user pid=2401 uid=0 auid=500 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg=‘op=PAM:session_open acct=“dacko” exe="/usr/libexec/gdm-session-worker" (hostname=?, addr=?, terminal=:0 res=failed)’
type=USER_LOGIN msg=audit(1247780700.978:10): user pid=2401 uid=0 auid=500 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg=‘uid=500: exe="/usr/libexec/gdm-session-worker" (hostname=?, addr=?, terminal=/dev/tty1 res=failed)’
type=CRED_DISP msg=audit(1247780700.978:11): user pid=2401 uid=0 auid=500 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg=‘op=PAM:setcred acct=“dacko” exe="/usr/libexec/gdm-session-worker" (hostname=?, addr=?, terminal=:0 res=success)’
type=DAEMON_END msg=audit(1247780718.265:1574): auditd normal halt, sending auid=0 pid=2557 subj=system_u:system_r:initrc_t:s0 res=success
ad secure: prvni dva zaznamy v logu nemam - netusim co presne to je a zda to vadi. Dale se 00:45:00 behem jedne sekundy dvakrat prihlasis - zda se OK, ale divne, pak v 00:45:16 vypinas pocitac ??
ad audit: vetsinou je to success - tedy overeni hesla asi projde, ale user_start a user_login failed… tezko rict proc.
Doporucuji zkusit to, co radilo drive slune: tedy vse ze sveho home adresare docasne presun(zazalohuj) jinam, aby to nemohla ovlivnit nejaka poskozena konfigurace.
Dalsi tipy: zkontrolovat konzistenci nainstalovanych programu: rpm -Va ; package-cleanup --problems, apod…
Zkusit system updatovat…Zachranne prace jsou popsany v prirucce.
Tohle je problém:
Jul 17 00:44:49 localhost gdm-session-worker[2401]: PAM (gdm) no module name supplied
Znamená to, že je poškozena konfigurace PAM pro GDM (a možná nejen pro něj). Dokud není načten nějaký konfigurační soubor, nelze posoudit, jestli nejsou poškozené moduly.
Ověř, že je GDM a PAM v pořádku:
rpm -V gdm pam
a ukaž nám verze
rpm -q gdm pam
Otestuj pro jistotu i stav passwd/shadow:
pwck -r
Tu kontrolu všech balíků udělat samozřejmě můžeš. Ty předchozí příkazy dělají v podstatě totéž, ale jsou směrovány na pravděpodobnou příčinu.
rpm -V gdm pam
.M…G. /var/log/gdm
.M… /var/run/gdm
…L… c /etc/pam.d/system-auth
S.5…T c /etc/security/limits.conf
rpm -q gdm pam
gdm -2.24.1 -4.fc10.3.i386
pam -1.0.4 -4.fc10.i386
pwck -r
user adm: file /var/adm no exist
user uucp: file /var/spool/uucp no exist
user gopher: file /var/gopher no exist
user ftp: file /var/ftp no exist
user avahi -autoipd: file /var/lib/avahi -autoipd no exist
user pulse: file /var/run/pulse no exist
pwck: bez zmen
To vypada v poradku. az na tu verzi gdm.
Zadej “rpm -qi gdm”
Name: gdm
Version:2.24.1
Release:4.fc10.3
Install Date:th, 20-Jun-2009 16:42:34 +0300
Group: User Interface/X
Source RPM: gdm- 2.24.1-4.fc10.3.src.rpm
Size:3436374
License: GPLv2+
Signature: DSA/SHA1.su. 12-Jun-2009 23:52:11 +0300 Key ID 371a3b264dd65180
URL: http // download.gnome.org/sources/gdm
Summary: Manager GNOME
To vypsalo jenom tohle? Zadny Vendor, Build host, atd. Nevypada to na balik od fedory :((. Premyslej, kde se to tam vzalo, nahrad to spravnym balikem. A podivej se neni-li tam takovych podivnosti vic. Jake mas zapnute repozitare?