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.
DUAS6: Uprocs getting Aborted "Could not submit" randomly
Article ID: 186184
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Some Uprocs, fail to be Submitted so they end in status Aborted, with the action Icon "Could not Submit".
The history trace is available.
The Job Log is created, but belongs to the user root and is empty.
A temporary file containing the environment execution variables remains present in the folder $U_TMP_PATH
When relaunching the Uproc, it usually works fine, launching it 5 minutes later, works fine as well.
Nothing can be found on /var/log/secure or /var/log/messages that explain why the "su" command fails to switch from root to the submission system user.
Cause
Unknown system issue, should be related to the su command failing to switch the user context from root to the submission account user.
Environment
Release : 6.9
Component : DOLLAR UNIVERSE
OS: Redhat Linux 7
Resolution
1. Assign the node to the user that will be the only one that can submit Jobs (in this case bjob), to do so, do the following as root:
./unistop
./uxrights -m assign -a bjob
./uxrights -m restrict
su - bjob
cd /path_of_du
. ./unienv.ksh
cd bin
./unistart
2. With UVC modify the submission account administrator to point to the user bjob instead of the current one ( in this case duadmin)
./unistop
./uxrights -m assign -a bjob
./uxrights -m restrict
su - bjob
cd /path_of_du
. ./unienv.ksh
cd bin
./unistart
2. With UVC modify the submission account administrator to point to the user bjob instead of the current one ( in this case duadmin)
Feedback
Yes
No
Powered by
