public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] haproxy: Update to 2.1.4
Date: Tue, 14 Apr 2020 14:17:58 +0200	[thread overview]
Message-ID: <ef1dcc31d935a8b06c030b0648dd7955fa2ba742.camel@ipfire.org> (raw)
In-Reply-To: <20200414115415.23158-1-michael.tremer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2364 bytes --]

Hi Michael,
have updated this package too. Haproxy do not starts with this version
without changing the haproxy.cfg .

Error message was:
$ /etc/init.d/haproxy start 
Starting HAProxy...
[ALERT] 061/082845 (6269) : parsing [/etc/haproxy/haproxy.cfg:63] : 'frontend' cannot handle unexpected argument '*:5000'.
[ALERT] 061/082845 (6269) : parsing [/etc/haproxy/haproxy.cfg:63] : please use the 'bind' keyword for listening addresses.
[ALERT] 061/082845 (6269) : Error(s) found in configuration file : /etc/haproxy/haproxy.cfg
[ALERT] 061/082845 (6269) : Fatal errors found in configuration.

The solution was:

$ diff -u /etc/haproxy/haproxy.cfg.old /etc/haproxy/haproxy.cfg
--- /etc/haproxy/haproxy.cfg.old	2020-03-02 08:36:36.685904927 +0100
+++ /etc/haproxy/haproxy.cfg	2020-03-02 08:41:22.951020763 +0100
@@ -60,7 +60,8 @@
 #---------------------------------------------------------------------
 # main frontend which proxys to the backends
 #---------------------------------------------------------------------
-frontend  main *:5000
+frontend  main 
+    bind *:5000
     acl url_static       path_beg       -i /static /images /javascript /stylesheets
     acl url_static       path_end       -i .jpg .gif .png .css .js

May this is useful.

Best,

Erik


Am Dienstag, den 14.04.2020, 11:54 +0000 schrieb Michael Tremer:
> This is a security release:
>   https://www.mail-archive.com/haproxy(a)formilux.org/msg36876.html
> 
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
>  lfs/haproxy | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/lfs/haproxy b/lfs/haproxy
> index d326a090a..62a1c4d10 100644
> --- a/lfs/haproxy
> +++ b/lfs/haproxy
> @@ -24,7 +24,7 @@
>  
>  include Config
>  
> -VER        = 2.1.3
> +VER        = 2.1.4
>  
>  THISAPP    = haproxy-$(VER)
>  DL_FILE    = $(THISAPP).tar.gz
> @@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
>  DIR_APP    = $(DIR_SRC)/$(THISAPP)
>  TARGET     = $(DIR_INFO)/$(THISAPP)
>  PROG       = haproxy
> -PAK_VER    = 13
> +PAK_VER    = 14
>  
>  DEPS       =
>  
> @@ -48,7 +48,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_MD5 = bea4726d8c99f5d9bac0e62906a1f2d0
> +$(DL_FILE)_MD5 = 100cccf98aaf3ba80b5fd070866ad115
>  
>  install : $(TARGET)
>  


  reply	other threads:[~2020-04-14 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 11:54 Michael Tremer
2020-04-14 12:17 ` ummeegge [this message]
2020-04-14 12:19   ` Michael Tremer
2020-04-14 12:46     ` ummeegge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef1dcc31d935a8b06c030b0648dd7955fa2ba742.camel@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox