Console -> properties tab -> you have option to change the STAGING_DIR
Yeah I know The Server-Property is set to /var/tmp/stage an every NSH-Job, BL-Package-Job and every other Job runs correctly there!
Only this Angent Installer Job! It seems, that he copy the installer to /tmp. But why?
For the Install option and Install/Upgrade option, SOCKS proxy and Advanced Repeaters are not supported. If the failing targets are in this category please check if the Running the Unified Agent Installer can help you.
No the failing targets aren't behind a SOCKS proxy or Repeaters.
ok, the Staging-Dir seems to be /var/tmp
on a Server there is 50GB free disk spase on the /var/
and the Job log says:
Info 24.10.2014 12:40:04 The agent is already installed on 'SERVERNAME'
Info 24.10.2014 12:40:04 Initiating agent upgrade.
Info 24.10.2014 12:40:09 The agent version detected on the target is '18.104.22.168'
Info 24.10.2014 12:40:09 The Operating System of target server is : 'Solaris 10/11 SPARC'.
Info 24.10.2014 12:40:09 The installation software picked from agent bundle is : 'RSCD85-SP1-SOL10-SPARC-LOCAL'.
Info 24.10.2014 12:40:15 Staging the agent installer, upgrade script and required (if any) configuration files to target servers staging directory : '/var/tmp/stage'.
Info 24.10.2014 12:40:15 Checking if installer file already exists in //SERVERNAME/var/tmp/stage/5850_18422db3-b37c-4913-9c11-718552426160/
Info 24.10.2014 12:40:16 RSCD85-SP1-SOL10-SPARC-LOCAL does not exists.
Info 24.10.2014 12:40:16 Ensuring required disk space exists
Error 24.10.2014 12:40:18 check_space:33: bad math expression: illegal character: ^H
Error 24.10.2014 12:40:18 Staging failed.Reason: Enough disk space was not available to copy installer.
What does this Error means?
It seems that for some reason the utility that should check if there is enough disk space available, is failing (the line in red). And therefore also the staging fails as it falsely assumes that there is no enough disk space.
Does this happens for all Solaris boxes or only for a specific ones.
No, the most Solaris are working. Its a normal Solaris 10 sparc (you can see it in the previous log, its not the only one, some more Solaris 10 sparc are affected).
On the most other Solaris 10 sparc it is working fine:
Info 22.10.2014 15:29:55 The agent is already installed on 'OTHERSERVER'
Info 22.10.2014 15:29:55 Initiating agent upgrade.
Info 22.10.2014 15:30:01 The agent version detected on the target is '22.214.171.124'
Info 22.10.2014 15:30:01 The Operating System of target server is : 'Solaris 10/11 SPARC'.
Info 22.10.2014 15:30:01 The installation software picked from agent bundle is : 'RSCD85-SP1-SOL10-SPARC-LOCAL'.
Info 22.10.2014 15:30:05 Staging the agent installer, upgrade script and required (if any) configuration files to target servers staging directory : '/var/tmp/stage'.
Info 22.10.2014 15:30:06 Checking if installer file already exists in //OTHERSERVER/var/tmp/stage/5850_81ea8ff1-83d8-4e5e-ac54-3bbb8942893b/
Info 22.10.2014 15:30:06 RSCD85-SP1-SOL10-SPARC-LOCAL does not exists.
Info 22.10.2014 15:30:06 Ensuring required disk space exists
Info 22.10.2014 15:30:07 Required disk space is available on target machine
Info 22.10.2014 15:30:07 Copying installer from //blfilesrv2.itoper.local/databl/fsbl2/installables/2102952.1/RSCD85-SP1-SOL10-SPARC-LOCAL to //OTHERSERVER/var/tmp/stage/5850_81ea8ff1-83d8-4e5e-ac54-3bbb8942893b/
Info 22.10.2014 15:30:14 Installer copied successfully.
This requires a deeper investigation. Therefore, I have opened a support ticket where we can continue.
I'm running into this same issue - could you let us know what the outcome of your ticket was?
I’d suggest opening your own ticket if you have no already.
For the server on which the job has failed,
What is the default shell?
If you find some script under //SERVERNAME/var/tmp/stage/5850_18422db3-b37c-4913-9c11-718552426160/
.Try running the script manually and check if it works properly