If the Exinda device is regularly crashing and the access can be recovered only after a power cycle, it might be because of NTP problems.
While reviewing the logs, the following errors appear:
pm: [pm.NOTICE]: Launched ntpd (NTP Daemon) with pid 12382
ntpd: ntpd firstname.lastname@example.org Fri Jul 24 10:56:17 UTC 2015 (1)
ntpd: proto: precision = 0.080 usec
pm: [pm.NOTICE]: Terminating process ntpd (NTP Daemon)
ntpd: ntpd exiting on signal 15
The Exinda failure is cascading from the NTP service to other processes like the schedule process and cron. When the RAM is fully occupied, the Exinda device crashes. This is usually caused by incorrect NTP server configuration.
To modify the NTP config:
- In Exinda WebUI, navigate to
Configuration > System > Setup.
- In the Date and Time tab > Add New NTP server section, specify the IP address or the hostname of the NTP server. You can specify the IP address of your DC (if joined to AD) or external services such as pool.ntp.org (https://www.pool.ntp.org/zone/<country_code>). Tick the "Enabled" option and save the configuration.
Alternatively, you can use
ntpdate CLI command. For more information, please refer to Force Time Sync Using an NTP Server.