Cognos Content Manager is running in Standby Mode

[krishnadwbi]

Hi Friends,

In our production we are facing 1 similar issue for every 15 days. We have 2 App Servers and those are connected to same Content Manager.
But for every 10 to 15 days our Content Manager is going to Standby Mode. Once it went to standby mode reports will not run as normal and the scheduled reports will go to pending state.

Every time, once we restart the Cognos services than only it's coming to normal state.

I would like to understand is there any way to overcome this or what could be the reasons to this problem.

If anybody wants to discuss about this issue please give me a miss call or please whatsapp.

Your earliest response in this regard would be highly appreciated.

Thanks in Advance.

Regards
Krishna M

[MFGF]

Hi Friends,

In our production we are facing 1 similar issue for every 15 days. We have 2 App Servers and those are connected to same Content Manager.
But for every 10 to 15 days our Content Manager is going to Standby Mode. Once it went to standby mode reports will not run as normal and the scheduled reports will go to pending state.

Every time, once we restart the Cognos services than only it's coming to normal state.

I would like to understand is there any way to overcome this or what could be the reasons to this problem.

If anybody wants to discuss about this issue please give me a miss call or please whatsapp.

Your earliest response in this regard would be highly appreciated.

Thanks in Advance.

Regards
Krishna M

Hi,

If you have two app servers configured to use the same content manager, then you only have one content manager - so there would be no option for it to go into standby. It would either be running or not running. The fact you are seeing it go into standby means you must have a second content manager that is becoming the active one. Can you clarify how you have configured your install?

If you have two content managers, one will be active (the one that starts first) and one will be in standby. If the first content manager dies or the Cognos service it uses is restarted, the standby content manager becomes active so that the Cognos instance can continue to work. When the first content manager restarts, it recognises there is already an active content manager and it becomes the standby. It sounds to me like this is what might be happening in your case.

You should first check the configuration to see where both content managers are - you MUST have more than one to see this behaviour. Next you should check the configuration of the second (standby) content manager to make sure it is using the exact same authentication provider configuration and content store configuration as the main one (I suspect one or both is configured differently on the standby). Then you should figure out why the main content manager is dropping out - check the cogserver.log on the machine this runs on to see what is happening.

Please don't post email addresses and phone numbers onto Cognoise - to protect us and yourself. Please read the Forum Etiquette post here - specifically point 7.

Cheers!

MF.

[mcc.chernandez]

To add on to MFGF - if this is happening regularly, do you have some scheduled task somewhere that is interrupting things? For example, if the CM server cannot reach the Content Store DB then the failover could occur. Search your cogserver.log files for entries that contain "CM-SYS" to see if there is anything relevant. If your standby CM server does not have the same services enabled or the same Notification settings in Cognos Configuration then that may cause the scheduled objects to stay in a Pending state. Are you using Server Groups/Routing rules?