MarkLogic Server 11.0 Product Documentation

Messages and Codes Reference Guide — Chapter 29

Message Text

No AWS security credentials are configured

Response

Configure them in the security section of the Admin GUI or using the Security API.

Message Text

Azure error: variable1 variable2 variable3 variable4 variable5

Message Text

No Azure storage account specified

Response

Configure it in the security section of the Admin GUI or using the Security API. Or specify it in the path with '@' following the container.

Message Text

No Azure security credentials are configured

Response

Configure them in the security section of the Admin GUI or using the Security API. Or use Azure IAM.

Message Text

Azure pathnames must begin with 'azure:/': 'variable1'

Message Text

Azure socket error: variable1 variable2 exception_stack

Message Text

Bad variable1

Cause

Normally indicates an internal error condition.

Response

Refer to the full text of the error for additional information. For more assistance, contact MarkLogic Technical Support if you have a current maintenance contract.

Message Text

Canceled

Cause

A connection is dropped or a request is canceled by the client.

Response

Retry the operation.

Message Text

Codepoint not legal

Message Text

Directory creation error: variable1 'variable2': variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was creating a directory. The host operating system function, directory name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Change working directory error: variable1 'variable2': variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was changing the working directory. The host operating system function, directory name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Get working directory error: variable1: variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was getting the working directory. The host operating system function and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Error iterating over directory: variable1

Cause

A host operating system file system directory function returned an unexpected error. The host operating system function, directory name, and error message are included in the error report. MarkLogic uses host operating system files for persistent storage.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Directory open error: variable1 'variable2': variable3

Cause

A host operating system file directory function returned an unexpected error while MarkLogic was opening a directory. The host operating system function, directory name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Directory removal error: variable1 'variable2': variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was removing a directory. The host operating system function, directory name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Directory rename error: variable1 'variable2': variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was renaming a directory. The host operating system function, directory name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Directory get size error: variable1 'variable2': variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was getting the size of a directory. The host operating system function, directory name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Time limit exceeded

Cause

A query or other operation exceeded its processing time limit. Surrounding messages in the log file may pinpoint the operation which timed out. In the example below, the time occurs during re-indexing:

Warning: XDMP-FORESTERR: Error in reindex of forest some_forest:
  XDMP-REFRAGMENT: Error refragmenting fn:doc("some_doc"):
    SVC-EXTIME: Time limit exceeded 

Response

If you determine the cause of the timeout is an inefficient or incorrect query, tune your query.

If you determine the cause of the timeout is an inadequate processing limit, you may be able to configure a more generous limit through the Admin Interface.

For more information on configuring timeouts, see the Administrator's Guide.

Message Text

Failed

Message Text

File chmod error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was changing the permissions of a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File chown error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was changing the ownership of a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File close error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was closing a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File copy error: variable1 variable2: variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was copying a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Source file does not exist: variable1

Message Text

File creation error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was creating a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File I/O error: variable1

Cause

A host operating system file function returned an unexpected error. The host operating system function, file name, and error message are included in the error report. MarkLogic uses host operating system files for persistent storage.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File I/O error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was accessing a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File or directory should not be a link: variable1

Message Text

File open error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was opening a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File read error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was reading a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File removal error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was removing a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File rename error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was renaming a file. The host operating system function, file names, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File reserve error: variable1 'variable2': variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was reserving space for a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File status error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was checking the status of a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File touch error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was touching a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File truncate error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was truncating a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File utime error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was updating the times on a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File write error: variable1 'variable2': variable3

Cause

A host operating system file function returned an unexpected error while MarkLogic was writing a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

HDFS URI missing netloc: variable1

Message Text

HDFS not available for 'variable1': variable2

Message Text

HDFS URI missing path: variable1

Message Text

Internal error: variable1

Message Text

Java string contains non-XML character: variable1

Message Text

HDFS Kerberos authentication failed for variable1: variable2

Message Text

Redirect standard I/O to log error: variable1 'variable2': variable3

Cause

A host operating system function returned an unexpected error while MarkLogic was redirecting stanadrd I/O to a log file. The host operating system function and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Mapped file flush error: variable1 'variable2': variable3

Cause

A host operating system memory-mapped file function returned an unexpected error while MarkLogic was flushing modified pages of a memory-mapped file. The host operating system function, file name, and error message are included in the error report. MarkLogic uses host operating system memory-mapped files for persistent storage.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Mapped file initialization error: variable1 'variable2': variable3

Cause

A host operating system memory-mapped file function returned an unexpected error while MarkLogic was mapping a file. The host operating system function, file name, and error message are included in the error report. MarkLogic uses host operating system memory-mapped files for persistent storage.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Mapped file unmapping error: variable1 'variable2': variable3

Cause

A host operating system memory-mapped file function returned an unexpected error while MarkLogic was unmapping file. The host operating system function, file name, and error message are included in the error report. MarkLogic uses host operating system memory-mapped files for persistent storage.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files have permissions allowing MarkLogic access. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Memory allocation error: variable1 variable2 bytes: variable3

Cause

A host operating system memory allocation function returned an unexpected error. The host operating system function, allocation size, and error message are included in the error report.

Response

Check the queries to see if they can be made more memory efficient. Increase the amount of memory on the host. Increase the amount of swap space on the host. Reduce the configured cache sizes on the host. See the MarkLogic technical note on troubleshooting out-of-memory issues.

Message Text

Canceled because of memory usage on host variable1, requestMemory=variable2, totalMemory=variable3, memoryLimit=variable4, opID=variable5, opMem=variable6

Cause

The request was cancelled because its memory usage was too high.

Response

Retry the operation.

Message Text

Internal memory allocation error: variable1 bytes

Message Text

Memory exhausted

Cause

The memory capacity of the host has been exhausted.

Response

Check the queries to see if they can be made more memory efficient. Increase the amount of memory on the host. Increase the amount of swap space on the host. Reduce the configured cache sizes on the host. See the MarkLogic technical note on troubleshooting out-of-memory issues.

Message Text

Mutex acquire error: variable1: variable2

Cause

A host operating system mutex function returned an unexpected error while MarkLogic was acquiring a mutex. The host operating system function and error message are included in the error report. MarkLogic uses host operating system mutexes for internal synchronization.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Mutex initialization error: variable1: variable2

Cause

A host operating system mutex function returned an unexpected error while MarkLogic was initializing a mutex. The host operating system function and error message are included in the error report. MarkLogic uses host operating system mutexes for internal synchronization.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Mutex release error: variable1: variable2

Cause

A host operating system mutex function returned an unexpected error while MarkLogic was releasing a mutex. The host operating system function and error message are included in the error report. MarkLogic uses host operating system mutexes for internal synchronization.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

variable3

Message Text

No Java VM: variable1

Message Text

Process done error: variable1: variable2

Message Text

Process exec error: variable1

Message Text

Process kill error: variable1: variable2

Message Text

Process run error: variable1: variable2

Message Text

Process wait error: variable1: variable2

Message Text

Random number generator error: variable1: variable2

Message Text

S3 commit error for 'variable1': variable2

Message Text

S3 error: variable1 variable2 variable3 variable4 variable5

Message Text

S3 cannot journal

Message Text

S3 pathnames must begin with 's3:/': 'variable1'

Message Text

S3 socket error: variable1 variable2 exception_stack

Message Text

Semaphore initialization error: variable1: variable2 variable3

Cause

A host operating system semaphore function returned an unexpected error while MarkLogic was initializing a semaphore. The host operating system function and error message are included in the error report. MarkLogic uses host operating system semaphores for internal synchronization.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Semaphore post error: variable1: variable2 variable3

Cause

A host operating system semaphore function returned an unexpected error while MarkLogic was posting semaphore. The host operating system function and error message are included in the error report. MarkLogic uses host operating system semaphores for internal synchronization.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Semaphore value error: variable1: variable2 variable3

Cause

A host operating system semaphore function returned an unexpected error while MarkLogic was reading the value of a semaphore. The host operating system function and error message are included in the error report. MarkLogic uses host operating system semaphores for internal synchronization.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Semaphore wait error: variable1: variable2 variable3

Cause

A host operating system semaphore function returned an unexpected error while MarkLogic was waiting for a semaphore. The host operating system function and error message are included in the error report. MarkLogic uses host operating system semaphores for internal synchronization.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Shutdown

Message Text

Socket accept error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was accepting a connection on a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket available error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was checking if data is available on a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket bind error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was binding a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was performing buffered I/O on a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket close error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was closing a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket connect error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was making a connection on a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket creation error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was creating a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket hostname error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was looking up a host name. The host operating system function, host name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket hostname too long: variable1

Cause

A host name passed to MarkLogic is too long to be resolved to an address.

Response

Use a shorter hos name.

Message Text

Socket error: variable1

Cause

A host operating system socket function returned an unexpected error during initialization. The host operating system function and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket listen error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was listening on a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket name error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was getting the name of a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket peer name error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was getting the peer name from socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket receive error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was receiving data over a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket send error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was sending data over a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket shutdown error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was shutting down a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Socket wait error: variable1 variable2: variable3

Cause

A host operating system socket function returned an unexpected error while MarkLogic was waiting on a socket. The host operating system function, socket name, and error message are included in the error report. MarkLogic uses host operating system sockets for communicating over the network.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Year cannot be formatted: variable1

Message Text

Cannot construct string larger than variable1.

Cause

Constructed strings cannot be larger than 4GB to 16GB, depending on memory and operating system.

Response

Break your data up in smaller parts.

Message Text

System call error: variable1 variable2: variable3

Message Text

Services testing error: variable1

Message Text

Thread creation error: variable1: variable2

Cause

A host operating system thread function returned an unexpected error while MarkLogic was creating a thread. The host operating system function and error message are included in the error report. MarkLogic uses host operating system threads for concurrent processing.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Thread exit: variable1: variable2

Cause

A host operating system thread function returned an unexpected error while MarkLogic was exiting a thread. The host operating system function and error message are included in the error report. MarkLogic uses host operating system threads for concurrent processing.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Thread initialization error: variable1: variable2

Cause

A host operating system thread function returned an unexpected error while MarkLogic was initializing a thread. The host operating system function and error message are included in the error report. MarkLogic uses host operating system threads for concurrent processing.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Thread priority error: variable1: variable2

Cause

A host operating system thread function returned an unexpected error while MarkLogic was changing the priority of a thread. The host operating system function and error message are included in the error report. MarkLogic uses host operating system threads for concurrent processing.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

Thread sleep error: variable1: variable2

Cause

A host operating system thread function returned an unexpected error while MarkLogic was sleeping a thread. The host operating system function and error message are included in the error report. MarkLogic uses host operating system threads for concurrent processing.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

variable1:Uncaught throw

Message Text

Invalid UTF-8 escape sequence: variable1

Message Text

Volume status error: variable1 'variable2': variable3

Cause

A host operating system file volume status function returned an unexpected error. The host operating system function, volume name, and error message are included in the error report. MarkLogic uses host operating system files for persistent storage.

Response

See the host operating system documentation for the precise meaning of the error message. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

Message Text

File read operation is not supported remotely from a different host

Cause

File read operation is not supported remotely from a different host. This operation can only be performed on the same host where the file is stored.

Response

Execute the read operation locally on the same host where the file is stored