Profiler attached, but no log file created

Questions about YourKit .NET Profiler
Post Reply
svdh
Posts: 1
Joined: Wed Mar 17, 2021 8:19 pm

Profiler attached, but no log file created

Post by svdh »

I have successfully started the profiler agent on a remote machine, but neither the log is created, nor is the session available remotely.

Here is the result of "YourKitTools.bat status"


C:\Program Files\YourKit .NET Profiler 2021.3-b98\bin>YourKitTools.bat status
YourKit .NET Profiler - Command line tool.
32-bit agent DLL is registered: C:\Program Files\YourKit .NET Profiler 2021.3-b9
8\bin\win32\ynpagent.dll
64-bit agent DLL is registered: C:\Program Files\YourKit .NET Profiler 2021.3-b9
8\bin\win64\ynpagent.dll

The YourKit ETW service is running.

Running .NET applications:

Name | PID | User | Profiler Agent | Port
---------+-------------+----------------+----------------+-------
mmc.exe | 1540 64-bit | admin | Not loaded |
w3wp.exe | 1592 64-bit | DefaultAppPool | Loaded | 10001

Profiling of all processes that will start: disabled


--------------------------------
Referring to your documentation I should find a file in C:\Users\admin\.ynp\log with the name

YourKitTools.dll-1592.log

but there is no such file. There are various other files but none concerning the w3wp.exe process.

Any thoughts on this?

Thank you
Anton Katilin
Posts: 6172
Joined: Wed Aug 11, 2004 8:37 am

Re: Profiler attached, but no log file created

Post by Anton Katilin »

The log should be in the home directory of the w3wp.exe process user "DefaultAppPool" which apparently differs from C:\Users\admin.
Anton Katilin
Posts: 6172
Joined: Wed Aug 11, 2004 8:37 am

Re: Profiler attached, but no log file created

Post by Anton Katilin »

Update:

Instead of using a generic attach command

Code: Select all

YourKitTools.bat attach <PID>
please try a dedicated command

Code: Select all

YourKitTools.bat iis-enable listen=all
which is specially designed for IIS profiling.
nor is the session available remotely
The above mentioned option "listen=all" will allow a remote connection to the profiled instance, please see https://www.yourkit.com/docs/dotnet/hel ... jsp#listen
Anton Katilin
Posts: 6172
Joined: Wed Aug 11, 2004 8:37 am

Re: Profiler attached, but no log file created

Post by Anton Katilin »

Update #2:

We've just released new build #99 which introduces the ability to specify startup options as parameter of "attach" command: https://www.yourkit.com/docs/dotnet/hel ... e_tool.jsp

This allows to use "YourKitTools.bat attach <PID> listen=all" to make the agent port remotely visible. However, as I wrote earlier, the command "YourKitTools.bat iis-enable listen=all" is preferable in the case of IIS. Attached agents are limited in functionality, see "Attach mode limitations" at https://www.yourkit.com/docs/dotnet/hel ... _agent.jsp
Post Reply