Bug 291609

Summary:	cron + mailer + syslog-ng-2.1.4 locks up logins
Product:	Gentoo Linux	Reporter:	Karlis.Repsons
Component:	Current packages	Assignee:	Mr. Bones. (RETIRED) <mr_bones_>
Status:	RESOLVED INVALID
Severity:	normal	CC:	jer
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Karlis.Repsons 2009-11-02 17:36:27 UTC

After complaining in bug 291367, where I documented how I cannot do any kinds of logins, there appears to have emerged some solution for it - unmerging sys-process/dcron-3.2! I must say, it was emerged additionally after upgrade and there were many sendmail programs stuck in ps -ef list, so I found out. 
Its dcron+ssmtp what triggered the problem with logins. When dcron tried to deliver output of its cronjobs, things ended as bad as that!

This is what was in ssmtp.conf of mail-mta/ssmtp-2.62-r6:
root= #Kar...sons@gmail.com
mailhub=smtp.googlemail.com:587
rewriteDomain=
hostname=smtp.gmail.com:587
UseSTARTTLS=YES
AuthUser=Kar...sons@gmail.com
AuthPass=juje435jd
FromLineOverride=YES # optional

in /etc/crontab there was by default MAILTO, but dcron ignored it, so I deleted it.

in /etc/mail/aliases nothing is set for root.

Given it caused consequences as bad as in my case, maybe there is something to look at?

Reproducible: Always

Steps to Reproduce:
1.emerge dcron ssmtp
2.set up some verbose cornjob and run it
3. wait until cronjob is executed
4.try doing some kind of login or su!

Actual Results:  
login blockade

Expected Results:  
whatever error for dcron / ssmtp, but not logins lockup!

Comment 1 Karlis.Repsons 2009-11-03 10:06:58 UTC

Silly, this moves on still. vixie-cron and Postfix did the same, but all the login blocker was resolved by killing syslong-ng. Now with syslog-ng-3.0 problems vanish.

So, somehow cron+mailer+syslog-ng-2.1.4 locks up logins etc. syslog-ng-3.0 resolves it. At least, maybe some googler finds that useful...

Comment 2 Jeroen Roovers (RETIRED) gentoo-dev

2009-11-11 17:14:58 UTC

Good thing syslog-ng 3 is being stabilised then. Maybe it's the installation of a newer eventlog before syslog-ng, or vice versa, that is causing this?

Comment 3 Mr. Bones. (RETIRED) gentoo-dev

2009-11-12 21:00:55 UTC

So far it sounds like user error to me.

Please attach /etc/syslog-ng/syslog-ng.conf as text/plain

Comment 4 Mr. Bones. (RETIRED) gentoo-dev

2009-12-22 04:05:03 UTC

No reply and it seems invalid to me.  Reopen if you can offer more information.