Good afternoon:
I stopped the collector by mistake from console Dynatrace section of Collectors in the System Profile, look at the console Dynatrace a solution but found nothing so I decided from the server where it is Dynatrace stop services collector and dynaTrace with commands (init.d/dynaTraceCollector stop y init.d/dynaTraceServer stop) then start services dynaTrace collector and the commands (init.d/dynaTraceServer start y init.d/dynaTraceCollector start ). As I saw the dashboard still not brought metric execute the command to find the status and collector even still down ... how I can start the collector with another alternative because the server has failed
Thanks
Regards
Answer by Andreas G. ·
Hi
Can you open a support ticket and attach all your log files to that case? I think one of our technical support engineers should look at this. The screenshot of the log file looks very odd. SOmeting is clearly not right
Andi
Answer by Nayeli P. ·
hi:
Take a look at the logs and from the collector unemployment (November 21) will not be returned to write any more, even though there have been attempts to start the services.
Why this happens???
Answer by Andreas G. ·
If you have agents connected they will show up. They will not show up in case a) there are really no agents connected or b) your collectors are currently not connected to the dynatrace server.
As you were reporting problems with your collector I assume your collector is simply not up and running correctly or at least not connected to your dynatrace server. Once you have the Collector back up and successfully connected your agents will also show up again
Answer by Andreas G. ·
Hi
You are following the correct path. Here is the doc page that explains how to configure, start & stop a collector on linux: Collector Configuration#StartingandStoppingonLinuxandUNIX
If the Collector doesnt show up in the list of Collectors on your Dynatrace Server I suggest you take a look into the Collector Log Files. You will find them in your dynaTrace installation directory under log/collector/dynaTrace Collector. There you will find a Collector.0.0.log and the CollectorLauncher_x.log. Have a look into these log files. There should be an indication of the problem, e.g: the Collector cant connect to the server (maybe a firewall issue), or the Collector cant startup because other processes are already using the same listening ports such as 9998.
It could be that stopping the Collector as you did still left the Collector Proceess lingering around in the background still holding on to that port. So - have a look at any still running processes and kill them
Andi
JANUARY 15, 3:00 PM GMT / 10:00 AM ET