[POC] - Apache 2.2 hung after restarting and loading Web Server Agent module
Hi all,
I'm assisting a POC, and after instrumenting a couple of Application servers, the next step is to place a web server agent on an Apache 2.2 (64 bit), where the OS is Solaris SPARC x64. After researching the reason why there was no init.d script inside the agent archive (community link related HERE ), inserting the "LoadModule dtagent_module ..." string inside the httpd.conf, and editing the dtwsagent.ini file, I was able to start the service and see the agent fully connected (Master + module) from my client.
Thing is, right after this, the Apache results as hung, and not reachable anymore. Commenting the LoadModule string will make the Apache available again, so it looks like it's not accepting the libdtagent.so for some reason.
From a Dynatrace perspective, there were no PurePaths incoming from that agent, and I assume this confirms the fact that the apache was unreachable after all.
Have you ever experienced this kind of behaviour? I looked up un JIRA and the community as well, in fact the customer team and I tried different solutions, like editing the string using the " ", or checking if the adobe Experience manager was present (it was not) but nothing worked.
The POC is running on a DT 6.0 environment, but the test environment where we're trying these solutions is 5.6. However, the servers are identical, and they're reacting to the agent in the same way.
Also, from our agent log, it shows no errors, same from the apache's.
Do you have any ideas? Or maybe there's some conflict with this kind of environment I'm not aware of..
Thanks in advance for your help,
Valerio
Hi Reinhard,
Thanks for your reply, they ensured me that is 64, but I asked to double check anyway, I know it could be tricky. About the shared memory file, there shouldn't be any problem for the agent to pick it up, because I didn't find any warning message in the logs, and this would have been reported there I suppose. I'm going to check them again.
Did you check if the apache ist indeed 64bit and not 32bit?
Check permissions on the shared memory file for the master and apache agent maybe?
