HEALTHCHECK invokes Z-line flood protection

[oogali]

In the current image published to Docker Hub, the HEALTHCHECK command is creating a TCP connection to check if the IRC server is running.

However, the repeated connections are being flagged as a flooding client.

(I added to extra blank lines between messages, in an attempt to chronologically group them togeter)

ircd_1  | Fri Jul 28 02:26:13 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to expire on Fri Jul 28 02:36:13 2017: Connect flooding
ircd_1  | Fri Jul 28 02:26:13 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 02:36:15 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 602 seconds ago)

ircd_1  | Fri Jul 28 02:40:46 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to 
expire on Fri Jul 28 02:50:46 2017: Connect flooding
ircd_1  | Fri Jul 28 02:40:46 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 02:50:47 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 601 seconds ago)

ircd_1  | Fri Jul 28 02:55:18 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to expire on Fri Jul 28 03:05:18 2017: Connect flooding
ircd_1  | Fri Jul 28 02:55:18 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 03:05:19 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 601 seconds ago)

ircd_1  | Fri Jul 28 03:09:50 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to expire on Fri Jul 28 03:19:50 2017: Connect flooding
ircd_1  | Fri Jul 28 03:09:50 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 03:19:51 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 601 seconds ago)

ircd_1  | Fri Jul 28 03:24:22 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to expire on Fri Jul 28 03:34:22 2017: Connect flooding
ircd_1  | Fri Jul 28 03:24:22 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 03:34:23 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 601 seconds ago)

ircd_1  | Fri Jul 28 03:38:54 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to expire on Fri Jul 28 03:48:54 2017: Connect flooding
ircd_1  | Fri Jul 28 03:38:54 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 03:48:55 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 601 seconds ago)

ircd_1  | Fri Jul 28 03:53:26 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to expire on Fri Jul 28 04:03:26 2017: Connect flooding
ircd_1  | Fri Jul 28 03:53:26 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 04:03:28 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 602 seconds ago)

ircd_1  | Fri Jul 28 04:07:59 2017: XLINE: Module m_connectban added Z:line on *@127.0.0.1/32 to expire on Fri Jul 28 04:17:59 2017: Connect flooding
ircd_1  | Fri Jul 28 04:07:59 2017: ANNOUNCEMENT: Connect flooding from IP range 127.0.0.1/32 (10)

ircd_1  | Fri Jul 28 04:18:00 2017: XLINE: Removing expired Z-Line 127.0.0.1/32 (set by irc.myserver.com 601 seconds ago)

[SISheogorath]

You can eline *@127.0.0.1 as a fix. That's what we change in #67, too. Should resolve the problem since elined IPs are not banned by the module.