Hi,
Eventhough I have changed from the dynaTrace Client:
- Configure setting -> Settings -> Sizing .. from Small to Medium
and dynaTrace show the legend "sufficient memory available to run at dynaTrace Server"
- Saving the changes
I still have a daily warning when starting the dynaTrace customer, "The dynaTrace Server memory is Currently limited to 3,072 MB total memory"
The server has 15 GBytes of RAM.
I do not understand what's going on.
Please, I need help !
Thanks
Answer by Jose M. ·
Hi Markie,
whats is your dynatrace sizing configuration??
This sound me like really your server memory is going at the top of default that dynatrace have with the umbral.
You can change this from dynatrace configuration file.
Frontend Configs:
...
-basedir
server
-restartonfailure
-memory
large
-vmargs
...
Backend Configs:
...
-basedir
server
-restartonfailure
-memory
large
-vmargs
...
as discussed Thomas, should first upgrade your client.
If you can not, the other option is to use the JNLP Client webstart.
You can access from the link:
http://your_dynatrace_server_name:8020/webstart/Client/client.jnlp
Good luck Markie !!
Answer by Markie S. ·
Hello,
We are running version 6.0.0.7064 with Launcher Version 6.0.0.6738 and are still receiving the warning below.
2015-03-01 09:09:13 [36329ef1] info [native] Native Launcher version: 6.0.0.6738 - built 2014-08-01 16:35:44 +0200
2015-03-01 09:09:20 [36329ef1] info [native] Launcher configuration summary for dynaTrace Frontend Server:
2015-03-01 09:09:13 [b21deed7] info [native] Native Launcher version: 6.0.0.6738 - built 2014-08-01 16:35:44 +0200
2015-03-01 09:09:18 [b21deed7] info [native] Launcher configuration summary for dynaTrace Server:
I noticed that the documentation states that this is a known issue that can be ignored, however it apears that the memory actually is being limited on our server since the last restart. Has anyone else seen this?
Dear Markie,
the documentation regards to a known display-only issue (JLT-104621) that is fixed in both public fixpacks for 6.0 (I updated the docs) and also in 6.0.0.7064. The launcher update addresses a separate problem that looks good looking at your logs.
However, you should not see the warning at all in your client. This looks like the client is not updated to 6.0.0.7064. Can you check the clients version? (Help -> About).
Regards,
Thomas
Thank you Thomas.
My Client is 6.0.0.6738 and I unfortunately cannot update it due to directory permissions.
Server memory usage has now exceeded the 5,120 MB, this appears to just be related to Client Version.
This is then the cause of this warning. I recommend to update the client (as all components) to the same version as the server to receive all client-side-fixes. Unless permissions were changed manually, the installer should have set them appropriately to allow all users to update the client if I recall correctly.
Answer by Jose M. ·
Thankyou Reinhard !! ... but I don't know how download the DTF fixpack file.
Please, can you provide the ftp or http link for download this?
Thank !!
Hi Jose,
as per your screenshot, the server is already running the mentioned Fixpack, so you should not need it. Could you post the version of the client that you are running (Client -> Help -> About)? If it is not 6.0.0.7000, could you restart it to update the client to the same version as the server?
Please note also that the technical alert that Reinhard posted has to be addressed by replacing the launcher files (see alert) or by re-installation using the new installers (if you do so, be sure to re-install also 6.0.0.7000).
When the launcher files are replaced and the client has 6.0.0.7000 running, all known issues should be addressed.
Best regards,
Thomas
As mentioned, you should not need the file, but it can be found on the usual Dynatrace download page:
https://downloads.compuwareapm.com/downloads/download.aspx?p=DT
Answer by Jose M. ·
Hi,
this is :
Jose,
please see this technical alert. If you have upgraded from dynatrace version 6.0.0.6733 via fixpack to build .7000
Technical Alerts dynaTrace DATM
08/06/2014 | 6.0.0.6733 | dynaTrace 6.0 may operate with incorrect memory settings |
This should solve the incorrect warning you are seeing.
Reinhard
Answer by Reinhard W. ·
Jose,
which version of dynatrace are you using (including build number). I think you are running into an issue of a wrong warning which has been fixed with the latest version of dynatrace.
Reinhard
JANUARY 15, 3:00 PM GMT / 10:00 AM ET