The arsmaint program has always been designed to be initiated on the server.
Prior to fixpack 10.5.0.6 this restriction was not enforced.
Starting with 10.5.0.6 this restriction is being enforced.
This can result in arsmaint failing in two different cases.
1.) If arsmaint is not being initiated on the server, the solution is to run arsmaint on the server,
2.) If arsmaint is being initiated on the server, the server may not be resolving localhost correctly. Check to ensure the domain name localhost is resolved correctly.
Ref:
https://www.ibm.com/support/pages/node/7027952