The following table contains core application messages and codes from the job detailed history and from the logs . Data is sorted numerically by code.
Code
|
Job Detailed History
|
Error Log
|
Possible Cause(s)
|
|---|
3000
|
|
IConstantsFES.ERR_CCM_NONE
|
No Error
|
3001
|
Unknown error.
|
FES.ERR_CCM_UNKNOWN
|
Unspecified error condition.
|
3002
|
Assignment Creation Failed.
|
FES.ERR_CCM_ASSGN_CREATE_FAILED
|
Error determining assignment changes. Files not readable. Disk accessibility.
|
3003
|
Availability Quorum Failed.
|
FES.ERR_CCM_PREQUORUM_FAILED
|
Not enough nodes reported online to meet availability quorum. Nodes offline/unreachable.
|
3004
|
Commit Quorum Failed.
|
FES.ERR_CCM_QUORUM_FAILED
|
Not enough nodes processed to commit assignment. Nodes offline/unreachable. Nodes failed for local reason.
|
3005
|
Transport Channel Creation Failed.
|
FES.ERR_CCM_CHANNELS_FAILED
|
Problem attempting to setup multicast channels. GLs offline/unreachable.
|
3006
|
Workspace Update Failed.
|
FES.ERR_CCM_WORKSPACE_UPDATE_FAILED
|
Failure updating shadow after publish. Possible disk space, permission issues.
|
3007
|
Initialization Failed.
|
FES.ERR_CCM_INIT_FAILED
|
Could not create assignment directory. Problems accessing database.
|
3008
|
Assignment Timed Out.
|
FES.ERR_CCM_ASSGN_TIMEOUT
|
GLs not reporting progress.
|
3009
|
User Aborted.
|
FES.ERR_CCM_USER_ABORT
|
User aborted assignment.
|
3010
|
Disk Space Availability Failure
|
FES.ERR_CCM_LOW_SPACE
|
Running low on disk space.
|
3011
|
No Destinations for Assignment.
|
FES.ERR_CCM_NODESTS
|
Core application found no nodes to push to. Possible database problem, destination group issue.
|
3012
|
No Journal file found for Repush.
|
FES.ERR_CCM_REPUSH_NOSNAP
|
Could not find a JournalFile to perform repush. Failed to access db, file was deleted by user.
|
3013
|
No Target found for Repush.
|
FES.ERR_CCM_REPUSH_NOTARG
|
Could not find a node to repush to. Failed to access db, db has no info.
|
3020
|
Removal of Temporary Channels Failed.
|
FES.ERR_CCM_TMPCHANCLEANUP
|
Failed to remove a temporary mcast channel. Not a fatal error but a warning. Could not contact GL.
|
3024
|
A Required file was not found.
|
FES.ERR_CCM_FILENOTFOUND
|
Disk accessibility, file removed by another process.
|
3025
|
The Shadow Directory Does Not Exist.
|
FES.ERR_CCM_NOSHADOW
|
Failed to create, disk accessibility.
|
3026
|
The Directory does not Exist
|
FES.ERR_CCM_DIR_NOEXIST
|
Failed to create, disk accessibility.
|
3027
|
The Specified Object is not a Directory.
|
FES.ERR_CCM_DIR_NOTDIR
|
A file by that name already exists in the file system and it is not a directory.
|
3028
|
No Read Permission to this Directory.
|
FES.ERR_CCM_DIR_NOTREAD
|
Disk accessibility - can't read.
|
3029
|
No Write Permission to this Directory.
|
FES.ERR_CCM_DIR_NOTWRITE
|
Disk accessibility - can't write.
|
3030
|
Could not create Workspace.
|
FES.ERR_CCM_WORKSPACE_NOCREATE
|
Disk accessibility - can't write/read.
|
3031
|
Insufficient Access to Workspace.
|
FES.ERR_CCM_WORKSPACE_INSUFFICIENTP ERMS
|
Disk accessibility - can't write/read.
|
3032
|
No Snapshot Detected.
|
FES.ERR_CCM_NOFILERSNAP
|
Snapshots not enabled, out of snapshots.
|
3033
|
Could not find the assignment dir.
|
FES.ERR_CCM_NOASSIGNDIR
|
Disk accessibility, can't read/write. Configuration problem.
|
3034
|
The CDFES service was shutdown.
|
FES.ERR_CCM_SERVICESHUTDOWN
|
The CDFES service was shutdown. Network or servlet issues.
|
3035
|
Could not communicate with GrpLdr.
|
FES.ERR_CCM_TRANSPORTEXCEPTION
|
Could not communicate with GL. GL down/unreachable. Servlet problem.
|
The following table contains messages from the job detailed history and codes from the logs and Status window of the main screen. Data is sorted numerically by code.
Code
|
Message
|
Possible Cause(s)
|
|---|
13
|
No disk space.
|
Running low on disk space.
|
14
|
Time out expired.
|
No response from target. Possible network/connectivity issues.
|
15
|
Invalid parameters.
|
Possible configuration problem.
|
17
|
Not enough memory.
|
Running low on memory.
|
18
|
DNS error.
|
DNS misconfigured, not available.
|
6001
|
Failed to open URL.
|
Attempt to open a socket for content assignment (CA) fetch failed.
|
6002
|
URL connection failed.
|
An I/O Exception raised while attempting to issue HTTP GET for content assignment (CA) fetch.
|
6003
|
File size is zero.
|
Caller passed a zero (or negative) file size parameter to assignment fetch logic (sendCA()). Value must be positive and greater than zero.
|
6004
|
Content is written short.
|
The thread that GCDP started to fetch a given content assignment (CA) received less than the expected number of bytes.
|
6005
|
Unknown exception thrown for receiver.
|
An unanticipated exception was raised during execution of assignment fetch logic (sendCA()).
|
6006
|
Http get failed.
|
Non-success status was returned in HTTP header in response to HTTP GET. It should be "200 OK" but was not. Content assignment cannot be fetched.
|
6007
|
No fetch because of no output stream.
|
MCTP returned a null output stream reference. A valid non-null such reference is required for assignment fetch logic (send)CA()) to transfer the incomong HTTP stream up to MCTP for multicast distribution.
|
6008
|
Remote service unreachable for receiver.
|
Cannot make contact with remote service for MCTP to issue either an asynchronous completion of a request or an unsolicited status notification to core application.
|
8002
|
Channel not found.
|
Core application attempts to push job to channel that GL does not have. Possible problem with database relating group to GL channels or possibly problem with core application creating/communicating channels to use to GL.
|
8003
|
Content assignment not found.
|
Core application asks to abort or asks status on assignment that GL does not have any knowledge of. GL might not be able to contact core application to report status and has aborted or completed already without informing core application.
|
8005
|
No report.
|
|
8007
|
Back End Server is down.
|
Cache is not responding to ping requests and was eliminated from push because of this make sure CDA is started on cache.
|
8019
|
MCTP client timed out.
|
GM doesn't return status information during data transmission in about 50 sec. The GM is probably not functioning.
|
8020
|
MCTP retransmission count exceeded.
|
GM cannot get all the data within a data burst during data transmission after several retransmissions. Probable reason is that channel loss rate is extremely high.
|
8021
|
MCTP client window stale.
|
The data delivered to a GM are not processed in timely manner.
|
8022
|
MCTP client stream closed.
|
GM discontinued data reception. Any assignment processing error can cause this.
|
12003
|
Content verification failed.
|
When verification is turned on, this means it failed. Corrupted assignment.
|
12004
|
Security alert, possibly MasterKey mismatch.
|
Masterkey mismatch.
|
12007
|
I/O Error while reading/writing to cache.
|
Socket connection to cache was closed for some reason. Something in the push header indicates that the object is not cacheable, such as .cgi, ? in filename, streaming push with non-streaming object, wrong content-type for streaming object.
|
12013
|
Content Interpreter thread died unexpectedly
|
Any unexpected event. Check the CDLog.Systemerr.log for more detail.
|
12015
|
Content assignment not supported.
|
Abort an assignment that can't be aborted, such as commit.
|
12017
|
Command buffer not found.
|
Assignment header is corrupted, or no disk space on cache to extract command buffer.
|
12021
|
Unknown assignment command.
|
Command buffer corrupted, or core application is a totally new version with new commands that the GM does not understand.
|
12022
|
CI/DP registration failed
|
Obsolete cd.zip file present on NetCache. Delete cd.zip if exists in /etc/java in cache.
|
12023
|
Cache quorum not met.
|
Completion criterion is set for quorum and it is not met. Check xml log for exception details.
|
12024
|
Group Member type unknown.
|
Config incorrect, check registry.
|
12025
|
Command buffer invalid.
|
Command buffer corrupted, or core application is a total new version with new commands and arguments that GM does not understand.
|
12026
|
Failed connecting to cache.
|
Cannot make connection to cache on loop back.
|
12027
|
System error.
|
Occurs only on upgrade GM from core application, failed exec command on cache.
|
12028
|
I/O Error on Streaming, incorrect number of bytes sent
|
GL or core application aborted the assignment.
|
12030
|
Content assignment header not found for payload.
|
PUB failed for that assignment but the payload still sent. Check disk space on cache.
|
12031
|
Content event unknown.
|
Core application is a totally new version with new events that GM does not understand
|
12400
|
Failed to cache object, Bad request.
|
Return code 400 from cache, check push header in xml file log.
|
12500
|
Failed to cache object.
|
Return code 500 from cache, check log.
|
12510
|
Cache content fill error.
|
Return code 510 from cache, many causes, such as disk space, non-cacheable object, corrupted streaming file.
|
15001
|
Property file not found.
|
One or both of two possible virtual site property files is not where system expects it to be.
|
15007
|
Unknown exception thrown.
|
An unanticipated exception was raised during execution of cache registry gathering and reporting logic.
|
15008
|
Number format exception thrown.
|
Unanticipated non-numeric data encountered during execution of cache registry gathering and reporting logic.
|
15009
|
Property file data invalid.
|
Ill-formatted or unexpected data found in one or both of two possible virtual site property files.
|
15010
|
Gigo exception thrown.
|
A call to an AgentStorage interface method was made before AgentStorage data is fully populated and ready to return valid data.
|
The following table contains messages from the job detailed history and codes from the logs and Status window of the main screen. Data is sorted alphabetically by message.
Message
|
Code
|
Possible Cause(s)
|
|---|
No disk space.
|
13
|
Running low on disk space.
|
Time out expired.
|
14
|
No response from target. Possible network/connectivity issues.
|
Invalid parameters.
|
15
|
Possible configuration problem.
|
Not enough memory.
|
17
|
Running low on memory.
|
DNS error.
|
18
|
DNS misconfigured, not available
|
Failed to open URL.
|
6001
|
Attempt to open a socket for content assignment (CA) fetch failed.
|
URL connection failed.
|
6002
|
An I/O Exception raised while attempting to issue HTTP GET for content assignment (CA) fetch.
|
File size is zero.
|
6003
|
Caller passed a zero (or negative) file size parameter to assignment fetch logic (sendCA()). Value must be positive and greater than zero.
|
Content is written short.
|
6004
|
The thread that GCDP started to fetch a given content assignment (CA) received less than the expected number of bytes.
|
Unknown exception thrown for receiver.
|
6005
|
An unanticipated exception was raised during execution of assignment fetch logic (sendCA()).
|
Http get failed.
|
6006
|
Non-success status was returned in HTTP header in response to HTTP GET. It should be "200 OK", but was not. Content assignment cannot be fetched.
|
No fetch because of no output stream.
|
6007
|
MCTP returned a null output stream reference. A valid, non-null such reference is required for assignment fetch logic (send)CA()) to transfer the incomong HTTP stream up to MCTP for multicast distribution.
|
Remote service unreachable for receiver.
|
6008
|
Cannot make contact with remote service for MCTP to issue either an asynchronous completion of a request or an unsolicited status notification to core application.
|
Channel not found.
|
8002
|
Core application attempts to push job to channel that GL does not have. Possible problem with database relating group to GL channels or possibly problem with core application creating/communicating channels to use to GL.
|
Content assignment not found.
|
8003
|
Core application asks to abort or asks status on assignment that GL does not have any knowledge of. GL might not be able to contact core application to report status and has aborted or completed already without informing core application.
|
No report.
|
8005
|
|
Back End Server is down.
|
8007
|
Cache is not responding to ping requests and was eliminated from push because of this make sure CDA is started on cache
|
MCTP client timed out.
|
8019
|
GM doesn't return status information during data transmission in about 50 sec. The GM is probably not functioning.
|
MCTP retransmission count exceeded.
|
8020
|
GM cannot get all the data within a data burst during data transmission after several retransmissions. Probable reason is that channel loss rate is extremely high.
|
MCTP client window stale.
|
8021
|
The data delivered to a GM are not processed in timely manner.
|
MCTP client stream closed.
|
8022
|
GM discontinued data reception. Any assignment processing error can cause this.
|
Content verification failed.
|
12003
|
When verification is turned on, this means it failed. Corrupted assignment.
|
Security alert, possibly MasterKey mismatch.
|
12004
|
Masterkey mismatch.
|
I/O Error while reading/writing to cache.
|
12007
|
Socket connection to cache was closed for some reason. Something in the push header indicates that the object is not cacheable, such as .cgi, ? in filename, streaming push with none streaming object, wrong content-type for streaming object.
|
Content Interpreter thread died unexpectedly
|
12013
|
Any unexpected event. Check the CDLog.Systemerr.log for more detail.
|
Content assignment not supported.
|
12015
|
Abort an assignment that can't be aborted, such as commit.
|
Command buffer not found.
|
12017
|
Assignment header is corrupted, or no disk space on cache to extract command buffer.
|
Unknown assignment command.
|
12021
|
Command buffer corrupted, or core application is a totally new version with new commands that the GM does not understand.
|
CI/DP registration failed
|
12022
|
Obsolete cd.zip file present on NetCache. Delete cd.zip if exists in /etc/java in cache.
|
Cache quorum not met.
|
12023
|
Completion criterion is set for quorum and it is not met. Check xml log for exception details.
|
Group Member type unknown.
|
12024
|
Config incorrect, check registry.
|
Command buffer invalid.
|
12025
|
Command buffer corrupted, or core application is a total new version with new commands and arguments that GM does not understand.
|
Failed connecting to cache.
|
12026
|
Cannot make connection to cache on loop back.
|
System error.
|
12027
|
Occurs only on upgrade GM from core application, failed exec command on cache.
|
I/O Error on Streaming, incorrect number of bytes sent
|
12028
|
GL or core application aborted the assignment.
|
Content assignment header not found for payload.
|
12030
|
PUB failed for that assignment but the payload still sent. Check disk space on cache.
|
Content event unknown.
|
12031
|
Core application is a totally new version with new events that GM does not understand
|
Failed to cache object, Bad request
|
12400
|
Return code 400 from cache, check push header, it should be in the xml file log.
|
Failed to cache object.
|
12500
|
Return code 500 from cache, check log.
|
Cache content fill error.
|
12510
|
Return code 510 from cache, many causes, such as disk space, non- cacheable object, corrupted streaming file.
|
Property file not found.
|
15001
|
One or both of two possible virtual site property files is not where system expects it to be.
|
Unknown exception thrown.
|
15007
|
An unanticipated exception was raised during execution of cache registry gathering and reporting logic.
|
Number format exception thrown.
|
15008
|
Unanticipated non-numeric data encountered during execution of cache registry gathering and reporting logic.
|
Property file data invalid.
|
15009
|
Ill-formatted or unexpected data found in one or both of two possible virtual site property files.
|
