Bug#773985: tzdata: 'dpkg-reconfigure tzdata' breaks fail2ban
changing the timezone from Europe/Berlin to Etc/UTC led to fail2ban not
banning anything anymore. A bit of research showed that auth.log was still
written in the old timezone, and fail2ban detected a timestamp mismatch and
failed to work.
I did not expect that, and thus it took several days to detect this situation.
Restarting sshd, fail2ban and rsyslog fixed it, though I suspect restarting
sshd (and maybe even fail2ban) wasn't necessary.
As an unsuspecting user, I'd expect that changing the time zone via
`dpkg-reconfigure tzdata` leaves the system in a working state, or at the very
least warn that things could be broken.
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages tzdata depends on:
ii debconf [debconf-2.0] 1.5.55
tzdata recommends no packages.
tzdata suggests no packages.
-- debconf information:
* tzdata/Areas: Etc
* tzdata/Zones/Etc: UTC
* tzdata/Zones/Europe: Berlin