Do you have any experience on running OneAgent for Solaris, but using a proxy? Solaris OS not using zones.
Customer needs to use a proxy in order to reach their SaaS instance
Once we did set up the proxy, as documented by Oracle/Solaris, the config is correct and working from the OS perspective
The agent shows the following exceptions and warnings, regarding heartbeat and web requests when trying to reach the /communication URI (replaced the IP with x characters to avoid disclosing IP or environment in URI)
2018-08-02 04:41:04.859 UTC  info [java ] [agent ] Detected WebLogic version : WebLogic 184.108.40.206.0
2018-08-02 04:41:05.051 UTC  warning [native] Exception sending async messages: unable to perform request using https://sg-us-east-1-35-171-x-x-prodx-virginia.live.ruxit.com/communication: Couldn't connect to server. Totaltime: 2.9056s, Uploadsize: 0b, Downloadsize: 0b, Connecttime: 0s
2018-08-02 04:41:06.405 UTC  info [native] Exception handling periodic task protocols.messages.shared.ClusterTimeRequest: unable to perform request using https://sg-us-east-1-x-171-x-x-prodx-virginia.live.ruxit.com/communication: Couldn't connect to server. Totaltime: 2.9047s, Uploadsize: 0b, Downloadsize: 0b, Connecttime: 0s
2018-08-02 04:41:06.588 UTC  info [java ] [reflector ] Reflector access mode: memberIterating
2018-08-02 04:41:26.962 UTC  info [java ] [reflector ] Reflector caching mode: on
2018-08-02 04:41:32.603 UTC  warning [native] Timer task 'sendCustomPropertiesMsg' took 22507ms to execute (which is more than half of the timer's period)
2018-08-02 04:41:40.096 UTC  warning [native] Potential suspension detected. It is now 20 seconds later than we expected - not sending message to server.
2018-08-02 04:42:01.883 UTC  info [java ] [servlet ] Exception occurred when creating servlet API wrapper - fallback to reflective wrapper javax/servlet/CompuwareServletWrapper
2018-08-02 04:42:13.501 UTC [0000000c] info [java ] [agent ] Detected the following GCs: ParNew, ConcurrentMarkSweep
2018-08-02 04:42:13.505 UTC [0000000c] info [java ] [agent ] Start monitoring of CMS background CPU usage
2018-08-02 04:42:41.344 UTC  info [native] Exception handling periodic task heartbeat: unable to perform request using https://sg-us-east-1-35-x-x-x-prod-x-virginia.live.ruxit.com/communication: Couldn't connect to server. Totaltime: 2.9048s, Uploadsize: 0b, Downloadsize: 0b, Connecttime: 0s
Solved! Go to Solution.
I was able to fix it by adding manually the PROXY entry under dynatrace-env.sh
And then under ruxitagentproc.conf
Once there, it may trigger some certificate issues while trying to connect to the tenant.
It can also be fixed by adding the local cert (customer/prospect cert) in:
So it takes some manual tweaks by at least all make sense and it is working perfectly