Troubleshooting › Agent Error Messages on i5/OS

Agent Error Messages on i5/OS

This section provides common error messages returned by the agent installed on an i5/OS system.

Command does not use shell

Reason:

Only a script can use a shell.

Action:

Remove the shell statement from the job definition.

Command or script name missing

Reason:

In the job definition, you have not defined the required command or script name.

Action:

Add the command name or script name to the job definition.

Command requires a User ID

Reason:

Each command must specify an allowable user.

Action:

Add the USER statement.

Connection aborted by peer: JVM_recv in socket input stream read

Reason:

You may need to reset the communication.timeout parameter to allow more time between a message being sent and an acknowledgement (ACK) being received. When this time is exceeded, the connection is aborted.

Action:

As a starting point, set the value in msecs to 120000 and test. Change the value as needed so this error does not occur.

Error changing directory

Reason:

In the agentparm.txt file, the parameter oscomponent.initialworkingdirectory specifies the working directory. If the path is incorrect, this error will occur.

Action:

1. Verify the directory exists.
2. Specify the correct path in the parameter.

Error closing stdout, stdout, or stderr

Reason:

The error is caused by a system problem that may be intermittent.

Action:

Try to resubmit the job. If this action does not resolve the problem, contact your system administrator.

Error creating pthread

Reason:

System resources are low.

Action:

Contact your system administrator.

Error creating spool file. Job: JOB.TXT/APPL. xxxx/MAIN, errno: 31, Reason: Too many links

Reason:

On AIX and Linux, the file system may limit the number of spool directories.

Action:

Refer to your operating system documentation for details regarding the spool directory limitations. Clear the spool directories periodically using the agent.

Error creating stdout spool file

Reason:

The user may not have the necessary permissions to create the spool file.

Action:

Check the user permissions.

Error getting owner of the script

Reason:

Failure to get the owner of the script from the system password file.

Action:

Contact your system administrator.

Error occurring during submission

Reason:

Connection error with the scheduling manager.

Action:

Check the connection to the scheduling manager.

Error opening stdin, stdout, or stderr

Reason:

The agent does not have permission to open the file. This error is caused by a system problem.

Action:

1. Check permissions. Change them as needed to allow the agent to open the file.
2. Contact your system administrator.

Error redirecting stdin, stdout, or stderr

Reason:

The agent tries to redirect an input file to another file and an error results. This file could be a spool file or some specified stdin or stdout file. For a stderr message, the cause may be a system problem that is intermittent.

Action:

Try to resubmit the job. If this action does not resolve the problem, contact your system administrator.

File not found

Reason:

The agent cannot find the file. Either the wrong path was specified in the job definition, or the file does not exist.

Action:

Verify the path and check the file exists.

Invalid command: not listed in oscomponent.validcommand

Reason:

Invalid command.

Action:

Add the command to the oscomponent.validcommand parameter in the agentparm.txt file, or contact your system administrator.

Invalid file name

Reason:

The file path is too long. This error can happen if there are too many symbolic links. The system call will return an error if the name is too long.

Action:

Relocate the files to get rid of the symbolic link.

Invalid shell error

Reason:

In the agentparm.txt file, you must specify the valid shell in the parameter oscomponent.validshell. The corresponding job definition may not have the correct shell specified in the shell statement.

Action:

1. Verify the correct shell is specified in the agentparm.txt file. Alternatively, you can set the oscomponent.checkvalidshell=false parameter in the agentparm.txt file, so that the agent will never bother to validate whether the shell is valid.
2. Verify the corresponding job definition has the correct shell specified in the shell statement.
3. In the first line of a script file, the shell and its path must match exactly what you specified in the validshell parameter.

Irregular file

Reason:

The file is not a regular file, such as an ascii or binary file. The file may be a directory file or a pipe, or a program in /bin being run under PASE.

Action:

Check the file's type using ls -l. Replace the file with a regular file.

Not a script file

Reason:

The script contains non-printable characters.

Action:

Use Command instead of Script name in the job definition.

Refused by Agent security

Reason:

The job is refused by the agent's local security.

Action:

Check the security.txt file.

Script/Command not accessible

Reason:

The symbolic link does not exist.

Action:

Check the definition of the symbolic link to see if it exists.

Script/Command not executable

Reason:

The user may not have the necessary permissions to execute the script or command.

Action:

Check the user permissions.

Script/Command not readable

Reason:

User does not have read permission.

Action:

Check the user permissions.

User does not exist in the system

Reason:

You did not define the user on the agent system.

Action:

Ensure the user exists on the agent system.