Murex Job scripts keep file handles on deleted Jobs reports

Products

• CA Automic One Automation

Issue/Introduction

In an environment where a Unix Agent launches Murex scripts  it is found that some open file handles remain in the system consuming disk space, since open file handles are on them.

When file descriptors are checked  by command lsof +L 1 | grep /opt/murex/uc4 we find about 400 lines of following kind:
java      89823 muradm    2w   REG 253,18    58175     0    2136618 /opt/murex/uc4/agent/out/OALPFBXP.TXT (deleted)
bash      89826 muradm    1w   REG 253,18    58175     0    2136618 /opt/murex/uc4/agent/out/OALPFBXP.TXT (deleted)
bash      89826 muradm    2w   REG 253,18    58175     0    2136618 /opt/murex/uc4/agent/out/OALPFBXP.TXT (deleted)
tee       89827 muradm    1w   REG 253,18    58175     0    2136618 /opt/murex/uc4/agent/out/OALPFBXP.TXT (deleted)
tee       89827 muradm    2w   REG 253,18    58175     0    2136618 /opt/murex/uc4/agent/out/OALPFBXP.TXT (deleted)

When checking pids we can see that they correspond to the murex scripts that were launched by the Automic Agent Unix.

How can we change this behavior and get rid of the no longer valid file handles?

 

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Sub-Component: Agent Unix

Third-Party Application: Murex

Cause

Root cause: Faulty Murex wrapper script used to submit jobs via the Automic agent.

Resolution

The submitted jobs were using an option that yields a suboptimal forking of processes and is not recommended anymore by Murex.

Solution consists on modifying the script used to launch the Murex jobs to not to use this option.

Additional Information

Please reach out Murex Technical Support or Services for more details.