Resolving Analytics Service Unexpectedly Stopped

Overview

The purpose of this article is to assist customers whose analytics service shuts down unexpectedly and without warning by providing information on the relevant log file that can be examined for details.

 

Prerequisites

  • Affected versions: All ScaleArc versions
  • Access to the ScaleArc instance via SSH
  • Either idb credentials 

 

Information

ScaleArc has a global Analytics service that spawns specific analytics processes per each cluster. The ScaleArc watchdog component continuously performs checks on the Analytics service and starts it automatically if necessary. 

The relevant log file for the Analytics service is located at: /data/logs/services/watchdog.log

Sample log entries:

2018-10-04 13:33:20,011 ERROR Component analytics is stopped, need to start now
2018-10-04 13:33:20,756 INFO Component analytics has started sucessfully
2018-10-04 13:35:51,822 ERROR Component analytics is stopped, need to start now
2018-10-04 13:35:52,424 INFO Component analytics has started sucessfully
2018-10-04 13:37:54,737 ERROR Component analytics is stopped, need to start now
2018-10-04 13:37:55,344 INFO Component analytics has started sucessfully

There is no action needed from the user to start the Analytics service. If the Analytics service is not working, please contact ScaleArc support.

Comments

0 comments

Article is closed for comments.