fail2ban expands the host placeholder into a named capture group, so a pattern naming it twice is a duplicate group name: the daemon refuses its whole configuration and exits, and the machine keeps no bans at all, for every jail rather than the one at fault. That happened live on the control node the day the jails shipped, and cost fail2ban on both servers for about ten minutes.
The manifest check refuses it at merge time with what it would cost. A jail with no name, no pattern, or a name another of the same module's jails took is refused too. Tests in internal/catalogue/jail_problems_test.go.
fail2ban expands the host placeholder into a named capture group, so a pattern naming it twice is a duplicate group name: the daemon refuses its whole configuration and exits, and the machine keeps no bans at all, for every jail rather than the one at fault. That happened live on the control node the day the jails shipped, and cost fail2ban on both servers for about ten minutes.
The manifest check refuses it at merge time with what it would cost. A jail with no name, no pattern, or a name another of the same module's jails took is refused too. Tests in `internal/catalogue/jail_problems_test.go`.
fail2ban expands <HOST> into a named capture group, so a pattern naming it twice is a duplicate
group name: the daemon refuses its whole configuration and exits, and the machine keeps no bans at
all — for every jail, not the one at fault. Hit live on the control node the day the jails shipped.
A jail with no name, no pattern, or a name another of the module's jails took is refused too.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
fail2ban expands the host placeholder into a named capture group, so a pattern naming it twice is a duplicate group name: the daemon refuses its whole configuration and exits, and the machine keeps no bans at all, for every jail rather than the one at fault. That happened live on the control node the day the jails shipped, and cost fail2ban on both servers for about ten minutes.
The manifest check refuses it at merge time with what it would cost. A jail with no name, no pattern, or a name another of the same module's jails took is refused too. Tests in
internal/catalogue/jail_problems_test.go.