Bug 1242146

Summary: [abrt] fail2ban-server: sqlite3_value_type(): python2.7 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: harry <hjohnson933>
Component: sqliteAssignee: Jan Staněk <jstanek>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: athmanem, Axel.Thimm, jonathan.underwood, jstanek, orion, patrick.sefton, puntogil, vonsch, wilmer5
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e5253eef4f6c2780adac488d6f917923294b6077
Whiteboard: abrt_hash:4b0a5c03d661dd003b97a3c43cafd8f76f358a78
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-02 14:20:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description harry 2015-07-11 15:44:53 UTC 
Description of problem:
It is a background process so I know nothing more than what is in the logs.

Version-Release number of selected component:
fail2ban-server-0.9.1-4.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/bin/python -Es /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b
crash_function: sqlite3_value_type
executable:     /usr/bin/python2.7
kernel:         4.0.6-200.fc21.x86_64+debug
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 0 (10 frames)
 #0 sqlite3_value_type at sqlite3.c:69187
 #1 sqlite3_column_type at sqlite3.c:69949
 #2 _pysqlite_fetch_one_row at /usr/src/debug/Python-2.7.8/Modules/_sqlite/cursor.c:353
 #3 pysqlite_cursor_iternext at /usr/src/debug/Python-2.7.8/Modules/_sqlite/cursor.c:922
 #4 listextend at /usr/src/debug/Python-2.7.8/Objects/listobject.c:881
 #5 list_init at /usr/src/debug/Python-2.7.8/Objects/listobject.c:2467
 #6 type_call at /usr/src/debug/Python-2.7.8/Objects/typeobject.c:745
 #7 PyObject_Call at /usr/src/debug/Python-2.7.8/Objects/abstract.c:2529
 #8 do_call at /usr/src/debug/Python-2.7.8/Python/ceval.c:4328
 #9 call_function at /usr/src/debug/Python-2.7.8/Python/ceval.c:4133
Comment 1 harry 2015-07-11 15:44:56 UTC 
Created attachment 1050892 [details]
File: backtrace
Comment 2 harry 2015-07-11 15:44:56 UTC 
Created attachment 1050893 [details]
File: cgroup
Comment 3 harry 2015-07-11 15:44:57 UTC 
Created attachment 1050894 [details]
File: core_backtrace
Comment 4 harry 2015-07-11 15:44:58 UTC 
Created attachment 1050895 [details]
File: dso_list
Comment 5 harry 2015-07-11 15:44:59 UTC 
Created attachment 1050896 [details]
File: environ
Comment 6 harry 2015-07-11 15:45:00 UTC 
Created attachment 1050897 [details]
File: exploitable
Comment 7 harry 2015-07-11 15:45:01 UTC 
Created attachment 1050898 [details]
File: limits
Comment 8 harry 2015-07-11 15:45:02 UTC 
Created attachment 1050899 [details]
File: maps
Comment 9 harry 2015-07-11 15:45:04 UTC 
Created attachment 1050900 [details]
File: open_fds
Comment 10 harry 2015-07-11 15:45:06 UTC 
Created attachment 1050901 [details]
File: proc_pid_status
Comment 11 Orion Poplawski 2015-07-11 18:37:14 UTC 
Let's see if the sqlite folks have any insight.
Comment 12 harry 2015-07-12 02:38:19 UTC 
(In reply to Orion Poplawski from comment #11)
> Let's see if the sqlite folks have any insight.

When I restarted the fail2ban server it added 17,000 lines to iptables. For a temp fix I manually set the jumps to the chains and disabled the everything in the action start except for the name. I also disabled the flush and delete the name from action start but left the delete for the match. I also truncated the database but made a backup copy if you need it. After poking around in my logs I found that to jail were matching on "password failed for root" so I added and ignore to one of the jails. So far all is working, but the memory usage has jumped to about 3%. If you need any more information let me know. I will be glad to help this is a very good application.

Harry
Comment 13 Orion Poplawski 2015-07-23 20:11:15 UTC 
https://retrace.fedoraproject.org/faf/problems/866690/ show as count of 5280, almost all on EL7.
Comment 14 Fedora End Of Life 2015-11-04 11:02:46 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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.
Comment 15 Fedora End Of Life 2015-12-02 14:20:43 UTC 
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.