We have our windows based web site hosted on 4 servers. Although we can see on the monitoring/infrastructure dashboard details and basic performance metrics about the servers only one of the four machines is showing us purepaths/transactions. Looking closer at the agent status we see the message:
The Agent is not correctly working because there's a shared memory related problem (details see logs)
Although the agent is connected we are not getting transactions captured when checking the purepaths. Any advice on this status message will be great. Where do we see the correct logs, is it within the System Information>System Profile>app profile log
Thanks
Answer by Christian S. ·
no, you have to look into the agent log files, which are located in the system information dashlet under:
<server_name> - "connected systems" - <collector_name> - "connected systems" - <agent_name>
HTH,
Christian
Thank you Christian, I can see the agent logs now. I think I opened the correct log and see the details below similar to the general memory problem I saw on the UI. Any additional advice on the details below will be greatly appreciated.
015-05-06 21:15:53.765620 [129288/0000020c] info [native] Shared memory file: F:\Program Files (x86)\dynaTrace2\dynaTrace Agent 5.5.0\agent\conf2015-05-06 21:15:53.765620 [129288/0000020c] info [native] Master agent port: 80022015-05-06 21:15:53.765620 [129288/0000020c] info [native] Using SHM location: F:\Program Files (x86)\dynaTrace2\dynaTrace Agent 5.5.0\agent\conf2015-05-06 21:15:53.765620 [129288/0000020c] warning [native] Could not open file F:\Program Files (x86)\dynaTrace2\dynaTrace Agent 5.5.0\agent\conf: Access is denied.2015-05-06 21:15:53.765620 [129288/0000020c] severe [native] Could not create or attach to shared memory segment. Using private data instead.2015-05-06 21:15:53.765620 [129288/0000020c] severe [native] This means the shared memory segment used for communication between the web server agent and the web server module could not be created or attached to. Try deleting the file and make sure the agent has write permissions to it. The backing file used was: F:\Program Files (x86)\dynaTrace2\dynaTrace Agent 5.5.0\agent\conf2015-05-06 21:15:53.765620 [129288/00000264] info [native] Loading collector peer list from f:/Program Files (x86)/dynatrace2/dynaTrace Agent 5.5.0/agent/conf/collectorlist.EIWEB174-ContractRatesPROD
mhm, it's interesting why the shared memory file should be "F:\Program Files (x86)\dynaTrace2\dynaTrace Agent 5.5.0\agent\conf", which is usually just the config directory.
could you please check the following:
HTH,
Christian
JANUARY 15, 3:00 PM GMT / 10:00 AM ET