> >> From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
> >> boun...@lists.adiscon.com] On Behalf Of singh.janmejay
> >> Sent: Friday, September 16, 2016 10:46 AM
> >> To: rsyslog-users
> >> Subject: Re: [rsyslog] Fwd: Re: rsyslog kills entire system
re or whatever problem it is.
>> CALL syslog() must not block the entire system. I know its not as
>> specified in the RFC but
>>
>>
>> Cheers
>> Raffi
>>
>>
>>
>>> Best regards,
>>> Andre Lorbach
>>>
>>>> -O
entire system. I know its not as
> specified in the RFC but
>
>
> Cheers
> Raffi
>
>
>
> > Best regards,
> > Andre Lorbach
> >
> >> -Original Message-
> >> From: rsyslog-boun...@lists.adiscon.com [mailto:rsyslog-
> >> bou
46 AM
>> To: rsyslog-users
>> Subject: Re: [rsyslog] Fwd: Re: rsyslog kills entire system => force
> reboot
>> How long does it take to go thru one cycle of verifying the problem
> exists?
>> I was wondering if bisecting would be viable?
>>
>> May not be requ
[rsyslog] Fwd: Re: rsyslog kills entire system => force
reboot
>
> How long does it take to go thru one cycle of verifying the problem
exists?
> I was wondering if bisecting would be viable?
>
> May not be required though, stats, entire config and all thread
backtrace will
> likely
How long does it take to go thru one cycle of verifying the problem exists?
I was wondering if bisecting would be viable?
May not be required though, stats, entire config and all thread backtrace
will likely give you/us enough clues.
On Sep 16, 2016 12:30 PM, "Raffael Sahli" wrote:
> yep, I can
yep, I can confirm that the problem is gone.
Downgrade back to 8.20 solved the problem.
Anybody with the same problem?
Forwarded Message
Subject: Re: [rsyslog] rsyslog kills entire system => force reboot
Date: Mon, 12 Sep 2016 11:03:58 +0200
From: Raffael Sahli
To: rsyslog@li
7 matches
Mail list logo
