Hi
We used the yum GUI to upgrade one of our servers yesterday and forgot about
it,
This morning YUM GUI still showed that the server was being updated,
We saw a yum.pid Running, we assumed it was frozen and killed the YUM
Process, removed the pid file from subsys and..
Unleashed hell... several cced processess started banging the server (6-7),
had to kill them
By hand, afterward there was no pam authentication on the whole server.
We did Brian's post(below) of an older post to reinstall PAM again.
(Remember to restore yum exclusions).
Rebooted and athentication worked, However customers that just begun using
SMTP AUTH had to remove this feature because it is no longer working.
We though it might be sendmail.cf related but wanted to ask first.
The YUM updates (2 updates)... We don't know if they were pam Related, but
it was after the major Dovecot Update which worked fine Thanks HISAO!.
Another thing that came to our mind was the fact that we made tmp on to "rw"
That might have caused the problem.
Any pointer on how should we chance sendmail.mc or sendmail.cf to restore
SMTP-AUTH
Would be greatly appreciated.
BY the way Sendmail does seem to have it configured because we did a Telnet
to port 25
And did
AUTH CRAM-MD5
And the server answers correctly
Also
AUTH LOGIN answers a HASH
So the feature seems to be IN Place, Outlook times out when trying to use
it.
Regards
Rodrigo O
Xnet / Pwworks
-----Original Message-----
From: Brian N. Smith [mailto:brian (at mark) nuonce.net]
Sent: Martes, 05 de Septiembre de 2006 10:45 p.m.
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:06767] Re: Yum Update broke my system. need help
>I did a YUM update just now and after rebooting my system is no longer
>authenticating users. Apache wont start etc...
Do this line by line, and you should be fine.
rpm -e --nodeps pam
cd /etc/yum.repos.d
rm -f CentOS-Base.repo
wget http://www.nuonce.net/bq/CentOS-Base.repo
yum install pam
Now, look at the following files;
cat /etc/pwdb.conf
#
# This is the configuration file for the pwdb library #
user:
unix+shadow
unixdb+shadowdb
unix
group:
unix+shadow
unixdb+shadowdb
unix
If it doesn't look like that, make it look like that. Then look at this
file
cat /etc/nsswitch.conf
Look for these three lines:
passwd: db files
shadow: db files
group: db files
If they do not have "db" before the "files", add them.
Once you do that, Pam will function just fine then!
Thanks,
Brian N. Smith
NuOnce Networks, Inc.