Jobs go to LAUNCH ERROR status or processes fail to start with 'Not enough Space' error

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Error Message :
java.io.IOException: Not enough space

Unable to login to the Applications Manager client and/or Jobs on an Agent all go into a LAUNCH ERROR status.

The folloiwng error messages can be seen in the RmiServer###.log and/or the AgentService###.log file(s):

ErrorMsg: AwE-9999 Internal error 
Details: null
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(Unknown Source)
at java.lang.ProcessImpl.start(Unknown Source)
at java.lang.ProcessBuilder.start(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at com.appworx.agent.AppWorx.AppworxStandardAgent$1SpawnJob.spawn(AppworxStandardAgent.java:547)
at com.appworx.agent.AbstractSpawnJob.doRun(AbstractSpawnJob.java:105)
at com.automic.be.threading.AbstractWorker.run(AbstractWorker.java:378)
at java.lang.Thread.run(Unknown Source)

However, there may not be an error when all jobs go into a LAUNCH ERROR status.  This can be tested if this issue is being encountered by going to the Agent's out directory and tryping to manually create a file.  If it fails due to no space available then you are experiencing this issue.

Environment

CA Automic Applications Manager

Cause

The root issue is specific to the processes not coming up correctly or being unable to create required files on the agent to launch a job because of space/memory related issues.

Resolution

This is something that needs to be checked with the System Administrator of the machine(s). The solutions include:

• Check/increase swap space on Unix/Linux based systems or look into increase actual RAM/memory.
• Check usage of hard drive space on the AM and/or '/' partition.
• Free up space on the agent itself.

 

Additional Information

Workaround :
N/A