On 07/04/2017 06:00 μμ, Coscend@HAProxy wrote: > Dear HAProxy Community, > > > > We are seeking your guidance with regard to the following issue we are facing > with our HAProxy use. > > > > ------ > > ISSUE > > ------- > > When we use a single monolithic config file (haproxy.cfg), HAPRoxy launches > fine > and we are able to access our products that use HTTP/TCP (WebSockets) and > RTMP. > > > > When we launch HAProxy using multiple config files in a directory, HAProxy > launches fine. However, our products do not allow administrator to login > (i.e., > locks out). We have to reset the password to login. Once the admin logs out, > again it locks out the administrator and the password has to be reset to > login. > > > > How is using multiple HAProxy config files in a directory connected to logging > in to our WebSocket product? > > > > ---- > > DETAILS > > ---- > > We are running HAProxy as a daemon service. We are using HAProxy init script > from HAProxy’s Github source. /etc/init.d/haproxy has the following lines: >
May I ask why you are using the SysVinit and not systemd to start haproxy? You are using CentOS 7.2, which uses systemd, thus my question. > > > Option 1: When using SINGLE Config FILE > > CFG=haproxy-1.7.5/conf/$BASENAME.cfg > > > > Option 2: When using a config DIRECTORY (conf.modular) with multiple files in > alphanumerical order, namely global, defaults, frontend, backend, dns resolver > and statistics: > > CFG=haproxy-1.7.5/conf.modular > > Without seeing the actual configuration, it would be quite difficult to get a useful response. Can you share a sanitized version of your configuration? Cheers, Pavlos
signature.asc
Description: OpenPGP digital signature
