A Snaplex node checks its configuration on initialization to ensure there are no issues that may affect operations. Any issues found during this check are raised as alerts. All alerts should be addressed before attempting to execute pipelines.
Alerts are visible in the Snaplex Health section of the Dashboard. A Snaplex that has a misconfigured node will be highlighted in orange. You can then select the Snaplex and go to the node's "Alerts" tab to view the alerts. The following is a list of the possible alerts, additional details, and ways to fix the configuration issue.
Large clock skew
- Details: The Snaplex node's clock must be in sync with the time on the cloud servers and other nodes in the Snaplex.
- Resolution: Configure the Snaplex node's operating system to synchronize its clock with a time server.
- Reference: Groundplex Requirements
Cannot bind to "..." network port ...
- Details: By default, the Snaplex node listens on network ports in the 8080 to 8090 range. If another service is listening on those ports, the Snaplex software cannot startup properly.
- Resolution: Stop the other service or change the ports that the Snaplex software will use.
- Reference: Configuration Options
Memory size is too small
- Details: The configured heap size for the Snaplex node's JVM is too small.
- Resolution: Update the "jcc.heap.max_size" property in the "global.properties" file.
- Reference: Configuration Options
JVM max memory size is more than the physical memory
- Details: The Snaplex node's JVM heap size is more than the host machine's physical memory size which can lead to suboptimal performance.
- Resolution: Reduce the JVM heap size or increase the host machine's memory size.
- Reference: Configuration Options
Maximum number of file descriptors is too low
- Details: On Linux, file descriptors are used to open files and make network connections. Not enough descriptors can cause errors while executing pipelines.
- Resolution: Configure the operating system and ulimit to set the maximum to 4096.
Insufficient number of processors
- Details: At least two processors are required.
- Resolution: Install on a machine with more than one processor.
- Reference: Groundplex Requirements
Local path has incorrect permissions: ...
- Details: The Snaplex software needs to read/write files under its installation directory.
- Resolution: Update the permissions on the directories mentioned in the alert.
Unable to reach Snaplex neighbor: ...
- Details: A node is having trouble communicating with another.
- Resolution: Examine the node in question for availability.
The current Snaplex war version is deprecated...
- Details: A Snaplex is running a deprecated version.
- Resolution: Update to the recommended Snaplex war version listed in the alert.
This node shares a jetty certificate with at least one other node. Nodes sharing this certificate: ['..........']
- Details: Multiple nodes are using the same jetty certificate/key (
jcc-serverkeys.jks and jcc-serverkeys.pass). This occurs when the certificate is copied from JCC node to another. - Resolution: Ensure that you use a different jetty certificate/key on each node.
The org-specific CC user should be used instead of bad-cc-user@example.com.
Details: The incorrect user was used in the jcc.properties file.
Resolution: Update the correct user in the Global Properties on the Snaplex Node Properties tab.
Reference: Updating a Snaplex.
See Also