Dynatrace 6 and Apache
hello all,
I have instrumented Apache :
/usr/sbin/httpd -Version
Server version: Apache/2.2.15 (Unix)
Server built: Aug 2 2013 08:02:15
Server's Module Magic Number: 20051115:25
Server loaded: APR 1.3.9, APR-Util 1.3.9
Compiled using: APR 1.3.9, APR-Util 1.3.9
Architecture: 64-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT="/etc/httpd"
-D SUEXEC_BIN="/usr/sbin/suexec"
-D DEFAULT_PIDLOG="run/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_LOCKFILE="logs/accept.lock"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"
and when I run dynaTraceWebServerAgent this is the message that I found in log:
2014-07-22 10:18:30.859563 [13564/f77e56d0] info [native] -----------------------------------------------------------------------------------------------
2014-07-22 10:18:30.859579 [13564/f77e56d0] info [native] dynaTrace Agent for Web server Copyright (c) 2004-2014 Compuware Corporation, www.compuware.com
2014-07-22 10:18:30.859592 [13564/f77e56d0] info [native] -----------------------------------------------------------------------------------------------
2014-07-22 10:18:30.859607 [13564/f77e56d0] info [native] Version ..................... 6.0.0.6733, build date Jul 7 2014 22:05:02
2014-07-22 10:18:30.859641 [13564/f77e56d0] info [native] Command line is /opt/dynatrace-6.0.0/agent/lib/dtwsagent server=localhost
2014-07-22 10:18:30.859655 [13564/f77e56d0] info [native] Build platform .............. Linux x86 32-bit
2014-07-22 10:18:30.859671 [13564/f77e56d0] info [native] Platform .................... Linux 2.6.32-358.6.2.el6.x86_64 x86_64
2014-07-22 10:18:30.859683 [13564/f77e56d0] info [native] Bootstrap version ........... 6.0.0.6733
2014-07-22 10:18:30.859695 [13564/f77e56d0] info [native] Log level console ........... none
2014-07-22 10:18:30.859706 [13564/f77e56d0] info [native] Log level file .............. info
2014-07-22 10:18:30.859718 [13564/f77e56d0] info [native] Log file .................... /opt/dynatrace-6.0.0/log/dt_dtwsagent_13564.0.log
2014-07-22 10:18:30.859733 [13564/f77e56d0] info [native] Agent host .................. IN42RM0101P
2014-07-22 10:18:30.859765 [13564/f77e56d0] info [native] Agent library ............... /opt/dynatrace-6.0.0/agent/downloads/6.0.0.6733/native/linux-x86-32/libdtwsagent.so
2014-07-22 10:18:30.859778 [13564/f77e56d0] info [native] Agent name .................. Was2_Reflet_Apache
2014-07-22 10:18:30.859791 [13564/f77e56d0] info [native] Server/Collector ............ xx.xxx.xxx.xxx:9998
2014-07-22 10:18:30.861412 [13564/f77e56d0] info [native] Reading LoadBalancing configuration from 10.170.192.236:9998
2014-07-22 10:18:30.861703 [13564/f77e56d0] info [native] Storing collector peer list (0 entries) to /opt/dynatrace-6.0.0/agent/conf/collectorlist.Was2_Reflet_Apache
2014-07-22 10:18:30.862175 [13564/f77e56d0] info [native] Trying to connect to Server/Collector for up to 19 seconds
2014-07-22 10:18:30.874793 [13564/f77e56d0] info [native] Instrumentation channel connected successfully
2014-07-22 10:18:30.874833 [13564/f77e56d0] info [native] Connected to Server/Collector xx.xxx.xxx.xxx:9998
2014-07-22 10:18:30.877584 [13564/f69deb70] info [native] Control channel connected successfully
2014-07-22 10:18:30.897812 [13564/f69deb70] info [native] Retrieved Application Configuration (Default Application|capture server and user sides|/|n3|debug off)
2014-07-22 10:18:30.901895 [13564/f69deb70] info [native] Agent ID .................... 3d1c0e09
2014-07-22 10:18:30.901917 [13564/f69deb70] info [native] Process ID .................. 13564
2014-07-22 10:18:30.901943 [13564/f69deb70] info [native] Recovery .................... enabled
2014-07-22 10:18:30.907117 [13564/f69deb70] info [native] Hypervisor .................. VMware
2014-07-22 10:18:30.996325 [13564/f77e56d0] info [native] Eventsender channel connected successfully
2014-07-22 10:18:31.007716 [13564/f77e56d0] info [native] Successfully started agent Was2_Reflet_Apache
2014-07-22 10:18:37.044268 [13564/f294db70] severe [native] Rejecting slave agent due to a shared memory mismatch -- a slave agent (id: 7abf44628) using /opt/dynatrace/agent/conf/dynaTraceWebServerSharedMemory is attempting registration on a master agent using /opt/dynatrace-6.0.0/agent/conf/dynaTraceWebServerSharedMemory
2014-07-22 10:36:56.436683 [13564/f294db70] severe [native] ... last message repeated 85 times ...
2014-07-22 10:36:56.436532 [13564/f294db70] severe [native] Rejecting slave agent due to a shared memory mismatch -- a slave agent (id: 70d76ded5) using /opt/dynatrace/agent/conf/dynaTraceWebServerSharedMemory is attempting registration on a master agent using /opt/dynatrace-6.0.0/agent/conf/dynaTraceWebServerSharedMemory
2014-07-22 10:40:10.307809 [13564/f69deb70] severe [native] ... last message repeated 18 times ...
Why ?
Alexis
Looks like there are two install directories here:
/opt/dynatrace/
/opt/dynatrace-6.0.0/
Do you have an old installation you can remove?
Rick B
Rick - I am planning to upgrade to DT 6 & now on 5.6. Is there anything that I need to be careful here about previous installations?
We'll have to get confirmation from the lab but I think this issue may have to do with the architectural change of having the Web Server Agent Process be a child process of Apache (<=5.6) to having it be a service (>=6.0).
Edit: looks like the pre-6.0 behavior is default unless explicitly changed by the user...
I'll reach out and try to get attention here for any considerations for the upgrade.
Thanks,
Rick B
Beginning with 6.0 the master agent (dtwsagent process) is not started by the apache module any more. You must use the init.d/dynaTraceWebServerAgent script instead for starting/stopping the dtwsagent.
This behavior is managed by the property isMasterAgentServiceInstalled in the dtwsagent.ini file, which is false by default and set to true in fresh 6.0 installations. Customers migrating from 5.6 -> 6.0 and using their old dtwsagent.ini, will not have this property in the ini file and the master will be started automatically as before.
hth,
Clemens
Hi Clemens, do we have any reason why this works this way now? It feels a little bit like a retrocess having to start the master agent manually when it used to e automatic.
Is it safe to just add that property to the ini file or should we suggest the customer to start the master agent manually?
Thanks!
We had a couple of issues already with this approach of automatically starting the master, therefore we decided this way.
If a customer didn't have problems in the past, he can go with this setting.
However, for new customers I'd suggest to follow the new way.
hth,
Clemens
Hi Clemens,
You said that this property is set to true from 6.0 on, but the documentation says false is default (https://community.compuwareapm.com/community/display/DOCDT60/Web+Server+Agent+Configuration#WebServerAgentConfiguration-isMasterAgentServiceInstalled), Is this an error in the docs?
Thanks,
Gabriel
The default is false - that will kick in if you have an existing installation where this property is not present in the dtwsagent.ini file. If you install a new agent now you will see that this property is explicitly added with a value of true to the ini file.
Best, Roman
Clemens - For customers migrating to 6.0 , what is the best approach long term? should we also move to dynaTraceWebServerAgent script?
The long term strategy should be to use the new master agent service
I'm working with a customer that is running Apache on Solaris SPARC 32 bit. When we run the .sh file to drop the web server agent files onto the OS, there is not a "dynaTraceWebServerAgent" shell script, or an init.d folder. I just did this same install the other day on Linux, and the file was there.
Has anyone else noticed this?
All,
We are going to upgrade to 6.1 from 5.6. As were were originally using it as a service I have asked our middleware team to disable the web server agents till I upgrade my server to 6.1. Plan to change the configuration so as to use the master agent service after that. I once again wanted to use the forum to check for any know issues etc.
I am always a bit worried about the upgrade considering the fact that in the past we had a major issue in our production env due to the web server agents (old case 00865302). Please let me know on any other best approaches so as to aid the upgrade of the web server agents.
Basically I want to minimize risk...
Hi Jibi,
Regarding the mentioned case, the fix for that problem is included since Dynatrace 6.0 in all releases, thus you should not experience that issue again.
In general I can recommend to closely follow the Upgrade and Migration Guide and to of course perform the mentioned backups.
Best regards,
Thomas
All,
The upgrade to 6.1 is complete for all except the web server agents. Web server agents were disabled prior to upgrade.
Please tell me if the below steps for web server agent upgrade sound good to you.
- Add the web server agent module back with isMasterAgentServiceInstalled as false.
- Web server Agents get upgraded to the 6.1 version.
- Now disable the web server agents again and change isMasterAgentServiceInstalled to true and
- start the agent as a daemon and not as a process. For this use dynaTraceWebServerAgentInstanceName.
- if all looks good, configure to use dynaTraceWebServerAgentInstanceName during boottime.
Or is it really necessary to get the 6.1 dynatrace-wsagent.. tar? All documentation I see reference to 64bit.... But I believe we were using the 32 bit... we still have 32 bit support right?
EDIT: I do see the 32 bit web server agent in the downloads section
Thanks Thomas
When adding a web server tier via the wizard, Dynatrace (v 6.0) still does not mention the need to autostart the master agent as a daemon on Linux. It mentions only running the installation script and adding the web server module to the web server. My customer finds this confusing because they would not have known about the daemon requirement unless they read the documentation. Is there a way to include this instruction in the Add Tier wizard for web tiers?
This would actually be an easy RFE. Just so you can let your client know, when installing the web server agent, at the very end, it actually tells you that you need to start web server in order for it to work. I do agree with you, the wizard should include this info though
FYI - here is how the wizard looks like in upcoming 6.2. we reworked the instructions to make it clear what needs to be done
That looks much better! We still need to actually CREATE the service manually in DT 6.0+, right? The installation script doesn't do this automatically?
Thats a good question. I think the installation script actually DOES start the service for you. But I havent double checked
