Profiler already started after write file failed

[Jungzhang]

1. Start proflier task, specific -f to output file, but write file failed
2. Start new proflier task, Report an error "[ERROR] Profiler already started"

[apangin]

I'm not sure I fully understand the question - what does "write file failed" exactly means? Does profiler print any error?
Could you share the exact commands you type and all profiler messages?

[apangin]

[ERROR] Profiler already started message means the profiler is still running. You can stop it with the stop command along with -f option to dump results in the given file.

[Jungzhang]

Thank you for your reply.

I use ./profiler.sh -d 3 -f /root/profil.html [pid] start a profiler task, write failed because the process does not have write permission to the /root directory. I restart ./profiler.sh -d 3 -f /tmp/profil.html [pid] print [ERROR] Profiler already started.

The stop command could solve my problem. But can I terminate automatically when executing the ./profiler.sh -d 3 -f /root/profil.html [pid] command.

[apangin]

This is the intended behavior, I don't see an issue here.

If stopping fails (because of permissions or something), profiler keeps running to allow a user to stop it correctly and dump results to a different file.

I'm closing the issue as a duplicate of #699.