{"action":"created","issue":{"url":"https://api.github.com/repos/fail2ban/fail2ban/issues/1011","labels_url":"https://api.github.com/repos/fail2ban/fail2ban/issues/1011/labels{/name}","comments_url":"https://api.github.com/repos/fail2ban/fail2ban/issues/1011/comments","events_url":"https://api.github.com/repos/fail2ban/fail2ban/issues/1011/events","html_url":"https://github.com/fail2ban/fail2ban/issues/1011","id":66142325,"number":1011,"title":"fail2ban ignores action.d config after server reboot","user":{"login":"thomaszbz","id":11200727,"avatar_url":"https://avatars.githubusercontent.com/u/11200727?v=3","gravatar_id":"","url":"https://api.github.com/users/thomaszbz","html_url":"https://github.com/thomaszbz","followers_url":"https://api.github.com/users/thomaszbz/followers","following_url":"https://api.github.com/users/thomaszbz/following{/other_user}","gists_url":"https://api.github.com/users/thomaszbz/gists{/gist_id}","starred_url":"https://api.github.com/users/thomaszbz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thomaszbz/subscriptions","organizations_url":"https://api.github.com/users/thomaszbz/orgs","repos_url":"https://api.github.com/users/thomaszbz/repos","events_url":"https://api.github.com/users/thomaszbz/events{/privacy}","received_events_url":"https://api.github.com/users/thomaszbz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-04-03T12:58:57Z","updated_at":"2015-04-07T11:27:55Z","closed_at":null,"body":"I have applied the changes of  #1006 on my server and set\r\n\r\n    #_whois_command = %(_whois)s\r\n    _whois_command = %(_whois_convert_charset)s\r\n\r\nin the mail-whois-common.conf (or mail-whois-common.local alternatively).\r\n\r\nThat worked fine until I performed a server reboot.\r\n\r\nHow to reproduce\r\n\r\n- Apply changes from #1006 and use _whois_convert_charset\r\n- reboot server\r\n- let fail2ban ban some ip which contains non-ascii/non-utf-8 characters, like 179.111.212.221\r\n\r\nResult: I get an attachment in the email again, which should be avoided via #1006 config\r\n\r\nThen comes the strange part:\r\n\r\n- restart fail2ban with service fail2ban restart\r\n- let fail2ban ban the same ip again\r\n\r\nResult: All is fine and I get a perfectly formatted email without attachment. This can only happen with the changes from #1006\r\n\r\nAs far as I can see, fail2ban ignores my config after a reboot, but it respects my config after restarting the fail2ban service.\r\n\r\nSuggestion: There should not be a difference between reboot and restart of the service.\r\n\r\nPlease note that my fail2ban version is rather old: v0.8.6 which comes from debian wheezy.\r\n\r\nThe problem seems to be reproducable. I tried several times.\r\n\r\nI also found out that performing a\r\n\r\n    service fail2ban stop && service fail2ban start\r\n\r\nseems to be equivalent to \r\n\r\n    service fail2ban restart\r\n\r\nin terms of this issue."},"comment":{"url":"https://api.github.com/repos/fail2ban/fail2ban/issues/comments/90513003","html_url":"https://github.com/fail2ban/fail2ban/issues/1011#issuecomment-90513003","issue_url":"https://api.github.com/repos/fail2ban/fail2ban/issues/1011","id":90513003,"user":{"login":"sebres","id":3769657,"avatar_url":"https://avatars.githubusercontent.com/u/3769657?v=3","gravatar_id":"","url":"https://api.github.com/users/sebres","html_url":"https://github.com/sebres","followers_url":"https://api.github.com/users/sebres/followers","following_url":"https://api.github.com/users/sebres/following{/other_user}","gists_url":"https://api.github.com/users/sebres/gists{/gist_id}","starred_url":"https://api.github.com/users/sebres/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sebres/subscriptions","organizations_url":"https://api.github.com/users/sebres/orgs","repos_url":"https://api.github.com/users/sebres/repos","events_url":"https://api.github.com/users/sebres/events{/privacy}","received_events_url":"https://api.github.com/users/sebres/received_events","type":"User","site_admin":false},"created_at":"2015-04-07T11:27:55Z","updated_at":"2015-04-07T11:27:55Z","body":"Since 0.9.1 the loading of config files are totally revised, so I can no more track all changes since very old v0.8.6, what affects this problem. \r\nCan you test a new master (debian) branch or at least sid (or experemental) from https://packages.debian.org/sid/fail2ban?\r\n"}}