System Log Messages

The following messages are output to the Windows event log or Linux system log by the StateServer service to let you know the status of the service and to inform you of any errors that it encounters. Event messages are classified in one of three severity levels. Informational messages provide status information on the progress of the StateServer service. Warning messages alert you to abnormal conditions that require your attention but usually do not impede proper operation of the service. Error messages indicate serious problems that must be corrected for ScaleOut StateServer to resume normal operation. Some error conditions, such as brief network outages, correct themselves without user intervention.

ID Severity Message and Explanation
1 Info “The local StateServer service is starting.”
2 Info “The local StateServer service is stopping.”
3 Error
“The service failed to initialize with the Service Control Manager.”
Explanation: The Windows Service Control Manager (SCM) could not start the StateServer service. The most likely causes are: (1) ScaleOut StateServer was improperly installed, and the StateServer service was not registered with the SCM, or (2) the installation directory’s files have been deleted. You should reinstall ScaleOut StateServer on this system.
4(a) Error
“A network interface cannot be selected. No network interfaces are available.”
Explanation: No network interface was found. Check that your network interfaces are properly configured and operational. You must have at least one network interface to use ScaleOut StateServer. While the service runs, it will periodically poll for the selected network interface and will restart if the interface becomes available.
4(b) Error
“A network interface cannot be selected. No available network interface matches your net_interface and subnet_mask parameters. The loopback IP address (127.0.0.1) will be displayed while the service is running.”
Explanation: No network interface was found that matches your net_interface and subnet_mask parameters. Check that your network interfaces are properly configured and operational. You must have at least one network interface to use ScaleOut StateServer. While the service runs, it will periodically poll for the selected network interface and will restart if the interface becomes available.
5 Info
“The local StateServer service has selected the following network interface as its host id: …”
Explanation: Only one network interface was found, so it was automatically selected for use with the StateServer service. You should update the parameters file using the management tools with the host IP address or subnet.
6 Error
“The parameters file could not be read. The service is exiting.”
Explanation: The most likely causes are: (1) ScaleOut StateServer was improperly installed, and the registry key for the installation directory is missing, (2) the installation directory’s permissions or the parameters file’s permissions have been changed so that the local system account cannot write this file, or (3) the parameters file could have been deleted. If you do not have a backup copy of the soss_params.txt file, you should reinstall ScaleOut StateServer on this system.
7 Error
“An error occurred when writing to the parameters file.”
Explanation: The most likely causes are: (1) ScaleOut StateServer was improperly installed, and the registry key for the installation directory is missing or (2) the installation directory’s permissions or the parameters file’s permissions have been changed so that the local system account cannot write this file. You should reinstall ScaleOut StateServer on this system.
8 Error
“An error occurred when reading the parameters file. One or more parameter fields are invalid and will be replaced by default values.”
Explanation: The parameters file was corrupted so that it cannot be parsed by the StateServer service. If you do not have a backup copy of the soss_params.txt file, you should reinstall ScaleOut StateServer on this system.
9 Error
“An error occurred when reading the parameters file. A parameter value is invalid. Details: …”
Explanation: A parameter’s value is invalid and will be replaced by the parameter’s default value. You should review all parameters using the management tools and verify that they are set to the desired values.
10 Error
“The maximum number of licensed hosts has been exceeded. This host cannot join the store.”
Explanation: Your license key does not permit an additional host to join the store. Please contact ScaleOut Software to upgrade your license.
11 Warning
“The parameters file does not yet contain a user-specified host IP address or subnet. Please be sure to check and update these parameters.”
Explanation: You should select a host IP address or subnet using the management tools prior to using ScaleOut StateServer. If you have only one network interface, it will automatically be selected. However, you should always update the parameters file.
12 Info “The local host has started to join the distributed store.”
13(a) Error
“The local host failed to join the distributed store. The parameters and/or license key are not valid.”
Explanation: The local StateServer service cannot attempt to join the store because either you have an invalid license key and/or the parameters file was determined to be corrupted. Please correct these problems using the management tools.
13(b) Error
“The local host failed to join the distributed store. The selected network interface is not available.”
Explanation: The local StateServer service cannot attempt to join the store because it cannot detect the network interface you selected. (When this condition exists, the management console displays the local host’s IP address as 127.0.0.1.) Please correct the networking problem or select a different network interface using the management tools. Note that all store hosts must use the same network subnet.
13(c) Error
“The local host failed to join the distributed store. This host timed out waiting to join.”
Explanation: The local StateServer service detected a problem that delayed its joining the distributed store. Please restart the service on this host and then reattempt to join it to the store.
14 Info “The local host has successfully joined the distributed store.”
15 Error
“The local host has detected a network interruption.”
Explanation: The local host has determined that it cannot communicate with one or more of the hosts in the store. The StateServer service will now begin recovery actions. Please make sure that all network connections are working properly and that all hosts are running normally.
16 Error
“The local host is isolated from the network. The service is restarting.”
Explanation: The local host has determined that it cannot communicate with any other host in the store and must restart the local service to ensure correct recovery and healing of the store.
17 Info
“The local host has started healing the distributed store after a paused heartbeat link was detected.”
Explanation: The local host has determined that a network outage was detected, and it will now begin to heal the store so that full redundancy is re-established.
18 Info
“The local host has resumed normal operation after a network outage and/or host failure was handled.”
Explanation: The local host has resumed normal operation because either (1) the network outage was corrected before further recovery and healing was deemed necessary or (2) a failed host has been removed from the store and healing has been completed.
19 Info
“The local host is leaving the distributed store.”
Explanation: The local host’s StateServer service was issued a STOP command and will now leave the store.
20 Info
“Restarting the local StateServer service.”
Explanation: The local StateServer service will be restarted using the Windows service control manager due to a RESTART SVC command or a change to the parameters.
21 Error
“The local StateServer service cannot be programmatically restarted. Please stop and restart the service from the Service Control Manager. Detailed error:”
Explanation: The attempt to restart the StateServer service failed for unknown reasons, and the service must be restarted manually at this time. It is possible that ScaleOut StateServer will need to be reinstalled if the Windows service control manager database has become corrupted.
22 Error
“An internal error has occurred. Please contact technical support at ScaleOut Software for assistance.”
Explanation: The StateServer service encountered an internal error while performing a consistency check. Please contact ScaleOut Software at support@scaleoutsoftware.com to report the problem. Be sure to provide the full contents of the event log entry, including the two numeric values in the message.
23 Warning
“The parameters file does not yet contain a license key. Please be sure to enter a key so that the service can create or join a store.”
Explanation: The soss_params.txt file in the installation directory has no value for the license_key parameter. You should enter the license key you that you received from ScaleOut Software using either the console, command-line program, or a text editor. NOTE: ScaleOut StateServer requires a valid license key.
26(a) Error
“The local host failed to leave the distributed store. This host timed out waiting to leave.”
Explanation: The local StateServer service detected a problem that delayed its leaving the distributed store. Please restart the service on this host.
26(b) Error
“The local host failed to leave the distributed store. This host cannot leave because it is not active or already leaving.”
Explanation: After receiving a leave command, the local host has detected that it is unable to leave because it is either inactive or already starting to leave the store.
27 Info “The local host has successfully left the distributed store.”
28 Info
“The local StateServer service has detected a network interface that matches the selected net_interface and subnet_mask parameters. The service will now restart so that the network interface can be used.”
Explanation: When the local StateServer service was started, the selected network interface was not available. The service has now detected the network interface and needs to restart so that it can be used.
29 Info
“The local StateServer service has obtained a newer valid license key from another host to replace its key and will write this key to the parameters file.”
Explanation: After startup, the StateServer service detected another host with a newer, valid, non-null license key, and this key will be recorded and used. After you enter a license key one time, this behavior automatically records it on all additional hosts.
30 Warning
This host has more than 254 network interfaces; only the first 254 interfaces will be shown in the host list.
Explanation: ScaleOut StateServer supports up to 254 network interfaces on each server. If the local host has more than 254 interfaces, only the first 254 reported by the operating system will be shown in the host list.
31 Error
Another distributed store with an earlier creation time has been detected on the subnet. This host will restart.
Explanation: The local StateServer service created or joined a store while the network was isolated from another set of hosts that have previously formed another distributed store. After the network was reconnected, all hosts detected each other, and the distributed store with the earliest creation time has been chosen to survive. All other hosts on the network log this message and restart the StateServer service so that they can join the store.
32 Error
This host’s version is incompatible with the store; the host cannot join the store.
Explanation: Each version of ScaleOut StateServer maintains a version number to which it is backwards compatible. A host is not allowed to join a distributed store with which it is not backwards compatible. Otherwise, unpredictable behavior would result which could affect the stability of the distributed store.
33 Error
The store has detected possible loss of data due to multiple server failures.
Explanation: Multiple server failures or a network outage may have caused all of the replicas for some objects to have been lost. The StateServer service will continue operations even though the lost data is no longer available.
This situation also can occur if a network outage (e.g., a switch failure or a lost connection between network switches) causes a subset of hosts to become isolated from another subset. ScaleOut StateServer maintains service whenever possible even after catastrophic failures that may cause some data to be lost. NOTE: Loss of data may affect the load-balance between servers so that some servers have more stored data than others. This situation usually can be cleared by restarting all servers in the distributed store.
34 Info
(GeoServer Option) The local host has started synchronization and replication to remote store <remote store name>.
Explanation: Replication was started to the specified remote store on all hosts, and this host is now starting synchronization of the local store’s contents and replication of updates. Note that replication can be started by a management command, or it can be automatically started when the local store is joined.
35 Info
(GeoServer Option) The local host has started replication to remote store <remote store name>.
Explanation: Replication was started to the specified remote store on all hosts, and this host is now starting replication of updates to the local store. Note that replication can be started by a management command, or it can be automatically started when the local store is joined.
36 Info
(GeoServer Option) The local host has stopped replication to remote store <remote store name>.
Explanation: Replication was stopped to the specified remote store on all hosts, and this host is now stopping replication. Replication is stopped by a management command.
37 Warning
(GeoServer Option) The local host has suspended replication to remote store <remote store name> because it cannot reach the remote store.
Explanation: Replication was temporarily suspended to the specified remote store on all hosts, and this host is now suspending replication. Replication is suspended when the local store cannot reach a remote store to replicate an object update. Replication is automatically resumed after communications have been re-established with the remote store.
When this situation occurs, you should check that the network connection to the remote store has not failed. Also check that at least one host in the remote store is operational. This problem should be corrected quickly because the local store will consume additional memory to buffer outgoing object updates until these updates can be sent.
38 Info
(GeoServer Option) The local host has resumed replication to remote store <remote store name>.
Explanation: Replication was resumed to a remote store after a temporary suspension. Replication is suspended when the local store cannot reach a remote store to replicate an object update. After resumption, replication returns to a normal operational status.
39 Error
The local host has persisted in a not-ready state and must restart to heal the store.
Explanation: The local host has detected that it has persisted for an abnormal time period in a not-ready state. Restarting this host should clear the condition and allow the distributed store to heal.