8.5.4 Troubleshooting for service linkage jobs
- Organization of this subsection
(1) An unexpected value was returned as the return value for the command defined on the JP1/AJS3 for Cloud Service Applications server
The cause might be the following:
-
The command does not exist in the server.
If the command is not installed, install the command.
If the command path is not set by the PATH environment variable, set the command path.
-
The user executing the job might not have the permission to execute the command.
If the user does not have permission to execute the command, execute the service linkage job as a user who has permission. Alternatively, change the permission required to execute the command so that the user executing the service linkage job can execute the job.
-
If Windows is the OS of the execution host for the service linkage job, the command line might be too long.
Check the length of the command line and make sure that it is around 8,000 characters in length.
(2) In a Linux environment, the service linkage job was forcibly terminated unexpectedly
The size of the standard output and standard error output for the command defined for the JP1/AJS3 for Cloud Service Application server might be too large.
Check the syslog. The kernel might have stopped due to insufficient memory for the ajscsaexec process.
We recommend a total size of about 3 MB for the standard output and standard error output of commands defined on the JP1/AJS3 for Cloud Service Applications server. Configure the command line so that the size is not too large.
If the standard output and standard error output of commands defined on the JP1/AJS3 for Cloud Service Applications server are not required, consider specifying the command line to output to /dev/null.