RA FTP agent fails to start and Routine UCEX_R forces traces
search cancel

RA FTP agent fails to start and Routine UCEX_R forces traces


Article ID: 217775


Updated On:


CA Automic Operations Manager CA Automic One Automation


We are unable to start our test RA FTPAGENT. I see this in the log.

20210616/110710.024 - U00003620 Routine 'UCEX_R' forces trace because of error.
20210616/110710.035 - U02000048 TRACE file opened with flags '0000000000000001', max.trace: '9', memory trace: '0', search type: 'S', search string: ''.
20210616/110710.088 - U00003449 Output to the TRACE file is finished.
20210616/110710.089 - U02013310 Failed to load RA Agent.
20210616/110710.089 - U07001001 Charset used by the Agent: 'ISO-8859-15'
20210616/110710.090 - U02000041 Shutdown Agent 'FTPAGENT'.
20210616/110710.091 - U02000002 Agent 'FTPAGENT' version '12.3.5+build.1234566789' ended abnormally.

The forced trace file from the same time (ra_trace_00.txt) includes the following:

20210616/121908.912 - 33     ----------------------- Stack Trace -----------------------
20210616/121908.914 - 33     java.io.FileNotFoundException: ./inner_jarfiles/FTPConnection/Riverlayout-1.0.jar (The file access permissions do not allow the specified action.)
 at java.io.FileOutputStream.open(FileOutputStream.java:286)
 at java.io.FileOutputStream.<init>(FileOutputStream.java:226)


Release : 12.3



The directory or the files within it do not have the correct owner or correct permissions.


Have the system admins ensure that (and manually update as necessary):

The /inner_jarfiles directory has the same owner and group as the user starting the agent.  The directory should have 755 permissions (rwxr-xr-x).
Within that directory are two other directories, FtpAgent and FTPConnection that should have the same permissions as above.
Within those directories are files where the owner and group should be the same as the user starting the agent.  The files inside should have 644 permissions (rw-r--r--).  

The other option to resolve this is:

1) Make sure the agent is stopped
2) Make a backup of the inner_jarfiles directory
3) Delete the inner_jarfiles directory
4) Start the agent again

It should re-create the inner_jarfiles directory with the correct .jar files based on who is starting the agent.