Re: conserver exit on failed NSS lookup

On Tue, Jun 23, 2009 at 12:11:18AM +0200, Bryan Stansell wrote:
> Those two lines should be independent of themselves.  In other words,
> the first (pcitfiot05) logs an exitsbecause the command to bring up that
> console exited (with a value of 1).  The second line must be a PAM-based
> LDAP error string...and if it takes down all of conserver, I'd like to
> know.  I don't have anything in the code to actually exit, so I'm
> guessing it's the PAM library doing that.  Unless you're just assuming
> conserver is exiting because of the first line...which would be a bad
> assumption.

OK, thanks for the clarification (I did make the wrong assumption here.)

This is conserver running OK on my box:

[root@lxc1rg27 ~]# ps axuw | grep conserv
uucp     11263  0.0  1.4  74672 14780 ?        Ss   Jun22   0:00 /usr/sbin/conserver -d -L /var/log/console/__server.log
uucp     11264  0.0  0.1  50396  1532 ?        S    Jun22   0:00 /usr/sbin/conserver -d -L /var/log/console/__server.log
uucp     11266  0.0  1.4  74636 14584 ?        S    Jun22   0:00 /usr/sbin/conserver -d -L /var/log/console/__server.log
uucp     11267  0.0  0.1  50392  1544 ?        S    Jun22   0:00 /usr/sbin/conserver -d -L /var/log/console/__server.log
root     14664  0.0  0.0  61148   704 pts/0    R+   10:48   0:00 grep conserv
[root@lxc1rg27 ~]# 

After the crash/exit/whatever, there were still three threads hanging
around but the network port was closed. I'll try to reproduce the issue
with -D.

> Running in debug mode (-D) might help see things too.  Do you get any
> "CheckPass():" entries in the log file?  PAM issues should be logged

not without -D, and it's not easy to force this issue but I'll try to
get it back again.

Andras