ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Utility doesn't create log, fails with Application return code = 1

book

Article ID: 199916

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When running an Automic utility from linux/unix command line, the command exits with a return code 1, but does not create a log file.  The output may look similar to this:


[[email protected] bin]$ ./ucybdbld -B -X/automic/Automation.Platform/Utility/db/general/12.3/UC_UPD.TXT
========================================================
Starting C++ batch mode loader...
User account (user/domain) <AUTOMIC/>
Startup parameter <-B -X/automic/Automation.Platform/Utility/db/general/12.3/UC_UPD.TXT >
Application name <./ucybdbld>
Launch from </home/automic/automic/Automation.Platform/Utility/bin/>
LoadLibrary pointer = <0x19cf4a0>
Application return code = 1

Better details of why the utility fails should be in the log file under the utility's /temp directory, but no file is being written

Cause

This can be caused by attempting to run the utility as a user who does not have write access to the /temp folder.

If this is the case, running a ls -l on the parent folder to the temp directory will show that there is no write privilege for anyone except the owner.

In the example above, the automic user is running the command, but the temp dir is owned by root and group and world do not have write permissions:

[[email protected] Utility]$ ls -l
total 8
drwxr-xr-x. 2 root root 4096 Aug  4 10:40 bin
drwxr-xr-x. 8 root root  172 Jul 28 13:11 db
drwxr-xr-x. 2 root root  195 Sep 14 13:48 temp
-rw-r--r--. 1 root root 3624 Jul 28 13:11 THIRD-PARTY-LICENSES.txt

Environment

Version: Any

OS: Linux, UNIX

Resolution

There are two options:
1) Run the utility as the user who owns the /temp folder or as a user who has write access to the /temp folder

2) Have an OS admin open up write permissions to the /temp folder to the user who is being used to run the utility.

This will then write the correct error to the log file in the /temp directory for further investigation as to why the utility failed to run.