• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Michael C. · Dec 16, 2013 at 03:04 PM ·

any way to manually/force an agent update for a dynaTrace patch in 5.5?

We pushed out a 5.5.0.5562 patch this weekend in production however during the update the collector crashed (filesystem filled up).  We got that worked out, restarted the collector and all our agents can connect to it now however in the agent logs some of them show they processed the update however in the client it still shows as the old version for all of them using that collector (5.5.0.5301).  Is there a way to manually/force the update to take effect in the agents?  Or could this still be a collector issue.  I can reinstall the collector fairly easily but that has to wait until the weekend and still would be crossing my fingers the agents are updated automatically as well.

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

9 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Michael C. · Dec 16, 2013 at 07:03 PM

Sure, well here's the obvious ones:

2013-12-14 09:21:04 WARNING [SessionHandshakeRequest] session initializer error: No space left on device: com.dynatrace.diagnostics.communication.tcp.session.SessionHandshakeRequest executeR
equestResponse:87
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:282)
at com.dynatrace.diagnostics.sdk.io.DataInputStreamDataInput.readStream(DataInputStreamDataInput.java:198)
at com.dynatrace.diagnostics2013-12-14 09:21:04 WARNING [SessionHandshakeRequest] session initializer error: No space left on device: com.dynatrace.diagnostics.communication.tcp.sess
ion.SessionHandshakeRequest executeRequestResponse:87
java.io.IOException: No space left on device

 

But then subsequent restarts gave these here & there:

 

2013-12-14 10:12:54 SEVERE [ThrowableHandler] Uncaught exception in thread "Communication-Thread-0@main": illegal byte array size 16777216 (max. byte array size is 10485760): com.dynatrace.d
iagnostics.util.modern.ThrowableHandler uncaughtException:50
java.lang.IllegalArgumentException: illegal byte array size 16777216 (max. byte array size is 10485760)
at com.dynatrace.diagnostics.sdk.io.DataInputStreamDataInput.readByteArray(DataInputStreamDataInput.java:329)
at com.dynatrace.diagnostics.communication.tcp.connection.DefaultSocketHeaderReaderWriter30.readHeader(DefaultSocketHeaderReaderWriter30.java:51)
at com.dynatrace.diagnostics.communication.tcp.connection.DefaultSocketHeaderReaderWriter30.readHeader(DefaultSocketHeaderReaderWriter30.java:24)
at com.dynatrace.diagnostics.communication.tcp.socket.DefaultSocketHandlerRunnable.handleRequest(DefaultSocketHandlerRunnable.java:65)
at com.dynatrace.diagnostics.communication.tcp.socket.DefaultSocketHandlerRunnable.execute(DefaultSocketHandlerRunnable.java:55)
at com.dynatrace.diagnostics.util.threads.StatusRunnable.run(StatusRunnable.java:46)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Andreas G. ♦ · Dec 16, 2013 at 07:27 PM 0
Share

Thanks a lot. I will forward this to the engineering team

avatar image

Answer by Michael C. · Dec 16, 2013 at 06:36 PM

Just an update:  We ended up completely reinstalling the collector in question and appears to have done the trick.  We will be restarting the rest of our applications tonight after hours to see if they all fall in line ( I restarted one small one as a test and it worked).  There must have just been something not quite right after the filesystem filled up and it crashed.

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Andreas G. ♦ · Dec 16, 2013 at 06:38 PM 0
Share

Thanks for the update. Would be interesting to inspect the collector log file of the "crashed" collector. If you still have it somewhere you may want to take a look at it and see whether it contains any log messages that indicate a problem. This would be valuable feedback for our engineering team

avatar image

Answer by Michael C. · Dec 16, 2013 at 04:36 PM

Ok thanks!!

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Dec 16, 2013 at 04:35 PM

If the server and collector are both updated and run with the latest version - and the agent doesnt correctly update to the fixpack version even after a restart I suggest opening a support ticket. A support engineer can then have a closer look at your problem.


 

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Michael C. · Dec 16, 2013 at 03:58 PM

(the reason this is even a significant issue is that this patch has a bug fix in it we need on some of our Prod webservers)

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Michael C. · Dec 16, 2013 at 03:58 PM

It shows 5562 (the updated version).  It was bounced last night (command line) and actually did it again this morning via the console.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Dec 16, 2013 at 03:52 PM

In your server settings dialog you see an overview of all connected collectors. can you check which version of the collector you are running right now? Maybe you need to bounce your collectors as well so that they get properly upgraded

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Michael C. · Dec 16, 2013 at 03:48 PM

Hi Andreas,

We did bounce our apps, and they did then connect back to the collector however still show 5301.  However I can see in their agent log the following:

 

2013-12-15 20:40:08 [40eeb940] info [native] Server requests us to use Agent 5.5.0.5562 with a hash of a0007c29349ce008e9c9e3bce4279356
2013-12-15 20:40:08 [40eeb940] info [native] Agent already available locally

But then after that in the next log:

2013-12-15 20:40:10 [40eeb940] info [java ] Java Agent Version .......... 5.5.0.5301, Agent15

 

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Dec 16, 2013 at 03:42 PM

The agents will automatically get updated when they start. So - rebouncing your application should do the trick.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A