Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Could not start attach mechanism: No such file or directory #44

Closed
egor-ryashin opened this issue Aug 12, 2017 · 2 comments
Closed

Could not start attach mechanism: No such file or directory #44

egor-ryashin opened this issue Aug 12, 2017 · 2 comments

Comments

@egor-ryashin
Copy link 

sudo ./profiler.sh -d 15 2381

Could not start attach mechanism: No such file or directory

Cannot figure out what's wrong.
@egor-ryashin
Copy link
Author

The process was in a docker container.

@apangin
Copy link
Collaborator

apangin commented Aug 12, 2017

Right, the profiler and the JVM should have access to each other, which is not usually the case with containers. I've added Troubleshooting section to README. Thank you for the report.

6fears7 pushed a commit to 6fears7/async-profiler that referenced this issue Apr 10, 2023
@korniltsev
feature: agent configuration options (async-profiler#44)
82b1dab 
Allow agent configuration from system properties, from properties file
Allow some components of agent to be swapped (Exporter, ProfilingScheduler, Logger)
Allow agent to be started from java code, not from -javaagent
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@apangin @egor-ryashin