Michele Baldessari a9c1bc3518 Lower the default stunnel log level ... Right now the default stunnel.conf log level is set at 'notice' which, when we deploy redis, fills up the logs with the following messages: May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: connect_blocking: connected 127.0.0.1:6379 May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: Service [redis] connected remote server from 127.0.0.1:60412 May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770 May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770 May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379 May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379 May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418 May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418 Those messages are from the haproxy healthceck. Let's move the default debug config to warning which will ignore the above errors. Closes-Bug: #1770180 Change-Id: I93bd0048e85864fa9e62dc38c3575ec7b48e5df5		2018-05-28 13:40:29 +02:00
..
foreground.erb	Lower the default stunnel log level	2018-05-28 13:40:29 +02:00
service.erb	Force stunnel to use TLSv1.2	2018-04-19 13:31:46 +00:00