Bug 1072768 - [abrt] zarafa-dagent: exit(): zarafa-dagent killed by SIGSEGV
Summary: [abrt] zarafa-dagent: exit(): zarafa-dagent killed by SIGSEGV
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: zarafa
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:57c014cc2ae0bf5091074118847...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-05 07:51 UTC by James Hill
Modified: 2014-04-20 18:03 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-20 18:03:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (15.27 KB, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: cgroup (158 bytes, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: core_backtrace (2.54 KB, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: dso_list (9.10 KB, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: environ (51 bytes, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: exploitable (82 bytes, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: limits (1.29 KB, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: maps (34.17 KB, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: proc_pid_status (925 bytes, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
File: var_log_messages (2.21 KB, text/plain)
2014-03-05 07:52 UTC, James Hill 		no flags Details
View All

Description James Hill 2014-03-05 07:51:55 UTC 
Description of problem:
Zarafa-Dagent delivering same email over and over again.
started after last update, reboot of server or restart of service does not fix.

Version-Release number of selected component:
zarafa-dagent-7.1.7-1.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/bin/zarafa-dagent jameshill
crash_function: exit
executable:     /usr/bin/zarafa-dagent
kernel:         3.12.9-301.fc20.x86_64
open_fds:       
runlevel:       N 5
type:           CCpp
uid:            981

Truncated backtrace:
Thread no. 1 (2 frames)
 #4 exit at exit.c:104
 #6 _start
Comment 1 James Hill 2014-03-05 07:52:00 UTC 
Created attachment 870832 [details]
File: backtrace
Comment 2 James Hill 2014-03-05 07:52:02 UTC 
Created attachment 870833 [details]
File: cgroup
Comment 3 James Hill 2014-03-05 07:52:04 UTC 
Created attachment 870834 [details]
File: core_backtrace
Comment 4 James Hill 2014-03-05 07:52:06 UTC 
Created attachment 870835 [details]
File: dso_list
Comment 5 James Hill 2014-03-05 07:52:08 UTC 
Created attachment 870836 [details]
File: environ
Comment 6 James Hill 2014-03-05 07:52:10 UTC 
Created attachment 870837 [details]
File: exploitable
Comment 7 James Hill 2014-03-05 07:52:12 UTC 
Created attachment 870838 [details]
File: limits
Comment 8 James Hill 2014-03-05 07:52:14 UTC 
Created attachment 870839 [details]
File: maps
Comment 9 James Hill 2014-03-05 07:52:16 UTC 
Created attachment 870840 [details]
File: proc_pid_status
Comment 10 James Hill 2014-03-05 07:52:19 UTC 
Created attachment 870841 [details]
File: var_log_messages
Comment 11 Robert Scheck 2014-03-05 07:53:11 UTC 
Can you please try the latest Zarafa packages in testing repository?
Comment 12 James Hill 2014-03-05 09:17:31 UTC 
Hi Robert

Enabled repos and updated zarafa.  dagent is now running testing version.
zarafa-dagent.x86_64 7.1.8-3.fc20 @updates-testing

Still getting same error.

Regards

James
Comment 13 Robert Scheck 2014-03-05 13:13:11 UTC 
James, thank you for the feedback. Then I need a reproducer if possible. If
you would like to send me that privately just use my e-mail address. Thanks!
Comment 14 James Hill 2014-04-08 23:26:33 UTC 
Updated with a new Kernal today.

Problem seems to have disappeared. 3.13.8-200.fc20.x86_64

Last update was 10 days previous, so its been one of the updates released since then.  But I'd point the finger at the kernal having a little bug fix in it :-)

Going to watch it for a few days to make sure, and if no repeat, I'll close the ticket.
Comment 15 Robert Scheck 2014-04-09 08:23:39 UTC 
Okay...hard to believe that it's the kernel but not impossible through. If
you like you can also mail me your /var/log/yum.log file - then I would have
a look to it.
Comment 16 James Hill 2014-04-20 18:03:08 UTC 
Seems to be resolved.
Note You need to log in before you can comment on or make changes to this bug.