4.3 System call return codes

Table 4-4 shows the causes and required actions for return codes from representative system calls. For errors that are not listed in Table 4-4, see the applicable OS manual.

In UNIX:
Unless otherwise noted, Table 4-4 shows the errno used in HP-UX. Because the table lists only the principal system calls, to determine the exact nature of the error, check the mnemonic associated with the value or errno indicated in the message in the errno definition file (the contents defined in (/usr/include/sys/errno.h for HP-UX or Solaris) of the OS being used. Regarding a system call that has resulted in an error, check it in the manual and identify the cause of the error associated with the mnemonic.
In Windows:
Because Table 4-4 only lists the principal system calls, to determine the exact nature of the error, check the mnemonic associated with the value of errno indicated in the message in the errno definition file of the OS being used. If a system call has resulted in an error, refer to the manual to identify the cause of the error associated with the mnemonic.

Table 4-4 System call return codes

System CallerrnoMnemonicPossible CauseAction
fcntl22EINVALIf you are using the raw I/O facility in Windows, a partition format that cannot be used was specified.Specify a partition format that can be used by the raw I/O facility. For information on partition formats that can be used by the raw I/O facility, see the HiRDB Version 9 Installation and Design Guide.
fork11EAGAINEither there are too many processes or a temporary memory shortage has occurred.If this error occurs repeatedly when the command is rerun, terminate any unneeded processes.
12ENOMEMOne of the following problems is suspected:
  • The swap area (in Windows, virtual memory) is too small for the process to be newly created.
  • There are too many processes or some processes are using too much memory.
If the swap area (in Windows, virtual memory) is too small, increase it.
If this is not possible, terminate the processes that are not needed. If some of the processes are using too much memory, determine whether they can be terminated.
malloc12ENOMEMOne of the following problems is suspected:
  • The swap area (in Windows, virtual memory) is too small for the process native area to be allocated.
  • There are too many processes or some processes are using too much memory.
If the swap area (in Windows, virtual memory) is too small, increase it.
If this is not possible, terminate the processes that are not needed. If some of the processes are using too much memory, determine whether they can be terminated.
22EINVALInvalid memory management information was detected.Contact the customer support center.
mkdir13EACCESSAn access privilege is invalid.Check if access privileges to files under the HiRDB directory are correct.
28ENOSPCThere is not enough free space for the file system.Either delete files that are no longer needed from the file system or move files to a file system that has adequate free space.
msgget28ENOSPCIn UNIX:
The value specified in msgmni (number of message queue identifiers) is too small.
In Windows:
The capacity of the installation drive or the number of resources in use is insufficient.
In UNIX:
Estimate the memory requirements of all programs that are running on the server machine indicated by msgmni, change the specified value, and then reboot the applicable server machine.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.
Or, specify the required number of resources (message queue identifiers) in the PDUXPLMSGMNI system environment variable.
For the formula for determining the number of message queue identifiers, see the HiRDB Version 9 Installation and Design Guide.
The default value of the PDUXPLMSGMNI system environment variable is 50.
msgrcv22
36
EINVAL
EIDRM
In UNIX:
The ipcrm command of the OS or the pdsetup command of HiRDB was incorrectly executed when HiRDB was running, which resulted in the deletion of the message queue used by HiRDB.
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
If HiRDB has not terminated abnormally, terminate it.
After that, reboot the applicable server machine. (In the case of Windows, restart the HiRDB service.)
msgsnd11EAGAINThe value specified in msgmni (number of message queue identifiers) or msgtql (number of messages) is too small.In UNIX:
Estimate the memory requirements of all programs that are running on the server machines indicated by msgmni or msgtql, change the specified values, and then reboot the applicable server machine.
In Windows:
Set the value for the number of required resources (number of message queue tables) in the PDUXPLMSGTQL system environment variable.
For the formula for determining the number of message queue tables, see the HiRDB Version 9 Installation and Design Guide.
The default for the PDUXPLMSGTQL system environment variable is 80.
22EINVALThe ipcrm command of the OS or the pdsetup command of HiRDB was incorrectly executed when HiRDB was running, which resulted in the deletion of the message queue used by HiRDB.If HiRDB has not terminated abnormally, terminate it. After that, reboot the applicable server machine.
open2ENOENTThe indicated file or directory is not found.
If the file logblib.c is output to the calling module for a KFPO00107-E message, a message text file cannot be found. If that is the case, the cause is as follows:
In UNIX:
Consider one of the following:
  1. A HiRDB command was executed before the pdsetup command terminated normally.
  2. The PDDIR environment variable is not correctly set up.
  3. A HiRDB version that is not currently used is registered in the OS.
In Windows:
The PDDIR environment variable might not be set correctly.
In UNIX:
Take the following actions according to the cause of the error:
  1. Execute the HiRDB command after confirming the normal return of the pdsetup command.
  2. Confirm that the PDDIR environment variable is correctly set up.
    For a user shell, use the env command to confirm that the value of PDDIR is correctly assigned. If the PDDIR environment variable is set when export is leaking or by using the set command, assigned values are not transferred to the HiRDB command process, which causes this error.
    If the OpenTP1, HA Monitor, Hitachi HA Toolkit Extension, cluster software, JP1, DBPARTNER,HiRDB Datareplicator, HiRDB CM, and other products are used, check to see if the PDDIR environment variable for those products is correctly set.
  3. Use the pdsetup -d command to delete from the OS the HiRDB version that is not being used. To delete all execution environments, specify y in response to the pdsetup -d command.
In Windows:
Ensure that the PDDIR environment variable is set correctly. If the command was executed from the command prompt, use the set command to determine whether the PDDIR environment variable was set correctly. If using a product such as OpenTP1, JP1, DBPARTNER, HiRDB Datareplicator, or HiRDB CM, confirm that the PDDIR environment variable has been set correctly for these products.
6ENXIONo access privilege for the file.Confirm that the device exists and that the device is validated. If the device is not validated, validate it. If the error still cannot be resolved, refer to the manual for the OS in use and take corrective action.
13EACCESNo access privilege for the file.
  • Review the privilege for the target file, directory, or HiRDB operation directory.
  • Check to see if the person executing the command has the access privilege for the target file, directory, or HiRDB operation directory.
17EEXISTThe file to be created already exists.Either rerun the command by renaming the file or, if the existing file is not needed, delete the file, and then rerun the command.
23ENFILEIn UNIX:
The number of open files exceeds the maximum for the system.
In Windows:
There is insufficient capacity on the installation drive.
In UNIX:
Increase the specification value for the maximum number of OS operating system parameter (kernel parameter) files that can be opened by the system (For HP-UX: nfile. For AIX: maxuproc[Figure] nofiles[Figure] number of fixed licenses. For Linux: NR_FILE or fs.file-max). Stop any processes or windows that are not needed.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.
24EMFILEIn UNIX:
Too many files are open in the indicated process.
In Windows:
There is insufficient capacity on the installation drive.
In UNIX:
If the error occurred in a HiRDB command or utility process, increase the value for the maximum number of OS operating system parameter (kernel parameter) files that can be opened by the system (For HP-UX: maxfiles. For Solaris: rlim_fd_cur. For AIX: nofiles. For Linux: INR_OPEN). If this problem occurs in a HiRDB server process, contact the customer support center.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.
999ENOENTFor Windows, HiRDB work files may have been destroyed.After confirming that HiRDB has stopped, delete all the files listed below and then restore them.
Note that the files from No. 4 on may not exist in all cases.
  1. %PDDIR%\uxpldir\spool\system\filmng.dat
  2. %PDDIR%\uxpldir\spool\system\flg.dat
  3. %PDDIR%\uxpldir\spool\system\shmmng.dat
  4. %PDDIR%\spool\...pdatmode
  5. %PDDIR%\spool\...pdipcid
  6. %PDDIR%\spool\oslmqid
  7. %PDDIR%\spool\oslsmid
  8. %PDDIR%\spool\pdprcsts
  9. %PDDIR%\spool\scdqid1
  10. %PDDIR%\spool\scdqid2
  11. %PDDIR%\tmp\pdommenv
  12. All files under %PDDIR%\uxpldir\spool\shm
  13. %PDDIR%\uxpldir\spool\system\semmng.dat
  14. %PDDIR%\uxpldir\spool\system\msgmng.dat
When starting HiRDB after deleting all these files, make sure other applications, such as Explorer, are not accessing %PDDIR%\tmp.
semget12ENOMEMShortage occurred in the number of resources used.Specify the number of resources required (the number of semaphore identifiers) in the PDUXPLSEMMAX system environment variable. For details on how to compute the number of semaphore identifiers, see the HiRDB Version 9 Installation and Design Guide. The default for the PDUXPLSEMMAX system environment variable is 64.
28ENOSPCIn UNIX:
The value specified in semmni (number of semaphore identifiers) or semmns (number of semaphores in the system) is too small.
In Windows:
There is insufficient capacity on the installation drive.
In UNIX:
Estimate the memory requirements of all programs that are running on the server machines indicated by semmni or semmns, change the specified values, and then reboot the applicable server machine.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size.
semop22EINVALIn UNIX:
The ipcrm command of the OS or the pdsetup command of HiRDB was incorrectly executed when HiRDB was running, which resulted in the deletion of the semaphore used by HiRDB.
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
If HiRDB has not terminated abnormally, forcibly terminate it. After that, reboot the applicable server machine (for Windows, restart the HiRDB service).
shmat12ENOMEMConsider one of the following:
  1. The number of available resources is insufficient. This includes the case in which a contiguous free area cannot be allocated in the process space to which shared memory is to be attached.
  2. In Windows, an error occurred while referencing the Windows registry.
  3. In Windows, the HiRDB service is not started (when shared memory is allocated to the paging file).
Take the following corrective action according to the cause of the error:
  1. For Windows, assign the number of required resources (size of required shared memory) in the system environment variable PDUXPLSHMMAX. For details on how to compute the size of the shared memory to be used, see the Determining Environment Variables Related to the Number of Resources section in the HiRDB Version 9 Installation and Design Guide. The PDUXPLSHMMAX default is 4096. If usable memory cannot be made available, change the HiRDB system definition (for example, by reducing the number of global buffers) to reduce the shared memory requirements.
  2. Check the specification value for the -shmfile option of the pdntenv command. If the specification value is other than regular, page, or blank, the Windows registry might have been corrupted. If that is the case, contact the customer support center.
  3. If the shared memory is allocated to the paging file, confirm that the HiRDB service started. If the HiRDB service has stopped, start it.
22EINVALIn UNIX:
Shared memory for HiRDB is missing. It is possible that a HiRDB command was entered before the OS was fully started (during the execution of /etc/rc) or a HiRDB command was coded in an environment file, such as /etc/localrc, which is executed upon completion of the startup of the OS.
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
Or, it is possible that the command was executed before the activation of HiRDB was complete.
In UNIX:
If a HiRDB command was entered before the OS was fully started, reenter the command after the startup of the OS is complete. Also, be careful not to code a HiRDB command in the /etc/localrc OS environment file.
If activation of HiRDB is not complete, wait until HiRDB is complete, and then execute the command.
In Windows:
If HiRDB activation has not been completed, complete HiRDB activation and then re-execute. If HiRDB did not terminate abnormally, terminate it forcibly. After that, restart the HiRDB service.
shmdt12ENOMEMIn Windows, consider one of the following causes:
  • An error occurred while referencing the Windows registry.
  • The HiRDB service is not started (when shared memory is allocated to the paging file).
  • Check the value specified for the pdntenv command's -shmfile operand. If it is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.
  • If the shared memory is allocated to the paging file, confirm that the HiRDB service is started. If the HiRDB service is stopped, start the service.
shmctl1EPERMBecause the user is not an owner, the shared memory cannot be processed.If a KFPH23015-E or KFPO00107-E message is output, see that message.
12ENOMEMIn Windows, consider one of the following causes:
  • An error occurred while referencing the Windows registry.
  • The HiRDB service is not started (when shared memory is allocated to the paging file).
  • Check the value specified for the pdntenv command's -shmfile operand. If it is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.
  • If the shared memory is allocated to the paging file, confirm that the HiRDB service is started. If the HiRDB service is stopped, start the service.
shmget12ENOMEMIn UNIX:
The required shared memory capacity is not available on the server unit.
In Windows:
Refer to Table 4-5.
In UNIX:
Reduce memory usage on the server unit. Or, increase the real memory under the operating system.
In Windows:
Refer to Table 4-5.
22EINVALIn UNIX:
There was an attempt to acquire a shared memory volume that exceeds the value specified in the shmmax operating system parameter (kernel parameter).
In Windows:
It is possible that the work files in the HiRDB installation directory were deleted when HiRDB was running.
In UNIX:
Increase the value specified in the shmmax operating system parameter (kernel parameter). After changing the specified value, reboot the server machine.
In Windows:
If HiRDB did not terminate abnormally, terminate it forcibly. After that, restart the HiRDB service.
28ENOSPCIn UNIX:
The number of shared memory identifiers exceeds the OS limit.
In Windows:
There is insufficient capacity on the installation drive. Also, if the paging file is allocated as shared memory, the process native memory used by the HiRDB service to manage the shared memory might be insufficient.
In UNIX:
Take one or more of the following actions:
(1) Reduce the number of shared memory segments set up on the same machine.
(2) Increase the specification value in the operating system parameters (kernel parameter) shmmni and shmall.
In Windows:
On the installation drive, allocate at least as much free space as is required for the shared memory size. Also, if the paging file is allocated as shared memory, check the maximum available memory for the entire system, and increase either the physical memory or the size of the paging file.
vfork-1800 level#--Refer to Table 4-6.
waitpid-1800 level#--Refer to Table 4-6.
write5EIOAn input/output error has occurred.Take corrective action according to OS and hardware information.
14EFAULTAn attempt was made to write to an inaccessible area. It is possible that the disk on which a write operation was attempted has been detached.The problem can be ignored if it occurred during disk switching associated with system switchover. If the disk was detached by mistake when HiRDB was still running, either back up or restore the affected file, and initialize it before using. In other cases, contact the customer support center.
27EFBIGThe file is greater than the system-imposed limit.Change the file size limit for the HiRDB administrator and the root user either to a size greater than required in HiRDB or to unlimited size. Alternatively, reduce the size of the file to be used.
28ENOSPCThe file system does not have enough area.Either delete files that are not needed from the file system or move to a file system that has more space.
abort
creat
execl
execle
execlp
execv
execvp
fopen
fork
gethostbyaddr
gethostbyname
mmap
msgctl
msgget
msgrcv
msgsnd
open
read
readv
select
semctl
semget
semop
shmat
shmctl
shmdt
shmget
signal
sigrelse
sigset
sigsetmask
sigvector
stat
system
write
writev
etc.
22EINVALFor the Windows edition of HiRDB, there may be insufficient memory.For the Windows edition of HiRDB, take corrective action from among the following options:
  • Specify Y in the pd_ntfs_cache_disable operand.
  • Decrease the total size of the databases on the server machine.
  • Decrease the size of the global buffer.
  • Decrease the values specified in the following operands:
    pd_max_users
    pd_process_count
    pd_max_bes_process
    pd_max_dic_process
    pd_max_server_process
    pd_max_rdarea_no
    pd_max_file_no
    pd_max_access_tables
    pd_lck_pool_size
    pd_fes_lck_pool_size
  • Set the default size and the maximum size of system virtual memory to the same value (a fixed size).
  • Do not collect statistical information and various trace information if you are currently doing so.
tempnam12ENOMEMIn UNIX:
The following possibilities should be investigated.
  • Process private memory cannot be allocated due to a shortage of swap area.
  • There are too many processes, or some of the processes are consuming an excessive amount of memory.
In Windows:
The following possibilities should be investigated.
  • Process private memory cannot be allocated due to a shortage of virtual memory.
  • There are too many processes, or some of the processes are consuming an excessive amount of memory.
In UNIX:
If the swap area is insufficient, expand it. If it cannot be expanded, terminate any unneeded processes.
If some processes are consuming a large amount of memory, see whether you can turn them off once.
In Windows:
If there is a shortage of virtual memory, expand the virtual memory. If it cannot be expanded, terminate any unneeded processes.
If some processes are consuming a large amount of memory, see whether you can terminate them for a while.
13EACCESYou do not have access privileges to this directory path.Check whether you have administrative access privileges to the directory path for the file name created by tempnam. If you do not have access privileges, assign them. Directory paths are indicated as follows.
In UNIX:
  • /tmp or /var/tmp
  • Directory path set in the TMPDIR environment variable
  • tmp directory under the HiRDB Entier directory
  • Setting value P_tmpdir defined in the OS. Include header file stdio.h
In Windows:
  • %PDDIR%\tmp
  • Directory path set in the TEMP or TMP environment variable
  • tmp directory under HiRDB Entier directory
24EMFILEIn UNIX:
The following possibilities should be investigated.
  • The number of temporary files is equivalent to or exceeds the TMP_MAX value.
  • There are too many open files in the corresponding process.
In Windows:
The following possibilities should be investigated.
  • There are 32,767 or more temporary files.
  • There is a shortage of drive space set in the install drive, the environment variable TEMP, or TMP.
In UNIX:
  • If the number of temporary files is equivalent to or exceeds the TMP_MAX value, delete any unnecessary temporary files that have been created under the directory path listed in the EACCES section. Temporary files include the following files.
    - Results file when an operation command or utility was executed
    - Files that start with the prefix pd
  • If there is a large number of open files and an error occurs in a HiRDB command or utility process, increase the maxfiles value of the operating system parameters (kernel parameters) of the OS.
  • If the above corrective actions are not applicable, contact the customer support center.
In Windows:
  • If there are 32,767 or more temporary files, delete any unnecessary temporary files that have been created under the directory path listed in the EACCES section. Temporary files include the following files.
    - Results file when an operation command or utility was executed
    - Files that start with the prefix pd
  • If there is a shortage of drive space set in the install drive, environment variable TEMP, or TMP, then allocate to the appropriate drive free space that is at least as large as the shared memory.
  • If the above corrective actions are not applicable, contact the customer support center.
bindIn UNIX:
226 (HP-UX),
67 (AIX),
125 (Solaris),
98 (Linux)
In Windows:
10048
EADDRINUSE
WSAEADDRINUSE
The port number set in HiRDB might have been a duplicate of another port code used for a different program, or it could be a duplicate of multiple port numbers set in HiRDB.Re-examine the port numbers set in HiRDB, and make sure there are no duplicates.
#
Because of the return value of the function that issues internal system calls, the system call errno does not remain as is.

Table 4-5 Corrective action when an error occurs in the shmget system call (in Windows)

ItemLocation of shared memory allocation#1CauseDeterminationAction
1Shared between files and the paging fileInsufficient memoryCheck the value specified for the PDUXPLSHMMAX system environment variable.Set the number of required resources (number of shared memories) in the PDUXPLSHMMAX system environment variable. For details about the formula for calculating the number of shared memories, see the manual HiRDB Version 9 Installation and Design Guide. If the PDUXPLSHMMAX system environment variable is omitted, 4,096 is assumed.
2FilesInsufficient free space on the installation diskDetermine whether there is sufficient free space on the drive where HiRDB is installed.If there is insufficient free space, delete unnecessary files.
3Because the initial and maximum values specified for the virtual memory are different, there is no free space on the disk that allocated the disk paging fileDetermine whether there is free space on the disk that allocated the disk paging file.If there is no free space on the disk, re-allocate the virtual memory. When re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.
4There is insufficient memoryCheck whether there is enough free space in the virtual memory (paging file).Expand or re-allocate the virtual memory. When expanding or re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.
5Determine whether there is sufficient free space on the disk that holds the paging file.If the virtual memory needs to be expanded, expand it. At this time, specify the same initial value and maximum value for the virtual memory.
6The installation information cannot be referenced correctlyCheck the installation information. The installation information can be displayed using the pdntenv command. For details about the pdntenv command, see the manual HiRDB Version 9 Command Reference.Use the pdntenv command to check the value of ShmFile. If the value of ShmFile is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.
7If memory page locking failsCheck in either the HiRDB system definitions or command line whether there is a setting for locking memory pages.If you are locking pages in the memory, the location for shared memory must be a paging file. Change the location for allocating shared memory to the paging file.
8Paging fileThere is insufficient free space on the installation driveDetermine whether there is sufficient free space on the drive where HiRDB was installed.If there is insufficient space, delete any unnecessary files.
9Because the initial and maximum values specified for the virtual memory are different, there is no free space on the disk that allocated the disk paging fileDetermine whether there is free space on the disk that allocated the disk paging file.If there is no free space on the disk, re-allocate the virtual memory. When re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.
10There is insufficient memoryCheck whether there is enough free space in the virtual memory (paging file).Expand or re-allocate the virtual memory. When expanding or re-allocating the virtual memory, specify the same initial value and maximum value (fixed value), so as to be able to create a contiguous area on the drive.
11Determine whether there is sufficient free space on the disk that holds the paging file.If the virtual memory needs to be expanded, expand it. At this time, specify the same initial value and maximum value for the virtual memory.
12The installation information cannot be referenced correctlyCheck the installation information. The installation information can be displayed using the pdntenv command. For details about the pdntenv command, see the manual HiRDB Version 9 Command Reference.Use the pdntenv command to check the value of ShmFile. If the value of ShmFile is other than regular, page, or blank, the Windows registry might be corrupt. If that is the case, contact the customer support center.
13The HiRDB service is not startedConfirm that the HiRDB service is started.If the HiRDB service is stopped, start it.
14If memory page locking failsCheck whether the disk where the virtual memory or paging file was allocated has enough free space. If this error occurs despite there being enough free space, page locking has failed due to the absence of contiguous space in the physical memory.Take one of the following corrective actions.
  • Do not lock the page in the memory.
  • Revise the specification value for the SHMMAX operand so that there is enough contiguous space in the physical memory in order to allocate shared memory.
  • Restart the OS in order to enable allocation to the contiguous space in the memory.#2
  • Increase the physical memory and the space where the shared memory can be allocated.
see the manual HiRDB Version 9 System Definition for information on the SHMMAX operand.
15You do not have valid permissions to be able to lock shared memory to pages in the memory.Take one of the following corrective actions.
  • Set HiRDB administrator permissions by going to OS -> Local security settings -> Local Policies -> User Rights Assignment -> Lock pages in memory.
  • On HiRDB/single server, if you do not use the system switchover facility, which does not take on an IP address, set the log-on account that you use when services are running to the local system account.
#1
The location where the shared memory is allocated can be determined by referring to the value of ShmFile obtained by the pdntenv command. The following table shows where the shared memory is allocated for each value displayed using the pdntenv command.

ItemShmFile valueAllocation location
1regularFiles under the HiRDB directory
2pagePaging file
3blankFiles under the HiRDB directory
#2
If the physical memory becomes fragmented, the fragmented areas might not be joined until the OS is restarted. Therefore, you must restart the OS to ensure that contiguous area is created.

Table 4-6 Causes and corrective actions to take when a -1800 number level error occurs in vfork, waitpid

System callerrnoMain possible causesCorrective action
vfork-1818Communication with the command execution process failed (disconnection was detected).Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, make sure that there is no shortage of file descriptors in the system as a whole.
-1819A resource shortage occurred during the XDS process.
The main possible causes are as follows:
  • Shortage of file descriptors
Perform either of the following actions:
  • Check the specification value of the pdq_max_descriptors operand in the XDS server definitions.
  • Check whether there is a shortage of file descriptors in the system as a whole.
-1871A resource shortage occurred during the command execution process.
The main possible causes are as follows:
  • There are too many processes.
  • A memory shortage occurred.
Perform either of the following actions:
  • Check whether the number of processes in the system has reached the maximum limit.
  • Check whether there is a shortage of memory in the system.
-1872An attempt to establish a connection with the command execution process failed.Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, make sure that there is no shortage of file descriptors in the system as a whole.
waitpid-1818Communication with the command execution process failed
(disconnection was detected).
Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, check whether there is a shortage of file descriptors in the system as a whole.
-1871A resource shortage occurred during the command execution process.
The main possible causes are as follows:
  • There are too many processes.
  • A memory shortage occurred.
Perform either of the following actions:
  • Check whether the number of processes in the system has reached the maximum limit.
  • Check whether there is a shortage of memory in the system.
-1873The connection with the command execution process was disconnected, and response waiting was canceled.Check whether the command execution process has started.#
If it has not started, contact the customer support center.
If it has started, check whether there is a shortage of file descriptors in the system as a whole.
#
It is possible to check whetherthe command execution process has started by executing the pdls -d prc -a command to check whether a process with server name cmdd exists.