|
|
|
There are situations in which an attempt to start a FairCom DB process can fail. A failed server startup can be detected by examining the list of processes running on the system. If ctsrvr (the name of the server binary) is not shown as a running process after the server is started, the server startup has failed.
The ps or pgrep utilities can be used on Unix systems to list active processes.
The Windows Task Manager can be used on Windows system to list active processes.
In the event of a failed FairCom DB startup, the server logs error messages to CTSTATUS.FCS and sometimes to the server console. Check for errors in these locations first in order to understand the reason the server failed to start. If FairCom DB has successfully started in the past, consider what might have changed since the last successful server startup (such as server configuration file options, server binaries, etc.).
The following are possible causes of a failed server startup:
|
|
|
If FairCom DB (c-tree server versions V9 and prior) is not pre-activated by FairCom, it must be activated before it is started. If an unactivated server is started, the server writes the following message to CTSTATUS.FCS and terminates:
Thu Sep 25 15:42:38 2003
- User# 01SERVER NEEDS ACTIVATION KEY!
Execute 'fcactvat' program first
To resolve this type of failed startup, activate the c-tree Server using the c tree Server Activation Utility. (DEPRECATED: only applies to c-tree Server versions 9 and prior)
|
|
|
The server may fail to start if the server configuration file is missing or contains settings that are inconsistent with those used previously when starting FairCom DB. For example, if the server configuration file specifies a PAGE_SIZE setting that differs from the setting used when the server created its FAIRCOM.FCS file, the server is unable to open FAIRCOM.FCS and server startup fails. In this situation, the server logs error details to CTSTATUS.FCS.
To resolve this type of failed startup, review the startup errors logged to CTSTATUS.FCS and start the server using a server configuration file with the appropriate configuration settings.
|
|
|
If the server configuration file used when starting FairCom DB contains a keyword that is used incorrectly or is not recognized, FairCom DB fails to start up. The example below shows the messages logged to CTSTATUS.FCS when an unrecognized keyword <unrecognized_keyword> is specified in the server configuration file:
Thu Sep 25 16:45:06 2003
- User# 01DO NOT RECOGNIZE CONFIGURATION KEYWORD...: 2
Thu Sep 25 16:45:06 2003
- User# 01<unrecognized_keyword>: 2
Thu Sep 25 16:45:06 2003
- User# 01O1 M2 L73 F9 P0x (recur #1) (uerr_cod=0)
To resolve this type of failed startup, review the errors logged to CTSTATUS.FCS and make the appropriate changes to the server configuration file.
|
|
|
FairCom DB will fail to start if it is unable to open its administrative files, which include the files FAIRCOM.FCS, SYSLOGDT.FCS, and SYSLOGIX.FCS. In this situation, check the server status log and look for a message such as the following:
Wed Oct 1 12:34:25 2003
- User# 01 Could not initialize server. Error: 14
If the server fails to start up and logs this message to the server status log, attempt to open FAIRCOM.FCS, SYSLOGDT.FCS, and SYSLOGIX.FCS to determine which of these files failed to open. The files SYSLOGDT.FCS and SYSLOGIX.FCS are the server’s event logs. If the server fails to open the files they can be safely deleted if their contents are not of interest, or they can be rebuilt, or they can be moved out of the server directory and the server will re-create these files during server startup. The file FAIRCOM.FCS contains user and group definitions. If the sever fails to open the files and the server’s default user and group account settings have not been changed, FAIRCOM.FCS can be deleted and the server will re-create it during server startup. If the server administrator has made changes to the user and group accounts settings, rebuild this file or restore it from backup.
If the message shown below appears in the server status log, the server was not able to open FAIRCOM.FCS because the current PAGE_SIZE setting differs from the page size used when FAIRCOM.FCS was created.
Wed Oct 01 12:46:38 2003
- User# 01 Could not process User/Group Information: 417
To correct this problem, change the PAGE_SIZE setting to the correct value, use the ctscmp utility to change the page size for FAIRCOM.FCS, or delete FAIRCOM.FCS.
If the server fails to start due to a failure to open its administrative files, consider adding DIAGNOSTICS LOWL_FILE_IO to the server configuration file. This diagnostic option causes the server to log messages showing filenames and system error codes for failed file open/close/delete/create/rename operations to the server status log.
|
|
|
The c tree Server can fail to start if the server binary is missing or in the case of the Windows server if a required communication DLL is missing. If the server binary is missing, the system command used to start the server typically outputs a message indicating that the binary was not found. In the event of a missing communication DLL, CTSTATUS.FCS shows a message such as the following:
Thu Sep 25 15:15:58 2003
- User# 01 F_TCPIP: 145
Thu Sep 25 15:15:58 2003
- User# 01 Could not establish logon area. Error: 143
To resolve this type of failed startup, review the startup errors reported by the server startup command or logged to CTSTATUS.FCS and copy the necessary binaries to the server’s working directory.
|
|
|
If FairCom DB is unable to initialize its communication subsystem at startup, it will terminate with an error. Examples of this type of failure include a missing communication DLL (as discussed above), improper system configuration for the specified communication protocol, or unavailable communication resources (for example, the TCP/IP port the server is attempting to use is already in use or otherwise unavailable).
To resolve this type of failed startup, review error messages logged to CTSTATUS.FCS to determine the reason for the failure. Correct the problem and restart the server.
|
|
|
Some versions of FairCom DB are require an encrypted server settings file to exist at startup. A server that requires a settings file will terminate at startup if the settings file is missing or if the server cannot read the settings file. In this situation, the server writes one of the following messages to CTSTATUS.FCS:
Thu Sep 25 16:41:10 2003
- User# 01 The Server's settings file is missing.
It is required to operate this server.
Thu Sep 25 16:42:01 2003
- User# 01 The current Server's settings file is invalid.
Use current FairCom utility to recreate the settings file.
To resolve this type of failed startup, review error messages logged to CTSTATUS.FCS. Make available to the server a good copy of the encrypted settings file and restart the server.
|
|
|
Each time FairCom DB starts, it examines its transaction logs to determine whether or not it needs to perform automatic recovery of TRNLOG files. The server automatically performs automatic recovery if it determines automatic recovery is required. When automatic recovery is successful, the server continues its normal startup processing. If automatic recovery fails, FairCom DB logs an error message to CTSTATUS.FCS and terminates.
To resolve this type of failed startup, review the error messages logged to CTSTATUS.FCS and take the appropriate action. See the "Automatic Recovery Fails" section in this chapter for a discussion of specific types of automatic recovery failures and what to do in each case.
|
|
|
Two FairCom DB instances cannot be running in the same working directory at the same time.
Note: Here the working directory refers to the directory in which the server stores its transaction logs and other *.FCS files.
If a server attempts to start in a directory in which another server is already running, the server fails to start up and logs the following error message to CTSTATUS.FCS:
Thu Sep 25 16:38:15 2003
- User# 01 Is another server running in this workspace?
Thu Sep 25 16:38:15 2003
- User# 01 O1 M99 L54 F537 P1x (recur #1) (uerr_cod=0)
To resolve this type of failed startup, shut down the running server or configure FairCom DB to start in a different working directory, then start FairCom DB.
|
|
|
If the server configuration file includes the DUMP keyword, the server opens the specified dynamic dump script file and attempts to schedule a dynamic dump. If the dump cannot be scheduled (for example, due to a missing dump script or a dump script with incorrect or unrecognized keywords), the server logs an error message to CTSTATUS.FCS and shuts down. Below is an example showing errors logged to CTSTATUS.FCS when a dynamic dump cannot be scheduled at server startup because the dump script file does not exist:
Thu Sep 25 16:48:43 2003
- User# 01 DD: could not open script file...: 12
Thu Sep 25 16:48:43 2003
- User# 01 my.scr: 12
Thu Sep 25 16:48:43 2003
- User# 01 Could not schedule Dynamic Dump...: 5
Thu Sep 25 16:48:43 2003
- User# 01 my.scr: 5
To resolve this type of failed startup, review the error messages logged to CTSTATUS.FCS to understand the specific cause of the failure. Correct the problem that prevented the scheduling of the dynamic dump and restart the server.
|
|
|
In addition to the specific causes of a failed server startup, FairCom DB may terminate abnormally at startup for the following reasons:
If a server startup terminates abnormally, follow these steps:
