Am 2.8.2007 schrieb "Henrik Krohns" <[EMAIL PROTECTED]>:

>On Thu, Aug 02, 2007 at 11:02:26AM +0300, Henrik Krohns wrote:
>> On Thu, Aug 02, 2007 at 09:24:22AM +0200, Robert Felber wrote:
>> > On Mon, Jul 30, 2007 at 06:42:12PM +0200, Thomas Krieger wrote:
>> > > > > I hope this will help to find the cause of the problem.
>> > > >
>> > > > Unfortunately not. It doesn't tell why the children received
>> > > > SIGPIPE. It doesn't appear to be reproduceable either.
>> > >
>> > > Ok, I searched the logfiles for policyd warnings. I did on 27th and 
>> > > 28th, the
>> > > day of the crash. Please find attached the output as gz file. But I do 
>> > > not
>> > > find any master messages in the file. But there are a view messages
>> > > concerning syslog and the crash happend during log rotation on the 
>> > > productive
>> > > server.
>> > >
>> > > Testing on my test server killing a child with SIGPIPE does not kill the
>> > > master. Everything goes on fine. Strange problem I think. I will 
>> > > investigate
>> > > this further on.
>> > >
>> >
>> > The master die()d because Sys::Syslog throw a die() when the
>> > master attempted to use syslog().
>> >
>> > This appears to be a race condition when syslog is not available
>> > for log-message submission.
>> >
>> > I am afraid I cannot resolve this cleanly.
>>
>> Postgrey had the same problem, simple fix. Upgrade Sys::Syslog.
>>
>> http://lists.ee.ethz.ch/postgrey/msg01815.html
>
>.. and policyd-weight needs to add nofatal to openlog call too.

Well the Sys::Syslog in Debian Sarge is quit old. It's perl 5.8.4 and
the Sys::Syslog version is 0.05 I think.

I will update to the newest version of Sys::Syslog.

Robert will you change the openlog accordingly?

Regards

Thomas

____________________________________________________________
Policyd-weight Mailinglist - http://www.policyd-weight.org/

Reply via email to