SnapCenter plug-in loader does not start automatically when the host is restarted

Description

When the host is restarted, the SnapCenter plug-in loader (SPL) does not start automatically if there is no symbolic link in /user/bin/Java, or if Java is mounted from an external entity.

Error message

ERROR: JAVA_HOME is set to an invalid directory.
Failed to start SnapCenter Plugin Loader.

Corrective action

If the host is running on... Then...
init.d
  1. Create the spl configuration file at /etc/default/.
  2. Add export JAVA_HOME=path_where_java_is_mounted to the spl configuration file.
  3. Add [-f /etc/default/spl ] && . /etc/default/spl to the beginning of the SPL init script located at /etc/init.d/.
system.d
  1. Create the spl.conf configuration file at /etc/systemd/system/spl.service.d/.
  2. Add the following lines to the spl.conf configuration file:
    • Environment=JAVA_HOME=path_where_java_is_mounted
    • RestartSec=30
    • StartLimitInterval=200
    • StartLimitBurst=5
  3. After updating spl.conf, reload systemctl by running the systemctl daemon-reload command.
Parent topic: Troubleshooting data protection operations
Copyright © 1994-2019, NetApp, Inc. All rights reserved.
Part number: 215-14393_2019-10_en-us
October 2019
Updated for 4.2.1