Server Down Errors

Hi Team,

We are observing three servers down errors in the monitoring tab.

Kindly assist us to resolve the issue.

Regards,
Mithunassri B.

Hey,

Below is a link that has some troubleshooting steps which will help you in dealing with this logs are not displayed on console

Thanks,
Manish

Hey there,

Are you able to see graphs on the health page of each components? :thinking:

Here is what you can do:

  • Hover on the Administration icon on the left sidebar of the Home screen, from the option displayed select Manage Components , the following screen will be displayed.

image.png

  • Click the Component name to view the Health page of that particular Component.
  • Check if graphs are visible
  • Check if any service is stopped by visiting the Manage icon displayed in the top right corner of the component Health screen.
1 Like

Hi Riccardo,

The health of the component and graphs are visible as mentioned
Services are also active but still we could see the correlation server, report server and query server down errors.

Regards,
Mithunassri B.

Hey,

The above errors indicate that something is broken at the service level, see the below link this may help you to resolve these errors.

https://docs.dnif.it/docs/troubleshooting-search

Thanks,
Manish

@Mithunassri

This issue is related to the one posted by you here → Observing Error While Searching - #4 by Blackbird2Raven

Both are related so let’s keep an update on one thread itself for simplicity, clarity and avoid confusion.

Thanks,

1 Like

Hi Team,

Observing the server down errors as mentioned in this thread. Also seeing “SYSLOG is fatal” and “datanode not available” errors. The syslog connector has also stopped. Tried restarting the Compute-Leader service as mentioned in the documentation, but the issue remains. PFB the screenshots for the same. Please help to resolve this issue.

Regards,
Anand R Menon

Hello,
One of the issues can be that the default port that the syslog service uses is already in use by an other service and hence syslog service maybe fatal.
Also please check the connectivity between datanode and core using telnet at port 9000 on the datanode server. There might be a connectivity issue there.
Thanks and Regards.

Hi @THOR ,

Thanks for the reply. Now the syslog connector issue is solved. The “services down” and “datanode not available” issues are pending. As you mentioned, we tried running telnet at port 9000 from datanode to core and the connection is getting refused. But there is a java-related service running on port 9000 in core.

Does Port 9000 need to be listening in Datanode as well? In core, no additional setups were done to make Port 9000 listening other than running the script to install the DNIF components.

Please help with this issue.

Regards,
Anand R Menon