DocFraggle
9100 looks like a Prometheus exporter?
yes, that’s running on there. Running on 9417 is monitoring exporter as well. No other applications though, this box is dedicated to mailcow only.
172.19.0.0/16 overlaps with your mailcow bridge interface’s network 172.22.1.0/24!
but that’s IPv4? Could it be the issue though?
$ netstat -tulpen
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name
tcp 0 0 0.0.0.0:35267 0.0.0.0:* LISTEN 0 795188870 2955120/sshd: /usr/
tcp 0 0 127.0.0.1:13306 0.0.0.0:* LISTEN 0 926973091 3301448/docker-prox
tcp 0 0 159.69.89.190:9417 0.0.0.0:* LISTEN 0 18737 1179/docker-proxy
tcp 0 0 159.69.89.190:9100 0.0.0.0:* LISTEN 0 16090 1263/docker-proxy
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 0 926977586 3303360/docker-prox
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 0 926974253 3301736/docker-prox
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 0 926974205 3301689/docker-prox
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 926979160 3303244/docker-prox
tcp 0 0 0.0.0.0:4190 0.0.0.0:* LISTEN 0 926971479 3301649/docker-prox
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 0 926972279 3301797/docker-prox
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 0 926978672 3303434/docker-prox
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 0 926971674 3301774/docker-prox
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 0 926978625 3303408/docker-prox
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 926979140 3303220/docker-prox
tcp 0 0 127.0.0.1:7654 0.0.0.0:* LISTEN 0 926970711 3300991/docker-prox
tcp 0 0 127.0.0.1:19991 0.0.0.0:* LISTEN 0 926974190 3301636/docker-prox
tcp6 0 0 :::35267 :::* LISTEN 0 795188872 2955120/sshd: /usr/
tcp6 0 0 :::587 :::* LISTEN 0 926979284 3303376/docker-prox
tcp6 0 0 :::993 :::* LISTEN 0 926972218 3301760/docker-prox
tcp6 0 0 :::995 :::* LISTEN 0 926974210 3301710/docker-prox
tcp6 0 0 :::80 :::* LISTEN 0 926978501 3303256/docker-prox
tcp6 0 0 :::4190 :::* LISTEN 0 926972185 3301671/docker-prox
tcp6 0 0 :::110 :::* LISTEN 0 926972295 3301807/docker-prox
tcp6 0 0 :::25 :::* LISTEN 0 926979342 3303444/docker-prox
tcp6 0 0 :::143 :::* LISTEN 0 926971687 3301783/docker-prox
tcp6 0 0 :::465 :::* LISTEN 0 926978648 3303422/docker-prox
tcp6 0 0 :::443 :::* LISTEN 0 926978469 3303230/docker-prox
udp 0 0 0.0.0.0:68 0.0.0.0:* 0 15482 531/dhclient
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
Using IPTables backend
Clearing all bans
Traceback (most recent call last):
File "/app/main.py", line 454, in <module>
clear()
File "/app/main.py", line 243, in clear
tables.clearIPv4Table()
File "/app/modules/IPTables.py", line 69, in clearIPv4Table
self.clearTable(iptc.Table(iptc.Table.FILTER))
File "/app/modules/IPTables.py", line 81, in clearTable
mailcow_chain.delete_rule(rule)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 1509, in delete_rule
rule.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 999, in final_check
match.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 343, in final_check
self._update_parameters()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 452, in _update_parameters
self.set_parameter(k, v)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 289, in set_parameter
return self.parse(parameter.replace("_", "-"), value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 336, in parse
self._parse(argv, inv, entry)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 605, in _parse
self._xt.parse_match(argv, inv, self._module, entry,
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 869, in new
return fn(*args)
^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 1144, in parse_match
raise XTablesError("%s: no such parameter %s" % (m.name,
iptc.errors.XTablesError: b'multiport': no such parameter b'dports'
What does this even do? It seems to be related to iptables.
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
Using IPTables backend
Clearing all bans
Traceback (most recent call last):
File "/app/main.py", line 454, in <module>
clear()
File "/app/main.py", line 243, in clear
tables.clearIPv4Table()
File "/app/modules/IPTables.py", line 69, in clearIPv4Table
self.clearTable(iptc.Table(iptc.Table.FILTER))
File "/app/modules/IPTables.py", line 81, in clearTable
mailcow_chain.delete_rule(rule)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 1509, in delete_rule
rule.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 999, in final_check
match.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 343, in final_check
self._update_parameters()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 452, in _update_parameters
self.set_parameter(k, v)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 289, in set_parameter
return self.parse(parameter.replace("_", "-"), value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 336, in parse
self._parse(argv, inv, entry)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 605, in _parse
self._xt.parse_match(argv, inv, self._module, entry,
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 869, in new
return fn(*args)
^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 1144, in parse_match
raise XTablesError("%s: no such parameter %s" % (m.name,
iptc.errors.XTablesError: b'multiport': no such parameter b'dports'
What does this even do? It seems to be related to iptables.
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
Using IPTables backend
Clearing all bans
Traceback (most recent call last):
File "/app/main.py", line 454, in <module>
clear()
File "/app/main.py", line 243, in clear
tables.clearIPv4Table()
File "/app/modules/IPTables.py", line 69, in clearIPv4Table
self.clearTable(iptc.Table(iptc.Table.FILTER))
File "/app/modules/IPTables.py", line 81, in clearTable
mailcow_chain.delete_rule(rule)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 1509, in delete_rule
rule.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 999, in final_check
match.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 343, in final_check
self._update_parameters()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 452, in _update_parameters
self.set_parameter(k, v)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 289, in set_parameter
return self.parse(parameter.replace("_", "-"), value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 336, in parse
self._parse(argv, inv, entry)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 605, in _parse
self._xt.parse_match(argv, inv, self._module, entry,
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 869, in new
return fn(*args)
^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 1144, in parse_match
raise XTablesError("%s: no such parameter %s" % (m.name,
iptc.errors.XTablesError: b'multiport': no such parameter b'dports'
What does this even do? It seems to be related to iptables.
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
Using IPTables backend
Clearing all bans
Traceback (most recent call last):
File "/app/main.py", line 454, in <module>
clear()
File "/app/main.py", line 243, in clear
tables.clearIPv4Table()
File "/app/modules/IPTables.py", line 69, in clearIPv4Table
self.clearTable(iptc.Table(iptc.Table.FILTER))
File "/app/modules/IPTables.py", line 81, in clearTable
mailcow_chain.delete_rule(rule)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 1509, in delete_rule
rule.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 999, in final_check
match.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 343, in final_check
self._update_parameters()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 452, in _update_parameters
self.set_parameter(k, v)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 289, in set_parameter
return self.parse(parameter.replace("_", "-"), value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 336, in parse
self._parse(argv, inv, entry)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 605, in _parse
self._xt.parse_match(argv, inv, self._module, entry,
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 869, in new
return fn(*args)
^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 1144, in parse_match
raise XTablesError("%s: no such parameter %s" % (m.name,
iptc.errors.XTablesError: b'multiport': no such parameter b'dports'
What does this even do? It seems to be related to iptables.
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
Using IPTables backend
Clearing all bans
Traceback (most recent call last):
File "/app/main.py", line 454, in <module>
clear()
File "/app/main.py", line 243, in clear
tables.clearIPv4Table()
File "/app/modules/IPTables.py", line 69, in clearIPv4Table
self.clearTable(iptc.Table(iptc.Table.FILTER))
File "/app/modules/IPTables.py", line 81, in clearTable
mailcow_chain.delete_rule(rule)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 1509, in delete_rule
rule.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 999, in final_check
match.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 343, in final_check
self._update_parameters()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 452, in _update_parameters
self.set_parameter(k, v)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 289, in set_parameter
return self.parse(parameter.replace("_", "-"), value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 336, in parse
self._parse(argv, inv, entry)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 605, in _parse
self._xt.parse_match(argv, inv, self._module, entry,
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 869, in new
return fn(*args)
^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 1144, in parse_match
raise XTablesError("%s: no such parameter %s" % (m.name,
iptc.errors.XTablesError: b'multiport': no such parameter b'dports'
What does this even do? It seems to be related to iptables.
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
Using IPTables backend
Clearing all bans
Traceback (most recent call last):
File "/app/main.py", line 454, in <module>
clear()
File "/app/main.py", line 243, in clear
tables.clearIPv4Table()
File "/app/modules/IPTables.py", line 69, in clearIPv4Table
self.clearTable(iptc.Table(iptc.Table.FILTER))
File "/app/modules/IPTables.py", line 81, in clearTable
mailcow_chain.delete_rule(rule)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 1509, in delete_rule
rule.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 999, in final_check
match.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 343, in final_check
self._update_parameters()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 452, in _update_parameters
self.set_parameter(k, v)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 289, in set_parameter
return self.parse(parameter.replace("_", "-"), value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 336, in parse
self._parse(argv, inv, entry)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 605, in _parse
self._xt.parse_match(argv, inv, self._module, entry,
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 869, in new
return fn(*args)
^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 1144, in parse_match
raise XTablesError("%s: no such parameter %s" % (m.name,
iptc.errors.XTablesError: b'multiport': no such parameter b'dports'
What does this even do? It seems to be related to iptables.
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
What does this even do? It seems to be related to iptables.
I found the netfilter docker container misbehaving. It is constantly crashing and reports this in the logs:
Using IPTables backend
Clearing all bans
Traceback (most recent call last):
File "/app/main.py", line 454, in <module>
clear()
File "/app/main.py", line 243, in clear
tables.clearIPv4Table()
File "/app/modules/IPTables.py", line 69, in clearIPv4Table
self.clearTable(iptc.Table(iptc.Table.FILTER))
File "/app/modules/IPTables.py", line 81, in clearTable
mailcow_chain.delete_rule(rule)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 1509, in delete_rule
rule.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 999, in final_check
match.final_check()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 343, in final_check
self._update_parameters()
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 452, in _update_parameters
self.set_parameter(k, v)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 289, in set_parameter
return self.parse(parameter.replace("_", "-"), value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 336, in parse
self._parse(argv, inv, entry)
File "/usr/lib/python3.12/site-packages/iptc/ip4tc.py", line 605, in _parse
self._xt.parse_match(argv, inv, self._module, entry,
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 869, in new
return fn(*args)
^^^^^^^^^
File "/usr/lib/python3.12/site-packages/iptc/xtables.py", line 1144, in parse_match
raise XTablesError("%s: no such parameter %s" % (m.name,
iptc.errors.XTablesError: b'multiport': no such parameter b'dports'
What does this even do? It seems to be related to iptables.