|
From: Dominic R. <dl...@ed...> - 2009-10-23 12:52:52
|
Heiko Zuerker wrote:
> Quoting Dominic Raferd <dl...@ed...>:
>> 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?)
>>
> 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.
Sorry I wrote that quite early in the morning. Now I look more closely
at what I posted I see that the login was on Oct 20; my attempted logins
on Oct 22 don't appear in /var/log/messages at all, in fact *nothing*
appears there since Oct 21 04:41 ('-- MARK --') - until I rebooted Oct
22 19:09. It looks as if my cron jobs had stopped working in the
intervening period, as had syslog-ng. Apache and Samba were definitely
still working through this period (Postfix I don't know).
|