Version 5.3.02 - Serendipity Software

Troubleshooting
Clustering
Here are some suggestions of where to look if you run into trouble and experience problems when using a Cluster.
Jobs Not Processing Through a Cluster Node
The possible reasons for this are:
• The Cluster Node is not configured to image, render or both. Check the ClusterStatus to see if either of the
processing tasks have been disabled. To enable them, open the Clustering Application and enable the
appropriate task.
• The Cluster Node has a Processing Pool attached and the Pagesetup you are submitting jobs to is not contained
within the Pool. You can either unselect the Pool or add the Pagesetup to the Pagesetup Pool.
• The Cluster Node has gone offline. To check, open the Clustering Application and check the node. If the
Clustering Application is already open, click the Refresh button. This will check for node status. If the node
appears grayed out or disabled, this indicates the node is not currently online.
Here the Cluster Node called “pomelo” is currently offline. In this
case, you would check the node server is up, the machine is still
connected to the network and can see the Master. If there is a
problem with the node, check the error log. One the problem is
resolved, click the Refresh button or close and reopen the Clustering
Application.
• The Node and Master are different versions. The node
should always be upgraded when the Master is to maintain the same versions in a Cluster.
Cluster Nodes Errors Log
The Cluster Nodes create an error log, which logs all the messages from the node. This is located in the Veripress
installation directory on the node’s own machine and is called “errors.log”. This can be viewed with a normal text editor
and can help to track a problem, or it can be sent to support for assistance in tracing a problem.
A Node Cannot Be Found
Once you have started your node successfully, you should be able to see it in the Clustering Application. If not, you need
to add the node manually. If this fails, there are a few things to check:
• Verify the node is still running and the clock is still counting up.
• Check the error log for any messages.
• Check that the Master machine can ping the node machine. If not, there may be a network issue and you will
need to contact your network administrator for assistance.
• Check the ports on the machines are open for the node to connect to the Master and they are not being used by
anything else. The port numbers for the node are as follows:
o 9103/tcp – Server connects here and submits jobs via this port.
o 9103/udp – Listens to broadcasts so the Server can enumerate available Node Servers.
• Make sure the node is the same version as the Master. Nodes (Veripress Slaves) should always be upgraded at
the same time as the Master.
Serendipity Software -­‐ Veripress User Manual – Version 5.3.02
119