On a Linux node it was required to launch the command:
"$UNI_DIR_EXEC/uxrights -m restrict" to remove the setuid bit to the binary uxdqmlan as there were some random issues while submitting jobs that would abort with "Could not submit".
Following an upgrade of the node to a superior version, the issue with jobs failing to be submitted started to occur again and root cause being that the previous owner and permissions of the binary "uxdqmlan" were restored to the default ones.
Is this behavior normal?
Release : 6.x
Component : DOLLAR UNIVERSE
OS: Linux/Unix only
Expected behavior, the setup or autopatch do not consider the current permissions of the "uxdqmlan" binary, so they will be restored to the default when upgrading the node.
This is expected behavior and a note will be added in the documentation of the product to reflect the fact that the "uxrights -m restrict" command should be executed post-upgrade by the Dollar Universe Administrators.
This operation could be automated via the U_POST_PATCH script.