Actually, I just remembered that we do have a few tcp mode frontends. Maybe that is the reason for the error? Still, is there a way to use a default log-format for the http frontends? I'm going to try turning logs off for tcp mode frontends and see if that fixes the error.
On Mon, Oct 9, 2017 at 10:22 AM Thayne McCombs <tha...@lucidpress.com> wrote: > I am working on upgrading haproxy from 1.6 to 1.7 on our load balancers. > > However, on 1.7 with our current config I get the following error: > > [ALERT] 278/170234 (8363) : Parsing [/etc/haproxy/haproxy-staged.cfg:31]: > failed to parse log-format : format variable 'Tq' is reserved for HTTP mode. > > The log-format directive is in the *defaults* section, which also has a *mode > http* directive. Was there a change in 1.7 that made the use of Tq (and > other http specific variables) illegal in the log-format of a defaults > section? > > All of my frontends are http frontends. Is there any way I can use a > common default log-format for all of them that uses http variables (for > example, something like an http-log-format directive) in 1.7? Or do I have > to duplicate the log-format for all of my frontends? > > Thanks, > > Thayne McCombs > Lucid Software, Inc. > -- > *Thayne McCombs* > *Senior Software Engineer* > Lucid Software, Inc. > > -- *Thayne McCombs* *Senior Software Engineer* Lucid Software, Inc.
