Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

cbcollect does not collect lsof information for memcached

Description

Cbcollect currently runs the following command to capture the lsof output for the machine:

However, as part of , all memcached threads are named 'mc:<purpose of thread>:<thread_num>', as such this lsof command will not actually retrieve any of the open files in use by any of the memcached threads, this needs to be updated so that it appropriately gathers the information for all memcached threads.

Components

Affects versions

Fix versions

Labels

Environment

All linux environments

Link to Log File, atop/blg, CBCollectInfo, Core dump

https://s3.amazonaws.com/cb-support/malarky/10153/collectinfo-2015-12-23T122115-ns_1%40malarky-cb-1.c.cb-googbench-101.internal.zip

Release Notes Description

None

blocks

Activity

Matt Carabine January 24, 2016 at 5:41 PM

Verified that after the changed in memcached, cbcollect_info now collects all of the relevant lsof information for memcached again on 4.5.0-1069 and 4.1.1-5703.

Dave Rigby January 7, 2016 at 3:45 PM

Fixes merged to sherlock and master branches.

Don Pinto [X] January 6, 2016 at 5:32 PM

@wayne - Let's go through this during the maintenance meeting.

Trond Norbye January 6, 2016 at 4:02 PM

Or the startup script can just create a process group and run ns_server and everything in it....

Dave Rigby January 6, 2016 at 3:45 PM

Correct me if I'm wrong but doesn't that require that ns_server launches the process in a specific manner?

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Yes

Triage

Triaged

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created December 29, 2015 at 3:03 PM
Updated March 4, 2016 at 8:13 PM
Resolved January 7, 2016 at 3:45 PM
Instabug