order of servcices start and stop

I currently have the following in a batch application used when I need to bring down all of TeamSite and OpenDeploy and then bring it all back up.

#Stop Services
prod.stop.service.1=D:/Interwoven/Teamsite/bin/iwreset -ui stop
prod.stop.service.2=net stop iwutild
prod.stop.service.3=net stop iwserver
prod.stop.service.4=net stop iwodadmin
prod.stop.service.5=net stop iwas
prod.stop.service.6=net stop iwod60

#Start Services
prod.start.service.1=net start iwutild
prod.start.service.2=net start iwserver
prod.start.service.3=D:/Interwoven/Teamsite/bin/iwreset -ui start
prod.start.service.4=net start iwod60
prod.start.service.5=net start iwas
prod.start.service.6=net start iwodadmin

I now want to add Event Subsystem, TeamSite Index and TeamSite search into that batch application.

Where is the best location in the above start and stop list to insert the stop and start of these additional three services?

Note: When starting search related services independantly I Stop search, Stop index, stop, then Start index, Start search. If Event Subsystem is down I start it first.

Find more posts tagged with

Comments

SethHickel

thinking this:

Future stop commands:

\Interwoven\Teamsite\bin\iwreset -ui stop
net stop "iwtsindex"
net stop "iwtssearch"
net stop "iweventsubd"
net stop "iwutild"
net stop "iwserver"
net stop "iwas"
net stop "iwod60"

Future start commands:

net start "iwutild"
net start "iweventsubd"
net start "iwserver"
net start "iwtsindex"
net start "iwtssearch"
d:\Interwoven\teamsite\bin\iwreset -ui start
net start "iwod60"
net start "iwas"
net start "iwodadmin"

Ugan

I think you are running extra commands which are not required.

ex : iwreset & utild is not required when you are restarting iwserver (it does already).

Always the order should be :

Stop teamsite server first and then its components (like OD, Search) and then vice versa (start components and then teamsite).

Migrateduser

To expound upon the previous post, iwreset does not stop service(s), it only restarts them. There is no "stop" or "start" option for the iwreset command.

You'll need to stop iwwebd, iwproxy, and iwservletd services instead of using iwreset.

nipper

To expound upon the previous post, iwreset does not stop service(s), it only restarts them. There is no "stop" or "start" option for the iwreset command.

iwreset -h

You will see that there are start/stop options now (at least in TS 7)

Migrateduser

Dang, guess I should have done iwreset -h and tested it out before my first post as the stop and start option are available in version 6.7 as well.

Of course it's not documented in the command line reference.

I did find it mentioned in the installation guide of 6.7.2 as part of the post-installation troubleshooting routine. I did not find it in the 6.5 installation guide, so perhaps it's new to version 6.7 and up. Since I don't have version 6.5 I cannot confirm this.

Looking at SethHickels previous posts it looks like he has version 6.7.1 and should probably be able to use it. But, I would guess he already knows that by now and I'm just rambling.

SethHickel

My batch returns the following from the iwreset -ui stop command

Executing command:: cmd /c /Interwoven/Teamsite/bin/iwreset -ui stop
Stopping UI. This operation takes some time
Please wait...
Performing cmd /c net stop "iwuiadmin" > nul: 2>&1 ...
Performing cmd /c net stop "iwservletd" > nul: 2>&1 ...
Performing cmd /c net stop "iwproxy" > nul: 2>&1 ...
Performing cmd /c net stop "iwwebd" > nul: 2>&1 ...
iwreset -ui stop Exit Value= 0
Command executed succesfully.

And then from iwreset -ui start

This from TeamSite 6.7.1

Executing command:: cmd /c /Interwoven/Teamsite/bin/iwreset -ui start
Starting UI. This operation takes some time
Please wait...
Performing cmd /c \INTERW~1\TeamSite\iw-webd\bin\iwwebd_conf.ipl > nul: 2>&1 ...
Performing cmd /c net start "iwwebd" > nul: 2>&1 ...
Performing cmd /c net start "iwproxy" > nul: 2>&1 ...
Performing cmd /c net start "iwservletd" > nul: 2>&1 ...
Performing cmd /c net start "iwuiadmin" > nul: 2>&1 ...
iwreset -ui start Exit Value= 0
Command executed succesfully.

Ugan

and just to add for the order of execution of services for teamsite and teamsite components.

Stop teamsite first.
For OD : Stop od,odadmin,access == Start access,odadmin,od.
For Search : Stop search,index,eventsubsystem == Start event,index,search.
Start teamsite last.

Use teamsite,search,od in order of execution.

Ugan

FYI ...

iwserver start/stop (includes iwreset operation)
iwreset -a does the utild start and -ui operations (which you were explicitly doing)

SethHickel

So - do we agree that the following is an OK order?

#FUTURE Stop Services
prod.stop.service.1=D:/Interwoven/Teamsite/bin/iwreset -ui stop
prod.stop.service.2=net stop "iwtsindex"
prod.stop.service.3=net stop "iwtssearch"
prod.stop.service.4=net stop "iweventsubd"
prod.stop.service.5=net stop iwutild
prod.stop.service.6=net stop iwserver
prod.stop.service.7=net stop iwodadmin
prod.stop.service.8=net stop iwas
prod.stop.service.9=net stop iwod60

#FUTURE Start Services
prod.start.service.1=net start iwutild
prod.start.service.2= net start iweventsubd
prod.start.service.3=net start iwserver
prod.start.service.4=net start iwtsindex
prod.start.service.5=net start iwtssearch
prod.start.service.6=D:/Interwoven/Teamsite/bin/iwreset -ui start
prod.start.service.7=net start iwod60
prod.start.service.8=net start iwas
prod.start.service.9=net start iwodadmin

ISCBorisB

So - do we agree that the following is an OK order?

#FUTURE Stop Services
prod.stop.service.1=D:/Interwoven/Teamsite/bin/iwreset -ui stop
prod.stop.service.2=net stop "iwtsindex"
prod.stop.service.3=net stop "iwtssearch"
prod.stop.service.4=net stop "iweventsubd"
prod.stop.service.5=net stop iwutild
prod.stop.service.6=net stop iwserver
prod.stop.service.7=net stop iwodadmin
prod.stop.service.8=net stop iwas
prod.stop.service.9=net stop iwod60

#FUTURE Start Services
prod.start.service.1=net start iwutild
prod.start.service.2= net start iweventsubd
prod.start.service.3=net start iwserver
prod.start.service.4=net start iwtsindex
prod.start.service.5=net start iwtssearch
prod.start.service.6=D:/Interwoven/Teamsite/bin/iwreset -ui start
prod.start.service.7=net start iwod60
prod.start.service.8=net start iwas
prod.start.service.9=net start iwodadmin

Looking good.

It all boils down to the Servers' dependencies. Therefore, normally this sort of things follows mutually reverse sequences.
(stop a,b,c / start c,b,a). You have small stop/start discrepancies in that respect (search vs index, etc). It may be of course
irrelevant.

myth

I have a similar order for start and stop. This is done each night for a backup.
For the past couple of weeks, I am seeing intermittent nights when iwserver does not stop and I have to manually stop it with a kill command.

What could be the cause. There is nothing on the server log. Trace log also shows all the information except "watch event thread stopping" is not shown on the days when iwserver does not stop correctly.

Any ideas on what "watch event thread stopping" means? I have read all the documentation and support site case notes with absolutely no reference to watch event thread.