collector listener port not opening
Hello,
We are creating a dynaTrace instance and we can see it connects to dynaTrace server but it shows with a red dot next to it:
Looking into the logs, we get this warning message:
2014-03-26 16:35:26 INFO [Collector] Server Buffers: 400 x 0.5 MB
2014-03-26 16:35:26 INFO [ClassCacheWritingThread] Class cache size on disk: 48 bytes (0.00M)
2014-03-26 16:35:26 INFO [ClassCacheWritingThread] Inheritance map files size on disk: 0 bytes (0.00M)
2014-03-26 16:35:26 WARNING [Collector] Could not open port 9997 on interface 'mycollector' for collector communication! java.net.UnknownHostException: mycollector
2014-03-26 16:35:26 WARNING [AgentListener] Could not resolve Agent Listener binding address: mycollector
2014-03-26 16:35:27 INFO [UserPluginManager] Plugin manager started on XXXXXXXX.exttest.local:6698
2014-03-26 16:35:28 INFO [CollectorMemoryTracker] Emergency Limit: 2007760896 Bytes (=95%)
2014-03-26 16:35:28 INFO [CollectorMemoryTracker] Refuse Agent Connection Limit: 1850474496 Bytes (=87%)
Why could this be happening? We do have another collector that is running in the same server on port 9998 without any issues. We have rebooted the server already and we have tried to re-create the instance again and we have no luck.
Any input will be valuable
Regards,
Santiago
Hi. For this Collector that fails it seems you have defined to bind it to the network interface "mycollector". I assume you simply did a little config mix up with collector name and binding information. Double check your collector.config file and see where you use mycollector. It is probably just in the wrong config field
Thank you Andy,
The bizarre thing about this is that we have been using the same script created internally for every single instance we built in multiple collectors.
After creating a collector instance, this is how the configuration looks like:
Name: mycollector ---> Host: collector server
*FQDN (fully qualified domain name)
This is the first time we have run into an issue like this. I will look into it and let you know if there was a resolution.
Thanks
As odd as this is, we ran the command
dtcollector -service install -instance MyCollector -listen :9997 -server mydynatraceserver
sc start "dynaTrace Collector 5.6.0 (MyCollector)"
And this time worked.
Thanks Andy
Community Member of the Month
December 2018
Announcing Dynatrace's Community Member of the Month for December 2018, Sebastian K.! Click here to read more! Employee Member of the Month
December 2018
Announcing Dynatrace's Employee Member of the Month for December 2018, Joshua P.! Click here to read more! 
