Repository: brooklyn-docs Updated Branches: refs/heads/master 30aff82ff -> 2459c7a7e
Fix troubleshooting links/formatting/typos Project: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/commit/91ae9e00 Tree: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/tree/91ae9e00 Diff: http://git-wip-us.apache.org/repos/asf/brooklyn-docs/diff/91ae9e00 Branch: refs/heads/master Commit: 91ae9e008e1080060a850bd238a5a4bd49d4d0da Parents: 30aff82 Author: Aled Sage <aled.s...@gmail.com> Authored: Tue Jun 7 16:12:54 2016 +0100 Committer: Aled Sage <aled.s...@gmail.com> Committed: Tue Jun 7 16:12:54 2016 +0100 ---------------------------------------------------------------------- guide/ops/troubleshooting/detailed-support-report.md | 2 +- guide/ops/troubleshooting/index.md | 2 +- guide/ops/troubleshooting/slow-unresponsive.md | 14 +++++++------- 3 files changed, 9 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/91ae9e00/guide/ops/troubleshooting/detailed-support-report.md ---------------------------------------------------------------------- diff --git a/guide/ops/troubleshooting/detailed-support-report.md b/guide/ops/troubleshooting/detailed-support-report.md index 6e3c741..c41ebcb 100644 --- a/guide/ops/troubleshooting/detailed-support-report.md +++ b/guide/ops/troubleshooting/detailed-support-report.md @@ -38,6 +38,6 @@ tar czf brooklyn-report.tgz ${REPORT_DIR} Also consider providing your log files and persisted state, though extreme care should be taken if these might contain cloud or machine credentials (especially if -[Externalised Configuration](({{ site.path.guide }}/ops/externalized-configuration.html) +[Externalised Configuration]({{ site.path.guide }}/ops/externalized-configuration.html) is not being used for credential storage). http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/91ae9e00/guide/ops/troubleshooting/index.md ---------------------------------------------------------------------- diff --git a/guide/ops/troubleshooting/index.md b/guide/ops/troubleshooting/index.md index ebbce45..bb3715c 100644 --- a/guide/ops/troubleshooting/index.md +++ b/guide/ops/troubleshooting/index.md @@ -5,7 +5,7 @@ children: - { path: overview.md, title: Overview } - { path: deployment.md, title: Deployment } - { path: connectivity.md, title: Server Connectivity } -- { path: unresponsive.md, title: Brooklyn Slow or Unresponsive } +- { path: slow-unresponsive.md, title: Brooklyn Slow or Unresponsive } - { path: detailed-support-report.md, title: Detailed Support Report } - { path: softwareprocess.md, title: SoftwareProcess Entities } - { path: going-deep-in-java-and-logs.md, title: Going Deep in Java and Logs } http://git-wip-us.apache.org/repos/asf/brooklyn-docs/blob/91ae9e00/guide/ops/troubleshooting/slow-unresponsive.md ---------------------------------------------------------------------- diff --git a/guide/ops/troubleshooting/slow-unresponsive.md b/guide/ops/troubleshooting/slow-unresponsive.md index 0b90e83..6a8e6f9 100644 --- a/guide/ops/troubleshooting/slow-unresponsive.md +++ b/guide/ops/troubleshooting/slow-unresponsive.md @@ -8,6 +8,7 @@ There are many possible causes for a Brooklyn server becoming slow or unresponsi describes some possible reasons, and some commands and tools that can help diagnose the problem. Possible reasons include: + * CPU is max'ed out * Memory usage is extremely high * SSH'ing is very slow due (e.g. due to lack of entropy) @@ -154,8 +155,7 @@ If the Brooklyn Server was originally run to allow a remote debugger to connect discouraged in production!), then this provides a convenient way to investigate why Brooklyn is being slow or unresonsive. See the Debugging Tips in the tip [Debugging Remote Brooklyn][({{ site.path.guide }}/dev/tips/debugging-remote-brooklyn.html) -and the the [IDE docs](See [Brooklyn Requirements]({{ site.path.guide }}/dev/env/ide/) for more -information. +and the [IDE docs]({{ site.path.guide }}/dev/env/ide/) for more information. ## Log Files @@ -171,7 +171,7 @@ these messages (or their very presence) may change in future version of Brooklyn The lines below are commonly logged, and can be useful to search for when finding the start of a section of logging. -{% highlight %} +{% highlight text %} 2016-05-30 17:05:51,458 INFO o.a.b.l.BrooklynWebServer [main]: Started Brooklyn console at http://127.0.0.1:8081/, running classpath://brooklyn.war 2016-05-30 17:06:04,098 INFO o.a.b.c.m.h.HighAvailabilityManagerImpl [main]: Management node tF3GPvQ5 running as HA MASTER autodetected 2016-05-30 17:06:08,982 INFO o.a.b.c.m.r.InitialFullRebindIteration [brooklyn-execmanager-rvpnFTeL-0]: Rebinding from /home/compose/compose-amp-state/brooklyn-persisted-state/data for master rvpnFTeL... @@ -183,7 +183,7 @@ The lines below are commonly logged, and can be useful to search for when findin The debug log includes (every minute) a log statement about the memory usage and task activity. For example: -{% highlight %} +{% highlight text %} 2016-05-27 12:20:19,395 DEBUG o.a.b.c.m.i.BrooklynGarbageCollector [brooklyn-gc]: brooklyn gc (before) - using 328 MB / 496 MB memory (5.58 kB soft); 69 threads; storage: {datagrid={size=7, createCount=7}, refsMapSize=0, listsMapSize=0}; tasks: 10 active, 33 unfinished; 78 remembered, 1696906 total submitted) 2016-05-27 12:20:19,395 DEBUG o.a.b.c.m.i.BrooklynGarbageCollector [brooklyn-gc]: brooklyn gc (after) - using 328 MB / 496 MB memory (5.58 kB soft); 69 threads; storage: {datagrid={size=7, createCount=7}, refsMapSize=0, listsMapSize=0}; tasks: 10 active, 33 unfinished; 78 remembered, 1696906 total submitted) {% endhighlight %} @@ -198,7 +198,7 @@ One source of high CPU in Brooklyn is when a subscription (e.g. for a policy or triggered many times (i.e. handling many events). A log message like that below will be logged on every 1000 events handled by a given single subscription. -{% highlight %} +{% highlight text %} 2016-05-30 17:29:09,125 DEBUG o.a.b.c.m.i.LocalSubscriptionManager [brooklyn-execmanager-rvpnFTeL-8]: 1000 events for subscriber Subscription[SCFnav9g;CanopyComposeApp{id=gIeTwhU2}@gIeTwhU2:webapp.url] {% endhighlight %} @@ -213,7 +213,7 @@ If a subscription is handling a huge number of events, there are a couple of com All activity triggered by the REST API or web-console will be logged. Some examples are shown below: -{% highlight %} +{% highlight text %} 2016-05-19 17:52:30,150 INFO o.a.b.r.r.ApplicationResource [brooklyn-jetty-server-8081-qtp1058726153-17473]: Launched from YAML: name: My Example App location: aws-ec2:us-east-1 services: @@ -232,6 +232,6 @@ include the stdout and stderr of all the commands executed by that entity. It can also be very useful to search for all effector invocations, to see where the behaviour has been triggered: -{% highlight %} +{% highlight text %} 2016-05-27 12:45:43,529 DEBUG o.a.b.c.m.i.EffectorUtils [brooklyn-execmanager-gvP7MuZF-14364]: Invoking effector stop on TomcatServerImpl{id=mPujYmPd} {% endhighlight %}
