Bug #16638: "saw valgrind issue <kind>SyscallParam</kind>" in hammer integration testing (rgw) - Ceph - Ceph

Actions

Copy link

Bug #16638

closed

"saw valgrind issue <kind>SyscallParam</kind>" in hammer integration testing (rgw)

Added by Nathan Cutler almost 8 years ago. Updated almost 8 years ago.

Status:

Duplicate

Priority:

Normal

Assignee:

Category:

Target version:

% Done:

Source:

other

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

This is happening in the rgw suite, but I'm not sure it's rgw-related:

2016-07-03T20:39:57.797 INFO:tasks.ceph:Checking for errors in any valgrind logs...
2016-07-03T20:39:57.797 INFO:teuthology.orchestra.run.smithi039:Running: "sudo zgrep '<kind>' /var/log/ceph/valgrind/* /dev/null | sort | uniq" 
2016-07-03T20:39:57.800 INFO:teuthology.orchestra.run.smithi007:Running: "sudo zgrep '<kind>' /var/log/ceph/valgrind/* /dev/null | sort | uniq" 
2016-07-03T20:39:57.906 DEBUG:tasks.ceph:file /var/log/ceph/valgrind/mon.b.log kind   <kind>SyscallParam</kind>
2016-07-03T20:39:57.906 ERROR:tasks.ceph:saw valgrind issue   <kind>SyscallParam</kind> in /var/log/ceph/valgrind/mon.b.log
2016-07-03T20:39:57.906 DEBUG:tasks.ceph:file /var/log/ceph/valgrind/osd.3.log kind   <kind>SyscallParam</kind>
2016-07-03T20:39:57.906 ERROR:tasks.ceph:saw valgrind issue   <kind>SyscallParam</kind> in /var/log/ceph/valgrind/osd.3.log
2016-07-03T20:39:57.907 DEBUG:tasks.ceph:file /var/log/ceph/valgrind/osd.4.log kind   <kind>SyscallParam</kind>
2016-07-03T20:39:57.907 ERROR:tasks.ceph:saw valgrind issue   <kind>SyscallParam</kind> in /var/log/ceph/valgrind/osd.4.log
2016-07-03T20:39:57.907 DEBUG:tasks.ceph:file /var/log/ceph/valgrind/osd.5.log kind   <kind>SyscallParam</kind>
2016-07-03T20:39:57.907 ERROR:tasks.ceph:saw valgrind issue   <kind>SyscallParam</kind> in /var/log/ceph/valgrind/osd.5.log

Happened in following four jobs from http://pulpito.ceph.com/smithfarm-2016-07-02_01:12:45-rgw-hammer-backports---basic-smithi/

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Nathan Cutler almost 8 years ago

Project changed from rgw to Ceph
Subject changed from "saw valgrind issue <kind>SyscallParam</kind>" in hammer integration testing to "saw valgrind issue <kind>SyscallParam</kind>" in hammer integration testing (rgw,fs)

Moving to Ceph tracker because the same valgrind errors occur in fs testing as well.

Actions

Copy link

Updated by Nathan Cutler almost 8 years ago

The FS suite failures have the following in addition to SyscallParam:

2016-07-08T22:48:17.814 DEBUG:tasks.ceph:file /var/log/ceph/valgrind/mds.a.log kind   <kind>Leak_DefinitelyLost</kind>
2016-07-08T22:48:17.814 DEBUG:tasks.ceph:file /var/log/ceph/valgrind/mds.a.log kind   <kind>Leak_PossiblyLost</kind>

which the documentation says indicates the program is definitely leaking memory.

Actions

Copy link

Updated by Nathan Cutler almost 8 years ago

Subject changed from "saw valgrind issue <kind>SyscallParam</kind>" in hammer integration testing (rgw,fs) to "saw valgrind issue <kind>SyscallParam</kind>" in hammer integration testing (rgw)

Actions

Copy link

Updated by Nathan Cutler almost 8 years ago

Project changed from Ceph to rgw

Actions

Copy link

Updated by Nathan Cutler almost 8 years ago

Possibly related to #16642 because it appeared in the same hammer integration run.

Actions

Copy link

Updated by Orit Wasserman almost 8 years ago

The valgrind issues are in the monitors and the osd.
They seems to be a tcmalloc issue, the run is configure as notcmalloc flavor.
see also here http://tracker.ceph.com/issues/15117

Actions

Copy link

Updated by Nathan Cutler almost 8 years ago

Orit writes: " @Nathan Cutler, this seems to be a build issue.
valgrind complains on tcmalloc but this run is notcmalloc
see also http://tracker.ceph.com/issues/15117 "

Actions

Copy link