Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
n/a
-
None
Description
Noticed this while debugging an unrelated failure. I'm guessing it's due to the VM upgrade in the dist-test environment? We should probably configure /proc/sys/kernel/yama/ptrace_scope in the host OS so that we can restore this functionality.
I0710 23:27:16.445466 18604 external_mini_cluster-itest-base.cc:86] Attempting to dump stacks of TS 0 with UUID 3576d2baa86141439f2e837433589a9b and pid 22014 ************************ BEGIN STACKS ************************** Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. /tmp/dist-test-taskXw_ur6/build/debug/test-work/tablet_copy_client_session-itest/22014: No such file or directory. No threads. ************************* END STACKS *************************** I0710 23:27:16.608888 18604 external_mini_cluster-itest-base.cc:86] Attempting to dump stacks of TS 1 with UUID 6ec7d1737cd1460ab9dd752e64eac912 and pid 22413 ************************ BEGIN STACKS ************************** Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. /tmp/dist-test-taskXw_ur6/build/debug/test-work/tablet_copy_client_session-itest/22413: No such file or directory. No threads. ************************* END STACKS ***************************