Re: Issue with systemd haproxy.service on RHEL 7.4

[Badari Prasad]

Patrick, William,
 systemctl daemon-reload did the trick, initially i did copy
haproxy.service.in and repalced it with proper haproxy.service.

systemctl daemon-reload  reloaded the latest file and issue is resolved now.

Thanks
 badari

On Thu, Mar 7, 2019 at 10:45 PM William Lallemand 
wrote:

> On Thu, Mar 07, 2019 at 09:38:01PM +0530, Badari Prasad wrote:
> > Hi
> >  RHEL 7.4 comes with haproxy 1.5.18, I wanted use latest version of
> > haproxy 1.9.4.  So source code comes with haproxy.service.in [
> >
> https://github.com/haproxy/haproxy/blob/master/contrib/systemd/haproxy.service.in
> ]
> > .
> > Executing make in the dir contrib/systemd/ creates haproxy.service. I
> tried
> > to copy this generarted file in :
> /usr/lib/systemd/system/haproxy.service .
> > With this I see lots of errors :
> > #systemctl status haproxy.service
> > ● haproxy.service - HAProxy Load Balancer
> >Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled;
> > vendor preset: disabled)
> >Active: inactive (dead)
> >
> > Mar 07 03:13:47 local systemd[1]:
> > [/usr/lib/systemd/system/haproxy.service:9] Executable path is not
> > absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> > Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both ExecStart=
> and
> > ExecStop= setting. Refusing.
> > Mar 07 03:13:47 local systemd[1]:
> > [/usr/lib/systemd/system/haproxy.service:3] Failed to add dependency on
> > =syslog.target, ignoring: Invalid argument
> > Mar 07 03:13:47 local systemd[1]:
> > [/usr/lib/systemd/system/haproxy.service:7] Executable path is not
> > absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> > Mar 07 03:13:47 local systemd[1]:
> > [/usr/lib/systemd/system/haproxy.service:8] Executable path is not
> > absolute, ignoring: @SBINDIR@/haproxy -Ws -f $CONFIG -p $PIDFILE
> > Mar 07 03:13:47 local systemd[1]:
> > [/usr/lib/systemd/system/haproxy.service:9] Executable path is not
> > absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> > Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both ExecStart=
> and
> > ExecStop= setting. Refusing.
> > Mar 07 03:29:51 local systemd[1]: Unit haproxy.service cannot be reloaded
> > because it is inactive.
> > Mar 07 09:28:57 local systemd[1]: Unit haproxy.service cannot be reloaded
> > because it is inactive.
> > Mar 07 09:35:45 local systemd[1]: Unit haproxy.service cannot be reloaded
> > because it is inactive.
> >
> >
> > Have attached haproxy.service for reference. Can I get some pointers to
> > resolve this issue.
> >
> > Thanks
> >  badari
>
> Looks like you copied the haproxy.service.in instead of the
> haproxy.service generated.
>
> "@SBINDIR@" is a macro that is present in the .in but replaced in the
> .service.
>
> --
> William Lallemand
>

Re: haproxy segfault

[Willy Tarreau]

Hi Tim,

On Fri, Mar 08, 2019 at 01:43:58AM +0100, Tim Düsterhus wrote:
> Willy,
> 
> Am 16.02.19 um 06:23 schrieb Willy Tarreau:
> > On Tue, Feb 12, 2019 at 10:28:01PM +0100, Lukas Tribus wrote:
> >>> Did this bug has been introduced in 1.9.4 ?
> >>> I haven't notice this behavior before.
> >>
> >> Yes. Also see the 1.8.19 release notes.
> > 
> > I forgot we backported it to 1.9.4, I thought it was only queued after
> > 1.9.4, we should have emitted a 1.9.5 when doing 1.8.19. I'll probably
> > do one early next week. There's another issue I want to look at quickly
> 
> What's the status of HAProxy 1.9.5? "early next week" clearly has passed
> and 1.9 already has accumulated a bunch of already backported fixes and
> I guess that there are even more in dev.

I've been quite busy on other things and completely forgot this one.
I even said yesterday to Christopher (who also has some fixes pending
which still need some deeper tests) that since we don't have anything
important pending there's no rush emitting a new release :-/

I'll see if I can do one this afternoon between two other things. No
promise though.

Thanks for the reminder,
Willy

Re: haproxy segfault

[Tim Düsterhus]

Willy,

Am 16.02.19 um 06:23 schrieb Willy Tarreau:
> On Tue, Feb 12, 2019 at 10:28:01PM +0100, Lukas Tribus wrote:
>>> Did this bug has been introduced in 1.9.4 ?
>>> I haven't notice this behavior before.
>>
>> Yes. Also see the 1.8.19 release notes.
> 
> I forgot we backported it to 1.9.4, I thought it was only queued after
> 1.9.4, we should have emitted a 1.9.5 when doing 1.8.19. I'll probably
> do one early next week. There's another issue I want to look at quickly

What's the status of HAProxy 1.9.5? "early next week" clearly has passed
and 1.9 already has accumulated a bunch of already backported fixes and
I guess that there are even more in dev.

Best regards
Tim Düsterhus

Re: QAT intermittent healthcheck errors

[Marcin Deranek]

Hi,

On 3/6/19 6:36 PM, Emeric Brun wrote:

According to the documentation:

ssl-mode-async
   Adds SSL_MODE_ASYNC mode to the SSL context. This enables asynchronous TLS
   I/O operations if asynchronous capable SSL engines are used. The current
   implementation supports a maximum of 32 engines. The Openssl ASYNC API
   doesn't support moving read/write buffers and is not compliant with
   haproxy's buffer management. So the asynchronous mode is disabled on
   read/write  operations (it is only enabled during initial and reneg
   handshakes).

Asynchronous mode is disabled on the read/write operation and is only enabled 
during handshake.

It means that for the ciphering process the engine will be used in blocking 
mode (not async) which could result to
unpredictable behavior on timers because the haproxy process will sporadically 
fully blocked waiting for the engine.

To avoid this issue, you should ensure to use QAT only for the asymmetric 
computing algorithm (such as RSA DSA ECDSA).
and not for ciphering ones (AES and everything else ...)


I did explicitly enabled RSA algos:

ssl-engine qat algo RSA

and errors were gone at that point. Unfortunately all QAT activity too as

/sys/kernel/debug/qat_c6xx_\:0*/fw_counters

were reporting identical values (previously they were incrementing).

I did explicitly enforce RSA:

ssl-default-server-ciphers ECDHE-RSA-AES256-GCM-SHA384

but that did not help. Do I miss something ?
Regards,

Marcin Deranek

Re: Issue with systemd haproxy.service on RHEL 7.4

[William Lallemand]

On Thu, Mar 07, 2019 at 09:38:01PM +0530, Badari Prasad wrote:
> Hi
>  RHEL 7.4 comes with haproxy 1.5.18, I wanted use latest version of
> haproxy 1.9.4.  So source code comes with haproxy.service.in [
> https://github.com/haproxy/haproxy/blob/master/contrib/systemd/haproxy.service.in]
> .
> Executing make in the dir contrib/systemd/ creates haproxy.service. I tried
> to copy this generarted file in : /usr/lib/systemd/system/haproxy.service .
> With this I see lots of errors :
> #systemctl status haproxy.service
> ● haproxy.service - HAProxy Load Balancer
>Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled;
> vendor preset: disabled)
>Active: inactive (dead)
> 
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:9] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both ExecStart= and
> ExecStop= setting. Refusing.
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:3] Failed to add dependency on
> =syslog.target, ignoring: Invalid argument
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:7] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:8] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -Ws -f $CONFIG -p $PIDFILE
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:9] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both ExecStart= and
> ExecStop= setting. Refusing.
> Mar 07 03:29:51 local systemd[1]: Unit haproxy.service cannot be reloaded
> because it is inactive.
> Mar 07 09:28:57 local systemd[1]: Unit haproxy.service cannot be reloaded
> because it is inactive.
> Mar 07 09:35:45 local systemd[1]: Unit haproxy.service cannot be reloaded
> because it is inactive.
> 
> 
> Have attached haproxy.service for reference. Can I get some pointers to
> resolve this issue.
> 
> Thanks
>  badari

Looks like you copied the haproxy.service.in instead of the haproxy.service 
generated.

"@SBINDIR@" is a macro that is present in the .in but replaced in the .service.

-- 
William Lallemand

Re: Issue with systemd haproxy.service on RHEL 7.4

[Patrick Hemmer]

On 2019/3/7 11:08, Badari Prasad wrote:
> Hi  
>  RHEL 7.4 comes with haproxy 1.5.18, I wanted use latest version of
> haproxy 1.9.4.  So source code comes with haproxy.service.in
> 
> [https://github.com/haproxy/haproxy/blob/master/contrib/systemd/haproxy.service.in]
> .
> Executing make in the dir contrib/systemd/ creates haproxy.service. I
> tried to copy this generarted file in
> : /usr/lib/systemd/system/haproxy.service .
> With this I see lots of errors : 
> #systemctl status haproxy.service
> ● haproxy.service - HAProxy Load Balancer
>Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled;
> vendor preset: disabled)
>Active: inactive (dead)
>
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:9] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both
> ExecStart= and ExecStop= setting. Refusing.
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:3] Failed to add dependency
> on =syslog.target, ignoring: Invalid argument
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:7] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:8] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -Ws -f $CONFIG -p $PIDFILE
> Mar 07 03:13:47 local systemd[1]:
> [/usr/lib/systemd/system/haproxy.service:9] Executable path is not
> absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
> Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both
> ExecStart= and ExecStop= setting. Refusing.
> Mar 07 03:29:51 local systemd[1]: Unit haproxy.service cannot be
> reloaded because it is inactive.
> Mar 07 09:28:57 local systemd[1]: Unit haproxy.service cannot be
> reloaded because it is inactive.
> Mar 07 09:35:45 local systemd[1]: Unit haproxy.service cannot be
> reloaded because it is inactive.
>
>
> Have attached haproxy.service for reference. Can I get some pointers
> to resolve this issue.
>
> Thanks
>  badari 
>
>

Differences between the output you have provided and the attached
service file indicates that you had an earlier version of the service
file present on your system, and have not reloaded systemd since
modifying it, so it's using the old file.
You need to run: `systemctl daemon-reload`

-Patrick

Issue with systemd haproxy.service on RHEL 7.4

[Badari Prasad]

Hi
 RHEL 7.4 comes with haproxy 1.5.18, I wanted use latest version of
haproxy 1.9.4.  So source code comes with haproxy.service.in [
https://github.com/haproxy/haproxy/blob/master/contrib/systemd/haproxy.service.in]
.
Executing make in the dir contrib/systemd/ creates haproxy.service. I tried
to copy this generarted file in : /usr/lib/systemd/system/haproxy.service .
With this I see lots of errors :
#systemctl status haproxy.service
● haproxy.service - HAProxy Load Balancer
   Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled;
vendor preset: disabled)
   Active: inactive (dead)

Mar 07 03:13:47 local systemd[1]:
[/usr/lib/systemd/system/haproxy.service:9] Executable path is not
absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both ExecStart= and
ExecStop= setting. Refusing.
Mar 07 03:13:47 local systemd[1]:
[/usr/lib/systemd/system/haproxy.service:3] Failed to add dependency on
=syslog.target, ignoring: Invalid argument
Mar 07 03:13:47 local systemd[1]:
[/usr/lib/systemd/system/haproxy.service:7] Executable path is not
absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
Mar 07 03:13:47 local systemd[1]:
[/usr/lib/systemd/system/haproxy.service:8] Executable path is not
absolute, ignoring: @SBINDIR@/haproxy -Ws -f $CONFIG -p $PIDFILE
Mar 07 03:13:47 local systemd[1]:
[/usr/lib/systemd/system/haproxy.service:9] Executable path is not
absolute, ignoring: @SBINDIR@/haproxy -f $CONFIG -c -q
Mar 07 03:13:47 local systemd[1]: haproxy.service lacks both ExecStart= and
ExecStop= setting. Refusing.
Mar 07 03:29:51 local systemd[1]: Unit haproxy.service cannot be reloaded
because it is inactive.
Mar 07 09:28:57 local systemd[1]: Unit haproxy.service cannot be reloaded
because it is inactive.
Mar 07 09:35:45 local systemd[1]: Unit haproxy.service cannot be reloaded
because it is inactive.


Have attached haproxy.service for reference. Can I get some pointers to
resolve this issue.

Thanks
 badari


haproxy.service
Description: Binary data