nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Impact of stopping and staring the event subsystem.

TroyP

We have had TS go down a couple of times when we had problems with our event subsystem database.

IWOV gives stop and start commands for the event subsystem. What is the impact of stopping and starting the event subsystem with TS running?

Does TS work after you stop the evet subsystem? What is the risk of "event" loss Smiley Very Happy

?

I have seen some procedures that make you do an iwreset -ui to "make sure the event subsystem has restarted". Others say you need to do and iw.server restart.

We are on TS 6.7.1 SP1.

Find more posts tagged with

Comments

nipper

Doubtful that there are any significant issues. It is possible that the search index may be slightly out of sync.

It should restart the search engine and index. When I restart it I do a iwreset -a as well.

Now the big question is WHY do you need to restart it ?

TroyP

Now the big question is WHY do you need to restart it ?

We are moving our DB and was told as part of the process we need to stop/start the event subsystem. You say you do a iwreset -a anyway. Why do they even have the stop and start commands for the event subsystem?

These instructions were taken right from the admin guide under "configureing the event subsystem manually.
7. Start the Event Subsystem by running the iw-home/private/bin/iweventsubd
script.
8. Restart the Interwoven servlet engine to ensure that the Event Subsystem servlet is
started; this can be done by issuing an iwreset -ui command.

nipper

iwreset -a does just a more complete restart of processes. servletd is the most important which is covered by iwreset -ui. As a habit I always use iwreset -a instead of -ui

Either should work just fine.

Firenze

If you schedule the move during a maintenance window and freeze the content store, then you should be able to mitigate event loss.

If you are expecting to have restart the event subsystem a lot of times then bouncing it individually may be helpful otherwise I would just restart the TeamSite services to ensure that the initialization sequence is correct.