On Fri, Jan 6, 2017 at 1:38 PM, Igor Cicimov wrote:
>
>
> On Fri, Jan 6, 2017 at 12:20 AM, Patrick Hemmer
> wrote:
>
>>
>>
>> On 2017/1/5 02:15, Igor Cicimov wrote:
>>
>> Hi all,
>>
>> On one of my haproxy's I get the following message
On Fri, Jan 6, 2017 at 12:20 AM, Patrick Hemmer
wrote:
>
>
> On 2017/1/5 02:15, Igor Cicimov wrote:
>
> Hi all,
>
> On one of my haproxy's I get the following message on reload:
>
>
>[ALERT]
> 004/070949
On Fri, Jan 6, 2017 at 12:37 AM, Jeff Palmer wrote:
> Also, it'd be great if in the future you don't put an error message as
> the subject. Especially one that starts with ALERT in all caps.
>
> I'm sure I'm not the only person who just spent a moment looking over
> my
Also, it'd be great if in the future you don't put an error message as
the subject. Especially one that starts with ALERT in all caps.
I'm sure I'm not the only person who just spent a moment looking over
my monitoring dashboards to figure out what part of my network was in
alarm.
On Thu, Jan
On 2017/1/5 02:15, Igor Cicimov wrote:
> Hi all,
>
> On one of my haproxy's I get the following message on reload:
>
>
>
Hi all,
On one of my haproxy's I get the following message on reload:
[ALERT] 004/070949 (21440) : sendmsg logger #1 failed: Resource temporarily
unavailable (errno=11)
Has anyone seen this before or any pointers where to look for to correct
this?
Thanks,
Igor
6 matches
Mail list logo