1833007 Members
3031 Online
110048 Solutions
New Discussion

Re: Swinstall issue

 
Dewa Negara_4
Regular Advisor

Swinstall issue

Hi All,

I have a script to distribute our SOE product using swinstall command on list of around 200 servers. Somehow the swinstall command is stuck on one of the servers that has been decommisioned, so the swinstall command for the rest of the servers can be completed. Please refer to the output below.

Is there any way to skip this stuck swinstall command, so it can continue to the next server?


[root@bdhm:/usr/local/sysmgr/secu_refresh]
# swinstall -x mount_all_filesystems=false -s bdhm:/var/spool/sw/applications/SECU SECU_TST @ bdhp4369

======= 09/17/06 23:30:23 EDT BEGIN swinstall SESSION
(non-interactive) (jobid=bdhm-4451)

* Session started for user "root@bdhm".

* Beginning Selection


Please help.

Thanks and Best Regards,
Dewa
Santos
4 REPLIES 4
RAC_1
Honored Contributor

Re: Swinstall issue

It should timeout on it's own or you can interrupt it. cntrl+c
There is no substitute to HARDWORK
Adisuria Wangsadinata_1
Honored Contributor

Re: Swinstall issue

Hi Mr. Dewa,

As RAC informed to you, you can interupt the process by using CTRL+C OR kill the process.

Hope this information can help.

Cheers,
AW
now working, next not working ... that's unix
Dewa Negara_4
Regular Advisor

Re: Swinstall issue

Hi Rac & Adi,

Thanks. This swinstall command is running on the script. Other word, my script contains swinstall command to distribute our SOE package. Of course the control+C won't be applicable.

My intention is that if the script is stuck because of swinstall command, it will skip it and continue the rest of the servers.

Thanks.
Dewa
Santos
Adisuria Wangsadinata_1
Honored Contributor

Re: Swinstall issue

Hi Mr. Dewa,

You can use timeout parameter on your script for this issue; let says if there's no activity within X period, the script will jump to next system on the list.

But if you have a list of 'decom servers', the jobs will be more easiest since you can create a script to execute only on the 'non-decom servers'.

Cheers,
AW
now working, next not working ... that's unix