https://ehsanakhgari.org/tags/ubuntu/Recent content in ubuntu on Home PageHugo -- gohugo.ioen-caTo the extent possible under law, Ehsan Akhgari has waived all copyright and related or neighboring rights to this website. This work is published from: Canada.Wed, 21 May 2008 04:12:00 +0000https://ehsanakhgari.org/blog/2008-05-21/fail2ban-only-picking-first-ignore-ip/Wed, 21 May 2008 04:12:00 +0000https://ehsanakhgari.org/blog/2008-05-21/fail2ban-only-picking-first-ignore-ip/Today I had this problem where Fail2ban was keeping on blacklisting an IP address, even though it was in the ignoreip list in /etc/fail2ban/jail.conf. After double-checking everything on the server, and googling desperately, I found out that up to version 0.8.2, Fail2ban had a bug which caused only the first IP in the ignoreip list to take effect. And guess what? Ubuntu versions before gutsy have older versions of Fail2ban. After a bit of digging, I found out the patch which had fixed the problem in 0.https://ehsanakhgari.org/blog/2008-05-21/libpam_foreground-undefined-symbol-error-ubuntu/Wed, 21 May 2008 03:14:02 +0000https://ehsanakhgari.org/blog/2008-05-21/libpam_foreground-undefined-symbol-error-ubuntu/If you happen to run Ubuntu Server (at least, up to version 7.04) and use the Courier POP3 or IMAP server, and you're watching your log files closely, you've seen error messages such as the below one in /var/log/syslog: May 21 01:14:10 server4 authdaemond: PAM [dlerror: /lib/security/pam_foreground.so: undefined symbol: pam_set_data] Many people have observed this problem. This happens because libpam-foreground.so has not been compiled with the right options. This library needs to be linked against libpam.