> Le 27 juin 2019 à 09:08, Vincent Bernat a écrit :
>
> ❦ 27 juin 2019 09:06 +02, Mildis :
>
> You can workaround this by not chrooting HAProxy. The problem is that
> once chrooted, it cannot load the library. We should force libpthread to
> preload this lib.
This
❦ 27 juin 2019 09:06 +02, Mildis :
You can workaround this by not chrooting HAProxy. The problem is that
once chrooted, it cannot load the library. We should force libpthread to
preload this lib.
>>>
>>> This mailing list thread might be relevant / helpful here:
>>>
> Le 24 juin 2019 à 19:32, Vincent Bernat a écrit :
>
> ❦ 24 juin 2019 19:08 +02, Tim Düsterhus :
>
>>> You can workaround this by not chrooting HAProxy. The problem is that
>>> once chrooted, it cannot load the library. We should force libpthread to
>>> preload this lib.
>>
>> This mailing
Le 24 juin 2019 à 19:32, Vincent Bernat a écrit :
>
> ❦ 24 juin 2019 19:08 +02, Tim Düsterhus :
>
>>> You can workaround this by not chrooting HAProxy. The problem is that
>>> once chrooted, it cannot load the library. We should force libpthread to
>>> preload this lib.
>>
>> This mailing list
пн, 24 июн. 2019 г. в 22:08, Vincent Bernat :
> ❦ 24 juin 2019 18:43 +02, Mildis :
>
> > I'm hitting
> > https://www.mail-archive.com/haproxy@formilux.org/msg33189.html
> > with haproxy 2.0 on Stretch, when doing a hot-reload
> >
> > Jun 24 18:34:05 haproxy[32347]: libgcc_s.so.1 must be
On Mon, Jun 24, 2019 at 07:42:44PM +0200, William Lallemand wrote:
> On Mon, Jun 24, 2019 at 07:38:03PM +0200, Tim Düsterhus wrote:
> > Vincent,
> >
> > Am 24.06.19 um 19:32 schrieb Vincent Bernat:
> > > with 1.9.8. Do you know what could have changed?
> > >
> >
> > I can't help there. I just
On Mon, Jun 24, 2019 at 07:38:03PM +0200, Tim Düsterhus wrote:
> Vincent,
>
> Am 24.06.19 um 19:32 schrieb Vincent Bernat:
> > with 1.9.8. Do you know what could have changed?
> >
>
> I can't help there. I just remembered I read something about libgcc_s.so
> on the list before and searched my
Vincent,
Am 24.06.19 um 19:32 schrieb Vincent Bernat:
> with 1.9.8. Do you know what could have changed?
>
I can't help there. I just remembered I read something about libgcc_s.so
on the list before and searched my INBOX.
Best regards
Tim Düsterhus
❦ 24 juin 2019 19:08 +02, Tim Düsterhus :
>> You can workaround this by not chrooting HAProxy. The problem is that
>> once chrooted, it cannot load the library. We should force libpthread to
>> preload this lib.
>
> This mailing list thread might be relevant / helpful here:
>
Vincent,
Mildis,
Am 24.06.19 um 19:05 schrieb Vincent Bernat:
> You can workaround this by not chrooting HAProxy. The problem is that
> once chrooted, it cannot load the library. We should force libpthread to
> preload this lib.
>
This mailing list thread might be relevant / helpful here:
Ilya,
Am 24.06.19 um 19:02 schrieb Илья Шипицин:
> who is Vincent ? and why are you asking the list about Vincent activities ?
Vincent Bernat. One of the Debian maintainers of HAProxy. Mildis is
asking whether their issie is caused by HAProxy or by Debian's packaging.
Best regards
Tim Düsterhus
❦ 24 juin 2019 18:43 +02, Mildis :
> I'm hitting
> https://www.mail-archive.com/haproxy@formilux.org/msg33189.html
> with haproxy 2.0 on Stretch, when doing a hot-reload
>
> Jun 24 18:34:05 haproxy[32347]: libgcc_s.so.1 must be installed for
> pthread_cancel to work
> Jun 24 18:34:05
Hello,
who is Vincent ? and why are you asking the list about Vincent activities ?
пн, 24 июн. 2019 г. в 21:47, Mildis :
> Hi,
>
> I'm hitting
> https://www.mail-archive.com/haproxy@formilux.org/msg33189.html
> with haproxy 2.0 on Stretch, when doing a hot-reload
>
> Jun 24 18:34:05
Hi,
I'm hitting
https://www.mail-archive.com/haproxy@formilux.org/msg33189.html
with haproxy 2.0 on Stretch, when doing a hot-reload
Jun 24 18:34:05 haproxy[32347]: libgcc_s.so.1 must be installed for
pthread_cancel to work
Jun 24 18:34:05 haproxy[32347]: [WARNING] 174/183405 (32347) : Former
14 matches
Mail list logo
