|
From: Heiko Z. <he...@zu...> - 2009-10-23 11:55:00
|
Quoting Dominic Raferd <dl...@ed...>: > Serge Leschinsky wrote: >> Please check syslog-ng options. Below the message I sent to the >> list some time ago: >> >> ---------------------------------------------- >> I'm still not sure, but it seems to be correlated: if syslog-ng >> starts before an >> attempt to login (ssh or console - it doesn't matter) the login process is >> getting stuck. >> >> As a workaround you can add "--no-caps" to the daemon parameters. >> >> ---------------------------------------------- >> >> I thought the issue went away after syslog-ng update.... > My inability to login did not occur immediately but only after DL had > been running for some days or weeks. My /var/log/messages shows things like: > > Oct 20 16:04:55 src@me login[8918]: pam_unix(login:session): session > opened for user root by LOGIN(uid=0) > Oct 20 16:04:55 src@me login[12927]: ROOT LOGIN on 'tty1' > Oct 20 16:07:31 src@me login[8918]: pam_unix(login:session): session > closed for user root > > The last line is me doing CTRL+C, I think. So it looks to me as if login > proceeded okay; I guess it is whatever daemon responds to a login (after > a login has succeeded) that is failing (agetty?) > > But I am trying your workaround, thanks Serge - definitely one I would > never have thought of! This is weird. I have my servers running for weeks with the grsec version of DL and never experienced this issue. I'll compiling a new server version when I get a chance, so you can test a newer release. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |