03-11-2013 08:49 PM
I built a script monitor to send remote command to remote server. it failed to execute the command: /home/dsb/bin/alert_logsurf;echo "all done" on remote: xxxx.com, timeout
I checked runmonitor.log and got the below error:
Mon Mar 11 15:48:35 CET 2013 Connection timed out(V2) com.mercury.sitescope.util.ssh.exception.SSHV2Time
The SSH connection has no problem.
The time to execute the command is long, more than 70 sec.
How to extend the threashold (currently it is 60 sec according to the log) ?
BTW, I have tried, the setting in general preference->ssh preference doesn't work for this case.
Solved! Go to Solution.
03-12-2013 12:11 AM
I just had a quick dig through the master.config file on this end, the following seems like it might have something to do with your error:
The following might be worth a try:
- Make a backup of your $SIS_HOME\groups\master.config file
- Edit your $SIS_HOME\groups\master.config file and change _serverReadRefresh=60000 to a higher value
- Restart Sitescope and test again
If that had no effect, either restore your master.config file and repeat the above for line _processPoolKillTimeout=60000, or change this line in addition to the previous change you made.
Hope this helps.
12-08-2014 08:07 AM
Finally you are modified this value _processPoolKillTimeout to 60000 ?
Or what are doing exactly because i have the some issue
12-08-2014 09:42 AM
This _processPoolKillTimeout is for perfex process pool, nothing to do with Unix scripts
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you haven’t tried it yet, come and join us in our entitled forums at Support Customer Forums