4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] logging
FromSent OnAttachments
GeoNov 20, 2004 3:05 pm 
Gordon MessmerNov 20, 2004 3:46 pm 
William HueNov 20, 2004 4:10 pm 
GeoNov 20, 2004 7:44 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] loggingActions...
From:Geo (zhin@gmail.com)
Date:Nov 20, 2004 7:44:32 pm
List:net.sourceforge.lists.courier-users

Thank you all for your help with this. As soon as I made the note in my email about syslog, I started looking deeper into that, and all your messages just confirmed that suspicion. Now I just need to get the logrotate configuration to check the maillog more frequently and rotate it if things start getting whacky.

After I do a bit more research, I'll post about the weirdness I'm seeing. So far all I know is that it is completely focused around users who setup .forward files. Under some circumstances, the mailer just starts looping on sending mail to the .forwarded account. Anyway, more on that later.

Thanks again!

- ZJ

On Sat, 20 Nov 2004 16:04:40 -0800, William Hue <will@telus.net> wrote:

Courier isn't logging directly to the logfile--it's syslogd that's doing it. After changing log files you have to send a SIGHUP to syslogd to get it to stop using the old file handle or inode.

I don't know which OS you're running, but Solaris runs /usr/lib/newsyslog from cron to rotate the logs. If /var/log/maillog isn't a standard log file then you have to edit newsyslog to rotate it, also. You'll see newsyslog signals syslogd after rotating the logs.

William

Geo wrote:

Is there a way to force the courier process(es) to stop using their current logfile and cycle to a new one? Or is this a function of the system's normal syslog mechanism? The problem is this....

I've had a couple instances where something whacked happens with courier, and the logfile (/var/log/maillog) spins wildly out of control trying to log all the crap courier is sending it. The last one I had went to 7Gig in size inside of about 3 hours. So, I stopped the courier processes, removed the logfile, and then restarted courier.

Result: courier isn't logging at all. Its almost like it holds open a handle to that particular file, and doesn't let it go until you reboot. This is further supported by the following:

1) stop courier 2) RENAME logfile 3) restart courier

Guess what: it still uses the RENAMED file as its log. Whacky.

Any insight anyone could provide would be great.

Regards, - ZJ

_______________________________________________ courier-users mailing list cour@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users