DT Web Server Agent 4.2.0.3170
Please help me with download link for
dynatrace-wsagent-4.2.0.3170-solaris-sparc64.tar
as on archive I'm only getting link for 3154.
I have DT server version 4.2.0.3170 and in webserver agent logs I'm getting exception
2013-01-14 19:15:09.404366 12204/00000001* warning native Detected version mismatch in shared memory segment. Expected: 4.2.0.3154, Actual: 4.2.0.3170. Not syncing. Waiting for agent to re-initialize the data. Suppressing this warning.*
Please suggest.
Regards,
Amol
Hi Amol
if you have upgraded your server to 3170 the only thing you need to do is to restart your web server agent and then your web servers. our agents are "bootstrapable" - meaning - they will automatically get the latest version from the dynaTrace Server when they connect. There is no explicit download for these versions as the upgrades to these "update versions" will be done automatically.
hope this helps
Please make sure you are actually injecting the bootstrap agent in the web server (usually dtagent.dll or dtagent.so) to avoid version mismatches.
If you are directly injecting the agentcore (e.g. libdtapacheagent22bo.so), such version conflicts will be the result.
Hi Team
Please tell me how to Restart web server Agent?
Regards,
Jalpesh
You need to restart Apache.
Our Web Server Module in Apache will start the Web Server Agent and will stop it again when Apache is stopped.
Andi
Hi Andi
I have restarted my webserver ,still it does not showing agent.
Please suggest.
Regards,
Jalpesh
can you open a ticket for this? probably better if our techsupport team looks into this.
Jalpesh,
can you post the agent configuration line from apache? The full LoadModule statement you are using?
Reinhard
Hi Reinhard,
Please find agent configuration line from OHS(Webserver):
LoadModule dtagent_module "/opt/oracle/dynatrace-4.2.0.3154/dynatrace-4.2.0/agent/lib64/libdtapacheagent22bo.so"
Regards,
Jalpesh
Hi Jalpesh,
To resolve your version mismatch, change
libdtapacheagent22bo.so
to
libdtagent.so
this will enable the "bootstrap" agent, which will auto-upgrade the web server agent binaries to build 3170 on next proper restart of Apache.
What we all missed here: the customer is using the OHS rather than Apache. OHS is not bootstrappable in 4.2, Apache is! Beware of this pitfall!
