Why do I see Internal Service Error (HTTP Response 500) after login?

Why do I see Internal Service Error (HTTP Response 500) after login?

There are two reasons because of which 500 Error can be seen.

  1. UI rendering service (kibana) is not running.
  2. Elasticsearch service is not running

 

1. UI Rendering Service Errors

This can be checked using
(vunetenv) vunet@ vunet-Pro:~$ sudo service kibana status
kibana.service – Kibana
Active: inactive (dead)

The service can be started using
sudo service kibana start

The service is configured using the configuration file at /opt/kibana/config/kibana.yml

 

Common reasons why the service is not running are:

  • Service was stopped manually
  • Service did not start after a system reboot
  • Permission issues. The service should be running as a user ‘kibana. The configuration file should have permissions so that ‘kibana’ user can read the configuration file.

 

If there are permission issues, a service start command will not be able to start the service. After verifying the permissions, if service is still not able to start, you can try starting the service from a terminal.
(vunetenv) vunet@ vunet-Pro:~$ sudo su -l kibana
(vunetenv) vunet@ vunet-Pro:~$ /opt/kibana/bin/kibana  

This will show up errors, if any, that could be analyzed to correct problems.

The configuration file, /opt/kibana/config/kibana.yml, contains the IP address and port number of elasticsearch. Ensure that these settings are correct.

The kibana service logs into /var/log/kibana. Check this log file for errors, if the above steps did not help in resolving the problem.

 

2. Elasticsearch service not running

The elasticsearch service runs on analyzer. The status of the service can be checked using:
sudo service elasticsearch status

Elasticsearch is controlled using configuration file at /etc/elasticsearch.yml

Since debugging elasticsearch problems is quite involved, the details will be covered in a separate section.

The first place to look at when there are problems is to look at elasticsearch logs located at /var/log/elasticsearch/vunet-cluster.log on analyzer.

You can also check whether elasticsearch is responding to requests using
curl <analyzer-ip>:9200/_cat/indices

 

Node Addresses not configured correctly

There are 2 places where node addresses are to be configured

  • In the product, in Preferences, configure IP address of shipper and Analyzer
  • In /opt/kibana/config/kibana.yml, configure IP address of Analyzer

 

Elasticsearch access from Shipper

The components running on shipper need access to port 9200 in analyzer to access elasticsearch service. You can use telnet to check whether this access is there on shipper.
Telnet <analyzer-ip> 9200

    • Related Articles

    • DAQ Service is Getting Stopped 402

      Solution Document              DAQ Service is Getting Stopped Overview General/Customer specific ICICI Author Komali Buddha Reviewer Seema Approver  Arunachala Vakod Release date 13/09/2022 Product Version       8.5r5  Audience: ...

    • What should I do when I see slow search performance or slow indexing performance in Elasticsearch?

      If we talk about performance problems, we can think of the following use cases from the end-user perspective. Search Performance is slow, i.e you execute a search from Kibana and the response is slow or times out. Indexing Performance is slow. i.e ...

    • What we should check and fix if we get ‘Internal Server Error’

      Lot of times we suddenly get ‘Internal Server Error’ on the page as below. What all should we check and what we can fix? Most common reason for this screen is kibana is not able to reach Elasticsearch. You may want to check the cluster status.  If ...

    • AEPS || Unable to see the data in UI 725

      VuNet Systems Private Limited Solution Document Ticket #725 Overview General/Customer specific RBL Author Rachitha H V Reviewer Seema Approver Sendil Release date Product Version 8.5r5 Audience: CSG/TechWarriors/PAC/Platform/Product teams What’s the ...

    • SOP for Docker based VuSmartMaps

      Introduction This document aims to provide standard operating procedure to handle diagnostics and troubleshooting of VuSmartMaps container based installations. Assumptions This SOP assumes a container installation of vuSmartMaps catering to the new ...