Re: System crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Cliff
usually an update crash suggests there is a package that removed a library,
overwrote a config file, or generally messed something up. I would
investigate what the 'update' did with a rpm -qa --last | more  and see
what packages were in the update. Review what those rpms did in hopes one
points to doing something with your X client or your pam auth.

You said you can TTY, do you mean ssh? If you ssh into the box it creates
an authorization key which sets that user up to be recognized again. That
should help with authentication issues. Also, has anything changed with
your X client on your desktop? I log into many other machines to work with
a java gui that requires Xming. If I just putty to the machine, the default
doesn't have X11 forwarding turned on and then the gui won't come up. I
have since gone and made the default always have this on.

And what do your /var/log/messages and secure logs say? Any hints to what
is not launching or working?

Phebe Mertes
Lotus Notes sucks

                                                                                               
  From:       Cliff <c4ifford@xxxxxxxxx>                                                       
                                                                                               
  To:         General Red Hat Linux discussion list <redhat-list@xxxxxxxxxx>                   
                                                                                               
  Date:       02/25/2010 07:51 AM                                                              
                                                                                               
  Subject:    Re: System crash                                                                 
                                                                                               
  Sent by:    redhat-list-bounces@xxxxxxxxxx                                                   
                                                                                               





I tried doing a reinstall to no avail though

Sent from my iPhone

On Feb 24, 2010, at 11:12 PM, Barry Brimer <lists@xxxxxxxxxx> wrote:

> Backup your current /etc/pam.d directory, and use rpm to reinstall
> your pam.  If needed boot into rescue mode, and then try.  You might
> need to use the --replacepkgs option in rpm .. and in this case
> using --repackage couldn't hurt either.
>
> On Wed, 24 Feb 2010, Cliff wrote:
>
>> It's a Pam issue I'm pretty sure I just don't know how to fix it
>>
>> Sent from my iPhone
>>
>> On Feb 24, 2010, at 7:37 PM, mark <m.roth@xxxxxxxxx> wrote:
>>
>>> cliff here wrote:
>>>> I apologize this is more of a Fedora questions, but I just had a
>>>> machine
>>>> crash during an update, and on reboot I find I can't log into X,
>>>> I check my
>>>> /var/log/secure and I get an statement about my X login
>>>> User not know to the underlying authentication module
>>>> but I can login to the TTY, any expedited hel[ would be greatly
>>>> appreciated.
>>> Sounds like the update updated the video driver, and you need to
>>> redo the X setup.
>>>   mark

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

-- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list

[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux