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 cluster is fine, apache error logs or vusmartmaps logs can give some lead.
It seems there could be multiple cases:
- ES in the analyser may be down.
- Logstash in Analyser is down. Because of which, redis queue has build so much that a OOM is coming and DAQ/Mickey is not able to communicate at all. (We saw this in a customer environment).
So we should check:
- ES status in Analyser. If failed, restart.
- vuSmartMaps logs for errors.
- Redis Queue size. If very high, check logstash in analyser.
Related Articles
Unable to get appropriate server status through heartbeat-571
Solution Document ICICI || Unable to get appropriate server status through heartbeat Overview General/Customer specific General Author Ashna Rajput Reviewer Deepak,Tejaswi Approver Ravi Release date 20/09/2022 Product Version 8.5r5 Audience: ...Why do I see Internal Service Error (HTTP Response 500) after login?
There are two reasons because of which 500 Error can be seen. UI rendering service (kibana) is not running. Elasticsearch service is not running 1. UI Rendering Service Errors This can be checked using (vunetenv) vunet@ vunet-Pro:~$ sudo service ...Error in adding data enrichment entry 581
Solution Document Error in adding data enrichment entry Overview General/Customer specific General Author Niveditha Reviewer Seema Approver Sendil Release date 05/09/2022 Product Version 8.5r9 Audience: CSG/TechWarriors/PAC/Platform/Product teams ...Date Parse Failure Error while Parsing Access Log
There is date parse failure error while parsing this access log. Please suggest a solution for this date parse error. Answer: Your timestamp field has some extra ‘%{date}’ in the beginning. Please fix parsing. No need to add + before ‘Z’. Use ...I just configured a server with healthbeat agent but I don’t receive data in frontend. What could be wrong?
Ans - We have to check the following Check the logstash output and port are correct in the healthbeat YML file. Check the shipper side you have added the input file to accept connections to the port [Beats input] Check the connectivity between your ...