Purepath: Corrupteds, Truncateds and Timed Out on AIX 6.1
Dynatrace Version 6.0 in a client environment.
Agent installed on AIX 6.1 64 bits with IBM_HTTP_Server/7.0.0.25 (Unix) 32 bits.
Dynatrace agent is wsagent on ppc 32 bits.
The agent, connect successfully and the column "Total Purepath" count on "Agents View" is not null.
The agent logs or collectors has no errors, but, I don´t see the purepaths from Webserver with WSAgent.
Important to note: OS is 64 bits, but web server is 32 bits and also the DT web server agent is 32 bits. This combination sounds good.
Resolution: Go to "system profile -> agent mapping -> advanced" and switch the timer of the agent(s) that runs on AIX to "POSIX" or "low-res system clock" and restart the agent(s).
Case reference: https://support.compuwareapm.com/supportportal/browse/SUPDT-3055
Can I ask why the timer matters? When should we think about checking the timer, and when not? Or we need to always check this?
What is the mechanism behind this?
hi,
to clarify this a little bit: the timer matters, because if we get completely incorrect timings (e.g. PurePath is seemingly a few months old), then the PurePaths are discarded at the server.
in dynaTrace 6.0 we fixed a bug which allowed us to use the POSIX timer on AIX, which also is the timer with the highest priority for web server agents on AIX. however, the POSIX timer on AIX behaves different then we expected for web server agents and different to POSIX timers on other platforms. this is why this problem came up in the first place.
easiest workaround: switch the timer to 'hardware high-res' or 'low-res', but NOT to 'POSIX' which will not make a difference.
in dynaTrace 6.1 and in the next public fixpack for 6.0 we have a fix for this to not use the POSIX timer for web server agents.
bottom line: usually (apart from 6.0 GA web server agents on AIX) you should be fine with the automatic timer selection.
best,
Christian
