Version-Release number of selected component: fail2ban-0.9-2.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x crash_function: sqlite3_value_type executable: /usr/bin/python2.7 kernel: 3.16.3-200.fc20.x86_64 runlevel: unknown type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 sqlite3_value_type at sqlite3.c:66453 #1 sqlite3_column_type at sqlite3.c:67116 #2 _pysqlite_fetch_one_row at /usr/src/debug/Python-2.7.5/Modules/_sqlite/cursor.c:354 #3 pysqlite_cursor_iternext at /usr/src/debug/Python-2.7.5/Modules/_sqlite/cursor.c:925 #4 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2571 #5 PyEval_EvalCodeEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:3330 #6 fast_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4194 #7 call_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4119 #8 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2740 #9 fast_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4184
Created attachment 942560 [details] File: backtrace
Created attachment 942561 [details] File: cgroup
Created attachment 942562 [details] File: core_backtrace
Created attachment 942563 [details] File: dso_list
Created attachment 942564 [details] File: environ
Created attachment 942565 [details] File: exploitable
Created attachment 942566 [details] File: limits
Created attachment 942567 [details] File: maps
Created attachment 942568 [details] File: open_fds
Created attachment 942569 [details] File: proc_pid_status
Created attachment 942570 [details] File: var_log_messages
Let's see what the sqlite folks have to say. When does this occur?
From the look in the detailed stacktrace, it seems that the crash is caused by dereferencing a NULL pointer. I will contact upstream and see what they will told us about it.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.