Automatic Active Sync failed to Start at appropriate time
Hellos,
Its holiday season here. We had a FF Active Sync process that failed to start up.
Ops noted an overheating CPU at 2am. Server was brought down.. App server stopped, Database stopped. Fan fixed and Server rebooted.. Database started Ok, App server started Ok.. according to AS Log idM started up ok... but the 'automatic' Active Sync process refused to start.
What could prevent it?!
I have seen various people's opinions.. e.g.
"Hi,
There can be lot of reasons , for not starting activesync.
if you are using activesync between SIM and database ,
then lets start from activesync wizard ,
1)check the i/p activesync form(version should be correct)
2)check the startup type
3) if you are using query based activesync
check the first and last predicate fields and you need to ensure that the logic you have used in i/p activesync form will generate some processing once you start active sync otherwise you will not see active sync in executing state.
you can check weather activesync has performed operation or not in IAPI in the debug page under configurator
if your CPU utilisation on server is very high activesync will not start
these are general things
if you can give some more specific details abt your application and problem i can help you out.
Warm Regards,
Gajanan"
This process had been left unstarted for some time. Noone checked.. why should they.. its automatic (obviously IdM isnt an R.E.M. fan)
Surely an automatic start type should (re)start after a reboot for hardware reasons!
Is the only thing we can we put in a Solaris shell script to test that these ****ing active sync process have been started and are running after a reboot/restart of App.server is a date test of the log file? i.e. if log file has not been touched in x days raise an alarm... seems something that is better built into IdM than a script.
How has this problem been faced and met by others out there? I am sure we are not the only people who have had to shutdown and restart IdM.
