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

Re: Can't login, won't ask for password



I got bit by this one, too. Here's how I went diagnosing it:

## to get list of recent changed logs
# ls -ltr /var/log/

## auth.log is listed at the bottom, let's check it out
# tail -100 /var/log/auth.log

## whoa! what's this?!
Jun 26 10:36:33 caligula login[8484]: PAM unable to
dlopen(/lib/security/pam_unix.so)
Jun 26 10:36:33 caligula login[8484]: PAM [dlerror:
/lib/security/pam_unix.so: undefined symbol: sgaddset]
Jun 26 10:36:33 caligula login[8484]: PAM adding faulty module:
/lib/security/pam_unix.so
Jun 26 10:36:36 caligula login[8484]: FAILED LOGIN (1) on `tty1' FOR
`root', Module is unknown

## get the source
# apt-get build-dep pam
# apt-get install libcap-dev  # for some reason 'build-dep' missed this
# apt-get -b source pam

## ok so it builds and the reinstall is still broken of course.
## put 2 and 2 together and get 4
# cd pam-0.72/build-tree/Linux-PAM-0.72/modules/pam_unix
# grep sgaddset *
support.c:    sgaddset(&sigset, SIGCHLD);

## HRM... that looks like a Type-o to me. so I made the following patch.
-------<038_sigCHLD_fix.diff>---------
--- Linux-PAM-0.72/modules/pam_unix/support.c   Tue Jun 26 10:30:12 2001
+++ Linux-PAM-0.72.new/modules/pam_unix/support.c       Tue Jun 26 10:54:43
2001
@@ -386,7 +386,7 @@
 
     /* Block SIGCHLD */
     sigemptyset(&sigset);
-    sgaddset(&sigset, SIGCHLD);
+    sigaddset(&sigset, SIGCHLD);
     sigprocmask(SIG_BLOCK, &sigset, 0);
 
     /* fork */
----------</038_sigCHLD_fix.diff>---------

# cp 038_sigCHLD_fix.diff pam-0.72/debian/patches
# cd pam-0.72
# debian/rules clean
# debian/rules binary
# cd ..
# dpkg -i libpam-cracklib_0.72-26_i386.deb libpam-modules_0.72-26_i386.deb
libpam-runtime_0.72-26_i386.deb libpam0g_0.72-26_i386.deb


I realize this is more info than you wanted, but I thought it might help
you in the future about how to go about diagnosing a problem. Of course,
this all happened because I didn't think about looking at incoming! :-)

-s



Reply to: