Dipatchers - not running

[Former Member]

Hi Experts,

While running check config script "./Dispatcher_Service_idmdispatcherhk1.sh test checkconfig, I am getting following warning. I've restarted the dispatchers to and check duplication in naming the dispatchers. Although, it shows 'running' status in MMC (Identity Center) on status tab. Does anyone know why it is throwing up this warning.

"STOP_DISPATCHER field in the mc_dispatcher table for dispatcher 'idmdispatche

This indicates that dispatcher 'idmdispatcherhk1'

    - has been previously stopped abruptly

    - or other dispatcher with same name is already running

Please verify this condition - it may have serious impact on whole IDM enviro

Cleaning of existing semaphores is NOT carried out"

Thanks

AR

[former_member2987 · Accepted solution]

Hi Abdur,

I'm going to make a couple of assumptions here:

1. You are using IDM 7.2

2. The dispatcher in question is running on a LINUX/UNIX system.

I'd first try removing and re-installing the dispatcher.  I'd also review this document: , even though it's for 7.1, most of the content still applies.  You can also check this blog entry for some other useful material: http://idm-thoughtplace.blogspot.com/2012/03/doing-linux-based-victory-lap.html

Let me know if you have other questions.

Regards,

Matt

[Former Member · Accepted solution]

Matt - Thanks for your kind reply!

[Former Member]

You get this message if the dispatcher was terminated without being able to set a stopped status (STOP_DISPATCHER) and clearing it's session-id to the DB, by using kill or ctrl+c instead of the "stop" button in the MMC.

Depending on the version you have there's a STOP_DISPATCHER column and optionally a session-id column in the dispatcher table. The dispatcher writes a unique string to the session column when starting, and keeps checking this while running to make sure another dispatcher with the same name has been started (in which case the session-id field would have been changed by the new dispatcher and the "old" dispatcher with the mismatched session will then terminate itself).

If the dispatcher cannot determine if the last started dispatcher shut down succesfully it throws the warning you mentioned. Beyond that the message also means that this dispatcher will not pick up tasks that were locked by its predecessor/clone untill they time out (300 seconds from allocation time, listed in mc_semaphore).

Br,

Chris