| Interstage Shunsaku Data Manager Messages - Linux - |
|
Contents
Index
|
This chapter explains about the messages output to the system log.
Decide the messages to monitor for each job.
The following table shows the classification of messages that are output to the system log and the process that those messages will be output. The massages will be output to the system log of the servers that each process is located.
|
Classification |
Process type (*1) |
|---|---|
|
director |
|
|
director |
|
|
searcher |
|
|
searcher |
|
|
conductor |
|
|
sorter |
|
|
Common |
|
|
director |
|
|
conductor |
|
|
Common |
|
|
conductor |
|
|
conductor |
|
|
director |
|
|
searcher |
|
|
conductor |
*1) 'Common' means that the messages will be output either to conductor, director, searcher, or sorter.
It is recommended to monitor the messages that the error type is "ERROR" because this type of errors will notify the user that an error has occurred.
|
Classification |
Error type (*1) |
Message code |
Description |
|---|---|---|---|
|
|
INFO |
shn01001i |
The update function has been forcibly stopped. |
|
WARNING |
shn01002w |
The update function log file could not be opened. |
|
|
INFO |
shn01005i |
The update function log file has been switched. |
|
|
INFO |
shn01100i |
The initialization process has started. |
|
|
INFO |
shn01101i |
The director data file already exists in the directory which specified by the "DataFileFolder" parameter in the director environment file. |
|
|
INFO |
shn01102i |
The director data file already exists in the directory which specified by the "DataFileFolder" parameter in the director environment file |
|
|
INFO |
shn01103i |
A consistency check is being performed on the director data stored in the directory which specified by the "DataFileFolder" parameter in the director environment file. |
|
|
INFO |
shn01104i |
The consistency of the director data stored in the directory which specified by the "DataFileFolder" parameter in the director environment file is maintained. |
|
|
INFO |
shn01105i |
The director data file exists in the directory which specified by the "DataFileFolder" parameter in the director environment file. |
|
|
INFO |
shn01106i |
The director is waiting for connections to the searchers to be made. |
|
|
INFO |
shn01107i |
Connections to the searcher have been made. |
|
|
INFO |
shn01108i |
The number of searcher connections has reached the maximum number defined in the director environment file. |
|
|
INFO |
shn01109i |
The initialization process has completed. |
|
|
INFO |
shn01110i |
Connections to the searcher have been made. |
|
|
INFO |
shn01200i |
The termination process has started. |
|
|
INFO |
shn01201i |
A stop command has been sent to the searchers. |
|
|
INFO |
shn01202i |
The termination process has completed. |
|
|
INFO |
shn01300i |
The deletion of director data process has started. |
|
|
INFO |
shn01301i |
A batch delete command has been sent to the searchers. |
|
|
INFO |
shn01302i |
The deletion of director data process has completed. |
|
|
INFO |
shn01400i |
The update process has started. |
|
|
INFO |
shn01401i |
An update cancellation request from a command has been received. |
|
|
INFO |
shn01402i |
Update data is being imported. |
|
|
INFO |
shn01403i |
Update data is being written to the director data file. |
|
|
INFO |
shn01404i |
Information about numbers of receiving updates. |
|
|
INFO |
shn01405i |
Update data is being transmitted to the searchers. |
|
|
INFO |
shn01406i |
An update cancellation request has been sent to the searchers. |
|
|
INFO |
shn01407i |
Update data is being reflected. |
|
|
INFO |
shn01408i |
A request to execute update processing has been sent to the searchers. |
|
|
INFO |
shn01409i |
A request to cancel update processing has been sent to the searchers. |
|
|
INFO |
shn01410i |
The update process has completed. |
|
|
INFO |
shn01411i |
The update cancellation process has completed. |
|
|
INFO |
shn01500i |
The defined number of searchers is being changed. |
|
|
INFO |
shn01501i |
The defined number of searchers has been changed. |
|
|
INFO |
shn01600i |
The reallocation process has started. |
|
|
INFO |
shn01601i |
The reallocation process has completed. |
|
|
INFO |
shn01700i |
The condense process has started. |
|
|
INFO |
shn01701i |
The condense process has completed. |
|
|
INFO |
shn01900i |
The degradation process has started. |
|
|
INFO |
shn01901i |
The searcher is being switched to the alternative searcher. |
|
|
INFO |
shn01902i |
The degradation process has completed. |
|
|
INFO |
shn01903i |
Connections to the searcher have been broken. |
|
|
INFO |
shn01904i |
Switching to the alternative searcher. |
|
|
WARNING |
shn01906w |
The required searchers to operate are insufficient. |
|
|
|
ERROR |
shn02000e |
An error has occurred with communications processing. |
|
ERROR |
shn02001e |
There is not enough memory available. |
|
|
ERROR |
shn02002u |
Processing cannot continue because of an error with an OS system call. |
|
|
ERROR |
shn02003u |
A system error has occurred. |
|
|
ERROR |
shn02004u |
The director data file does not exist in the directory which specified by the "DataFileFolder" parameter in the director environment file. |
|
|
ERROR |
shn02005u |
The director data file does not exist in the directory which specified by the "DataFileFolder" parameter in the director environment file. |
|
|
ERROR |
shn02006u |
The director data file could not be opened. |
|
|
ERROR |
shn02007u |
The director data file could not be opened. |
|
|
ERROR |
shn02008u |
Could not write to the director data file. |
|
|
ERROR |
shn02009u |
Could not write to the director data file. |
|
|
ERROR |
shn02010u |
The director data file is corrupt. |
|
|
ERROR |
shn02011u |
Processing failed due to an OS system call error. |
|
|
ERROR |
shn02012u |
The director has terminated abnormally because it received a signal. |
|
|
ERROR |
shn02013u |
The core file has been collected. |
|
|
ERROR |
shn02014u |
The update function has terminated abnormally. |
|
|
ERROR |
shn02100u |
There is an error with the startup parameters. |
|
|
ERROR |
shn02101u |
The director could not be started because the director data file does not exist. |
|
|
ERROR |
shn02102u |
The director could not be started because consistency of the director data stored in the directory which specified by the "DataFileFolder" parameter in the director environment file could not be verified. |
|
|
ERROR |
shn02103u |
Could not open the director environment file. |
|
|
ERROR |
shn02104u |
There is an error with definitions in the director environment file. |
|
|
ERROR |
shn02105u |
Shared memory is being used by another system. |
|
|
ERROR |
shn02106u |
The director cannot start for one of the following reasons: |
|
|
ERROR |
shn02107u |
The specified shared memory is being used by another Shunsaku system. |
|
|
ERROR |
shn02108u |
The area in the TCP segment that indicates the port is a 16-bit number. |
|
|
ERROR |
shn02109u |
Resolving host name of the alternative searcher has been failed. |
|
|
ERROR |
shn02400u |
There is an error with the end-of-file marker in the extraction data file. |
|
|
ERROR |
shn02401u |
There was an error in judging whether the extraction data file is big- or little-endian. |
|
|
ERROR |
shn02402u |
There is an error with the RowID length for the extraction data file. |
|
|
ERROR |
shn02403u |
There is an error with the number of data items in the extraction data file. |
|
|
ERROR |
shn02404u |
There is an error with the command type for the extraction data file. |
|
|
ERROR |
shn02405u |
The specified data to be deleted does not exist. |
|
|
ERROR |
shn02406u |
The specified data to be updated does not exist. |
|
|
ERROR |
shn02407u |
The specified data to be inserted already exists. |
|
|
ERROR |
shn02408u |
A data inconsistency between the director and a searcher has occurred. |
|
|
ERROR |
shn02409u |
There is a not well-formed XML document (which may be 0 byte data). |
|
|
ERROR |
shn02410u |
There is an XML document that is not well-formed, or an error is in a character code. |
|
|
ERROR |
shn02412u |
The document number judged to be the error of the "shn02410u" displayed before this message is displayed. |
|
|
ERROR |
shn02413u |
An overflow has occurred. |
|
|
ERROR |
shn02414u |
Processing cannot continue because of the file system for the working directory is full. |
|
|
ERROR |
shn02415u |
There is an error in the file identification of the input file. |
|
|
ERROR |
shn02600u |
The director data file is corrupt. |
|
|
ERROR |
shn02700u |
The director data file is corrupt. |
|
|
ERROR |
shn02800e |
There is a syntax error in the specified search expression. |
|
|
ERROR |
shn02801e |
There is a syntax error in the specified return expression. |
|
|
ERROR |
shn02900e |
An error has occurred with a searcher. |
|
|
ERROR |
shn02901u |
Degradation processing failed because there was not enough memory. |
|
|
ERROR |
shn02902u |
Degradation processing failed because of an OS system call error. |
|
|
WARNING |
shn02903w |
Alternative searcher was not connected to the director. |
|
|
|
INFO |
shn03100i |
The initialization process has started. |
|
INFO |
shn03101i |
A request to clear data was received from the director. |
|
|
INFO |
shn03102i |
The initialization process has completed. |
|
|
INFO |
shn03103i |
An attempt to connect to the director has been refused. |
|
|
INFO |
shn03104i |
An attempt to connect to the socket for director searches has been completed successfully. |
|
|
INFO |
shn03105i |
An attempt to connect to the socket for director updates has been completed successfully. |
|
|
INFO |
shn03106i |
The initialization process has completed as an alternative searcher. |
|
|
INFO |
shn03107i |
The connection of alternative searcher and the director was completed. |
|
|
INFO |
shn03200i |
The termination process has started. |
|
|
INFO |
shn03201i |
The termination process has completed. |
|
|
INFO |
shn03300i |
A batch deletion request was received from the director. |
|
|
INFO |
shn03301i |
The batch deletion process has completed. |
|
|
INFO |
shn03400i |
An update request has been received. |
|
|
INFO |
shn03401i |
A request to cancel the update has been received. |
|
|
INFO |
shn03402i |
Information about numbers of receiving updates. |
|
|
INFO |
shn03403i |
An update execution request has been received. |
|
|
INFO |
shn03404i |
A request to cancel the update has been received. |
|
|
INFO |
shn03405i |
The update process has completed. |
|
|
INFO |
shn03406i |
The update cancellation process has been started. |
|
|
|
ERROR |
shn04000e |
An error has occurred with communications processing. |
|
ERROR |
shn04001e |
There is not enough memory available. |
|
|
ERROR |
shn04002u |
A system call has terminated abnormally. |
|
|
ERROR |
shn04003u |
A system error has occurred. |
|
|
ERROR |
shn04004u |
The searcher has terminated abnormally because it received a signal. |
|
|
ERROR |
shn04005u |
The core file has been collected. |
|
|
INFO |
shn04006i |
An error has occurred with communications processing at MyPort. |
|
|
INFO |
shn04007i |
An error has occurred in the communications processing of alternative searcher request. |
|
|
ERROR |
shn04100u |
There is an error with the startup parameters. |
|
|
ERROR |
shn04101u |
Could not open the searcher environment file. |
|
|
ERROR |
shn04102u |
There is an error with definitions in the searcher environment file. |
|
|
ERROR |
shn04103u |
A communication error with the director occurred during initialization. |
|
|
ERROR |
shn04104u |
The possible causes are as follows: |
|
|
ERROR |
shn04105u |
Shared memory is being used by another system. |
|
|
ERROR |
shn04106u |
The searcher cannot start for one of the following reasons: |
|
|
ERROR |
shn04107u |
The specified shared memory is being used by another Shunsaku system. |
|
|
ERROR |
shn04108u |
The area in the TCP segment that indicates the port is a 16-bit number. |
|
|
ERROR |
shn04400e |
The specified data to be updated does not exist. |
|
|
ERROR |
shn04401e |
The specified data to be deleted does not exist. |
|
|
ERROR |
shn04402e |
There is a not well-formed XML document. |
|
|
ERROR |
shn04800e |
There is a syntax error in the specified search expression. |
|
|
|
ERROR |
shn06000u |
A system error has occurred. |
|
ERROR |
shn06001u |
A system call terminated abnormally. |
|
|
ERROR |
shn06002u |
The conductor has terminated abnormally because it received a signal. |
|
|
ERROR |
shn06003u |
The core file has been collected. |
|
|
WARNING |
shn06004w |
The conductor log file for the conductor could not be opened for some reason. |
|
|
WARNING |
shn06005w |
An error occurred while log data was being written to the conductor log file. |
|
|
WARNING |
shn06006w |
Logs cannot be written to the conductor log file because the file system for the conductor log file is full. |
|
|
INFO |
shn06007i |
The conductor log file has been switched. |
|
|
ERROR |
shn06008u |
There is not enough local memory. |
|
|
INFO |
shn06009i |
The initialization process for the conductor has completed. |
|
|
INFO |
shn06010i |
The stop process for the conductor has completed. |
|
|
ERROR |
shn06011e |
It took longer to respond to the application than the time specified in the WaitTimer parameter in the conductor environment file. |
|
|
ERROR |
shn06012e |
The number of concurrent connections from applications has exceeded the value specified in the MaxConnection parameter in the conductor environment file. |
|
|
ERROR |
shn06013e |
An error occurred during communications with the application. |
|
|
ERROR |
shn06014e |
An error occurred during communications with the director. |
|
|
ERROR |
shn06015e |
An error occurred during communications with the sorter. |
|
|
ERROR |
shn06016e |
It took longer to respond to the application than the time specified in the WaitTimer parameter in the conductor environment file. |
|
|
|
INFO |
shn07001i |
The sorter has started initialization. |
|
INFO |
shn07002i |
The start process for the sorter has been completed. |
|
|
INFO |
shn07003i |
The termination process has started. |
|
|
INFO |
shn07004i |
The termination process has completed. |
|
|
ERROR |
shn07005u |
There is not enough memory available. |
|
|
ERROR |
shn07006u |
Processing cannot continue because of an error in an OS system call. |
|
|
ERROR |
shn07007u |
A system error has occurred. |
|
|
ERROR |
shn07008u |
There is an error with the startup parameters. |
|
|
ERROR |
shn07009u |
Failed to open the sorter environment file. |
|
|
ERROR |
shn07010u |
There is an error in the definitions in the sorter environment file. |
|
|
ERROR |
shn07011u |
Shared memory is being used by other systems. |
|
|
ERROR |
shn07012u |
The sorter cannot start for one of the following reasons: |
|
|
ERROR |
shn07013u |
The specified shared memory is being used by another Shunsaku system. |
|
|
ERROR |
shn07015u |
The sorter has terminated abnormally because it received a signal. |
|
|
ERROR |
shn07016u |
The core file has been collected. |
|
|
ERROR |
shn07017e |
An error has occurred with communications processing. |
|
|
ERROR |
shn07018e |
There is not enough memory available. |
|
|
ERROR |
shn07019u |
An overflow has occurred. |
|
|
ERROR |
shn07020u |
The total length of the sort key exceeded the upper limit. |
|
|
|
ERROR |
shn10001u |
The message control file does not exist. |
|
ERROR |
shn10002u |
An error occurred with a system call to the message control file. |
|
|
ERROR |
shn10003u |
A message control code was not found in the message control file. |
|
|
ERROR |
shn10004u |
An error occurred with a system call to the message control file. |
|
|
|
ERROR |
shn12003u |
The director environment file for the specified director identifier does not exist. |
|
ERROR |
shn12004u |
The director environment file contains a line that contains too many characters. |
|
|
ERROR |
shn12005u |
The same execution parameter is specified more than once in the director environment file. |
|
|
ERROR |
shn12006u |
There is an error in a value specified in a execution parameter of the director environment file. |
|
|
ERROR |
shn12007u |
There is an error with a value specified in a execution parameter in the director environment file. |
|
|
ERROR |
shn12008u |
A required execution parameter is missing from the director environment file. |
|
|
|
ERROR |
shn16000u |
The conductor environment file for the specified conductor identifier does not exist. |
|
ERROR |
shn16001u |
The director environment file for the specified director identifier does not exist. |
|
|
ERROR |
shn16002u |
An OS system call returned an error. |
|
|
ERROR |
shn16003u |
One of the lines in the conductor environment file is too long. |
|
|
ERROR |
shn16004u |
One of the lines in the director environment file is too long. |
|
|
ERROR |
shn16005u |
There was not enough memory when the conductor or director environment file was being loaded. |
|
|
ERROR |
shn16006u |
There is an error with the syntax of a execution parameter in the conductor environment file. |
|
|
ERROR |
shn16007u |
There is an error with the syntax of a execution parameter in the director environment file. |
|
|
ERROR |
shn16008u |
There is an error with a value specified in a execution parameter in the conductor environment file. |
|
|
ERROR |
shn16009u |
There is an error with a value specified in a execution parameter in the director environment file. |
|
|
ERROR |
shn16010u |
An identical execution parameter appears more than twice in the conductor environment file. |
|
|
ERROR |
shn16011u |
An identical execution parameter appears more than twice in the director environment file. |
|
|
ERROR |
shn16012u |
The conductor environment file contains an invalid execution parameter. |
|
|
ERROR |
shn16013u |
The director environment file contains an invalid execution parameter. |
|
|
ERROR |
shn16014u |
A required execution parameter is missing from the conductor environment file. |
|
|
ERROR |
shn16015u |
A required execution parameter is missing from the director environment file. |
|
|
ERROR |
shn16016u |
The director information appears more than once. |
|
|
INFO |
shn16017i |
The director has been added. |
|
|
INFO |
shn16018i |
The specified director has been deleted. |
|
|
INFO |
shn16019i |
The StartPoint parameter has been changed. |
|
|
ERROR |
shn16020e |
At least one director must be defined. |
|
|
ERROR |
shn16021u |
Failed to bind a socket. |
|
|
ERROR |
shn16040u |
The execution parameter in the conductor environment file did not match the execution parameter in the director environment file. |
|
|
|
ERROR |
shn30000u |
Shunsaku could not be started because there are too many Shunsaku processes running on the server. |
|
ERROR |
shn30001u |
A command that runs while Shunsaku is inactive cannot be executed due to one of the following reasons: |
|
|
ERROR |
shn30002u |
Shunsaku is not running. |
|
|
ERROR |
shn30003u |
There is not enough local memory. |
|
|
ERROR |
shn30004u |
A system call has terminated abnormally. |
|
|
ERROR |
shn30005u |
A system call has terminated abnormally. |
|
|
ERROR |
shn30006u |
Because the file system temporarily used by the system is full, the current processing cannot continue. |
|
|
ERROR |
shn30010u |
There is an error with one of the values specified with a execution parameter in the environment file. |
|
|
WARNING |
shn30019w |
Cannot output logs because there is not enough local memory. |
|
|
WARNING |
shn30020w |
Cannot output logs because the system call has terminated abnormally. |
|
|
WARNING |
shn30021w |
Cannot open or switch the log file due to an error. |
|
|
WARNING |
shn30022w |
An error occurred while the log file was being written. |
|
|
WARNING |
shn30023w |
Cannot write to the log file because the file system for the log file is full. |
|
|
WARNING |
shn30024i |
The log file has been switched. |
|
|
|
ERROR |
shn30100e |
The collection of connection information will be suspended because there is not enough memory. |
|
ERROR |
shn30101e |
The collection of connection information will be suspended because an I/O error has occurred while connection information was being output. |
|
|
ERROR |
shn30102u |
The conductor could not be stopped because all transactions were not complete within a certain time. |
|
|
ERROR |
shn30103u |
The conductor environment cannot be changed dynamically using the "shunccfgedit" command because the environment uses files. |
|
|
ERROR |
shn30106u |
The director has already been registered in a file. |
|
|
ERROR |
shn30107u |
The directory has not been registered with the conductor. |
|
|
ERROR |
shn30108u |
The specified domain information has been defined more than once. |
|
|
ERROR |
shn30109u |
The specified file information has been defined more than once. |
|
|
INFO |
shn30110i |
The director belonging to the file has been registered successfully. |
|
|
INFO |
shn30111i |
The domain has been registered successfully. |
|
|
INFO |
shn30112i |
The file has been registered successfully. |
|
|
INFO |
shn30113i |
The file belonging to the domain has been registered successfully. |
|
|
ERROR |
shn30114u |
Domain information does not exist. |
|
|
ERROR |
shn30115u |
File information does not exist. |
|
|
ERROR |
shn30116u |
The file has already been registered with a domain. |
|
|
ERROR |
shn30117u |
The specified sorter information already exists. |
|
|
INFO |
shn30118i |
The sorter has been added. |
|
|
ERROR |
shn30121u |
The DefaultFile parameter in the conductor environment file does not exist. |
|
|
ERROR |
shn30122u |
An attempt to connect to the file or domain has failed. |
|
|
ERROR |
shn30127u |
An internal message is invalid. |
|
|
ERROR |
shn30128u |
The connection could not be closed within a certain time. |
|
|
ERROR |
shn30134u |
There is an error in the specified director identifier in system environment file. |
|
|
ERROR |
shn30135u |
There is an error in the specified director number in system environment file. |
|
|
INFO |
shn30136i |
The InsertPoint parameter has been changed. |
|
|
ERROR |
shn30137u |
An attempt to connect to the Shunsaku has failed. |
|
|
ERROR |
shn30138u |
Cannot set _LAST_ in the InsertPoint parameter or StartPoint parameter because a director that hasn't been allocated a director number exists. |
|
|
ERROR |
shn30139u |
The specified director cannot be deleted because it is where data is to be inserted. |
|
|
ERROR |
shn30140u |
The specified director cannot be deleted because it hasn't been allocated a director number. |
|
|
ERROR |
shn30143u |
There is an error with the specified maximum number of hits. |
|
|
|
ERROR |
shn30204u |
There is an error in the specification of the start point or the end point of the data to be extracted. |
|
ERROR |
shn30205u |
The sorter to be started has not been defined in the system environment file. |
|
|
ERROR |
shn30206u |
An overflow has occurred. |
|
|
|
ERROR |
shn30300u |
There is an XML document that is not well-formed, or an error is in a character code. |
|
ERROR |
shn30301u |
The port number is already being used. |
|
|
ERROR |
shn30302u |
A system error has occurred. |
|
|
ERROR |
shn30303u |
There is not enough local memory in searcher. |
|
|
ERROR |
shn30304u |
"Director" information for the director to be started has not been specified in the system environment file. |
|
|
ERROR |
shn30305u |
"Searcher" information for the director to be started has not been specified in the system environment file. |
|
|
ERROR |
shn30306u |
An I/O error has occurred with a file in the director data folder. |
|
|
ERROR |
shn30307u |
An I/O error has occurred with a file in the operation log folder. |
|
|
WARNING |
shn30309w |
The recovery processing of the director data file might fail, because the operation log file is discontinuous. |
|
|
ERROR |
shn30310u |
The director data file is broken. |
|
|
ERROR |
shn30311u |
The operation log file is broken. |
|
|
INFO |
shn30312i |
Switching to the normal searcher. |
|
|
INFO |
shn30313i |
The switch processing was completed. |
|
|
ERROR |
shn30375u |
The character code used in the stored XML document differs from the CharacterCode parameter defined in the system environment file. |
|
|
ERROR |
shn30380u |
An overflow has occurred. |
|
|
ERROR |
shn30383u |
There is an error in the direct access key definition file. |
|
|
WARNING |
shn30391w |
The value smaller than the actual resource is specified in the execution parameter of the director environment file. |
|
|
WARNING |
shn30392w |
The number of stored records has reached the alarm point. |
|
|
ERROR |
shn30393u |
The addition processing has been stopped because the maximum record number will be exceeded if data is added. |
|
|
WARNING |
shn30395w |
The size of the director data file has reached the alarm point. |
|
|
ERROR |
shn30396u |
The size of the director data file to be used has reached the maximum. |
|
|
WARNING |
shn30397w |
The size of the operation log file to be used has reached the alarm point. |
|
|
ERROR |
shn30398u |
The size of the operation log file to be used has reached the maximum. |
|
|
|
ERROR |
shn30404u |
There is an error with one of the values specified with a execution parameter in the environment file. |
|
INFO |
shn30406i |
An error has occurred with communications processing at Port number that receives requests from the director. |
|
|
ERROR |
shn30407u |
A communication error with the director occurred during initialization. |
|
|
WARNING |
shn30409w |
The contents received from the director have been changed. |
|
|
|
ERROR |
shn30515u |
The "InsertPoint" parameter cannot be omitted because multiple directors have been defined. |
|
ERROR |
shn30541u |
Processing has failed due to an system call error to the operating system. |
|
|
ERROR |
shn30542u |
The command cannot be executed because either another command is executing or the director is still starting up. |
|
|
ERROR |
shn30562u |
There is not enough local memory. |
|
*1) There are the following three types of the error types:
INFO : Information
WARNING : Warning
ERROR : Error
|
Contents
Index
|
