Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
I'm currently investigating a problem with the PHP Agent, which fails occasionally. The two errors that occur are
A colleague of mine already contacted AppDynamics, but unfortunately he is on holidays, so I can't follow up to that discussion. Their suggestion was to enable trace-level logging, which I did and which allowed me to capture some information concerning those issues.
The second case seems to be caused by a timeout from the service that provides the configuration (proxy agent?), "[config.ZMQConfigTransport] timed out (2000us) waiting for config. Actual wait time: 1846us". That's pretty short, in particular since the machine only runs on a single CPU.
The first case is harder. Comparing a successful with a failed call doesn't turn up any significant differences. The last line in the log is "[agent] started API exit call of type EXIT_HTTP", after that the segfault kills the process. The topmost frames are in libstdc++, std::string::assign() in particular, which I found out after running the program in a debugger.
Some system details...
So... any suggestions what to try next? Is there even a bugtracking system where I could search for similar issues?
About the two issue you are facing
Is it possible to share the trace level logs & core dump if any. Then I would share an SFTP credentials for same.
Please don't attach them here as it might contain sensitive information.
Concerning the segmentation fault:
Concerning the missing delegate:
I can share the trace-level logs and probably also the core dump.
Thanks for your help!
At the moment, we are not using AppDynamics on the systems that formerly were impacted by that bug. Also, since the the dev team of AppDynamics was able to reproduce the bug and fix it since it was filed, I believe that it shouldn't be a concern. Maybe it's a different bug with similar symptoms.
Two notes though: