cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Collector failed to restart.

christopher_teb
Organizer

Hi,

My Collector failed to restart. it prompts this error in the logs

"

2018-01-23 06:47:22 WARNING [WatchDog] Failed to ping native watchdog at 127.0.0.1:50000 (Connection refused (Connection refused))
2018-01-23 06:48:22 WARNING [WatchDog] Failed to ping native watchdog at 127.0.0.1:50000 (Connection refused (Connection refused))
2018-01-23 06:49:22 WARNING [WatchDog] Failed to ping native watchdog at 127.0.0.1:50000 (Connection refused (Connection refused))
2018-01-23 06:50:22 WARNING [WatchDog] Failed to ping native watchdog at 127.0.0.1:50000 (Connection refused (Connection refused))
2018-01-23 06:51:22 WARNING [WatchDog] Failed to ping native watchdog at 127.0.0.1:50000 (Connection refused (Connection refused))
2018-01-23 06:52:22 WARNING [WatchDog] Failed to ping native watchdog at 127.0.0.1:50000 (Connection refused (Connection refused))

"

Kindly help

Chris

3 REPLIES 3

BabarQayyum
Leader

Hello Chris,

Did you restart the box and tried?

Which activity has been done before this issue?

Is the 50000 port being used by another process or blocked by a firewall?

Can you share the full log?

Regards,

Babar

Hi Babar,

Did you restart the box and tried?

<>Yes i restarted it

Which activity has been done before this issue?

<>No, i just found it down. i did a normal restart but kept on prompting such

Is the 50000 port being used by another process or blocked by a firewall?

<>No, not really

Can you share the full log?

collector00.zip

Br,

cHRIS

peter_karlhuber
Dynatrace Pro
Dynatrace Pro

Hi Chris,

the collector consists of two processes that try to communicate over TCP port 50000. The first process (the "launcher") is a native service (in Linux started via the init.d shell scripts, in Windows it's a registered service) and opens the port 50000 for communication. It then starts the jvm for the actual collector java process. This tries to connect to this port 50000 to ping regularly.

Please inspect also the CollectorLauncher*.log files to see if there'S some error reported there.

Please also check if you're maybe running some security hardened Linux with something like SELinux.

If this doesn't help, please open a support ticket with all the log files from the collector's log folder. Thanks,

best regards,

Peter