1 of 1 people found this helpful
It appears that you have a environment issue, and I suggest opening an escalation with support.
Can you please run it trace mode as :
/bin/bash -x ./cpit status
you can redirect the output and attach it in this thread :
/bin/bash -x ./cpit status >cpit.out 2>&1
Could you please let us know if the issue has been fixed? If yes, what were the steps taken?
I found that someone had executed below wrong command to check the status of TSCO Scheduler's Service and which caused to made "cpit" executable file empty.
#=> => ./cpit status
In above command used ">" option / string generally we used to make the file empty.
From history command output we notices that above command was got executed on 8th Feb.
2020-02-08 15:36:57 => ./cpit status
Once you find the date then you need to contact unix admin team to identify who logged in to server at that particular time.
Now you need to get cpit file from bmc support, As current active file is corrupted.