Integrated Login - Server Crash

[deepakjain2020]

Hi All,

We have setup IntegratedSecurityMode = 5, but when we connect Tm1server.log captures below details.
If many users hit TM1 Server, it crashes.

2480 [4] DEBUG 2016-03-09 16:39:26.621 TM1.APIDetail.Return.Index RetIndex: index = 6
2480 [4] DEBUG 2016-03-09 16:39:26.621 TM1.APIDetail.Return.Index RetIndex: index = 6

There is nothing more apart from above details in log before it crashes.
Can someone please share knowledge on what exactly it means, and why it is happening?

If any more information is required please let me know.

Regards,
Deepak Jain

[qml]

These lines in your tm1server.log mean that you have debug-level logging for the TM1.APIDetail logger or one of its descendant loggers. Nothing more, nothing less. By itself these entries say nothing about your crash and the reasons for it.

The best advice I can give you is to log a PMR with IBM and upload as much detail as possible (tm1s.cfg, cmplst.txt, tm1server.log, detailed description of circumstances etc.), the most important piece of the puzzle being a full crash dump. Use Windows Error Reporting, ADPlus or Dr Watson to capture the crash dump when your service crashes. From there the engineering team should be able to figure out the state of the service at the time and what might have happened.

Of course, depending on the version of software you are on, you could just try and upgrade and see if the problem is resolved. That could be the quickest solution.

[Elessar]

Hello!
Here are IBM's guidelines on how to analyse server crash: http://www-01.ibm.com/support/docview.w ... wg21417409

Note that server_crashes are usually very difficult to debug. If you can determine the cause of the crash, it'll be 95% of all the work. You can collect tm1top, OpsConsole, tm1s logs to determine it.

[deepakjain2020]

Hi All,

Those records of debug are generated when any user connects for first time, not sure is it because of integrated security mode: 5.
Anyways will connect with IBM folks and check on it.

Regards,
Deepak Jain

[qml]

I am seeing the same behaviour (i.e. the logger TM1.APIDetail.Return.Index printing random DEBUG messages when new users connect via CAM) after upgrading to 10.2.2.5. No idea if it has anything to do with stability I have not yet seen any crashes with that version. But the logger messages seem to be a defect and I'll raise it with IBM too.

[deepakjain2020]

Hey friend,

It never crashed for us in test environment when either one or two users login and that too at different time.
It will crash when many users hit the server at same time.

Further observation:

To be more specific, 20 records of debug are generated in server log for one user login.
It happens only for first time when user connect to TM1 Server.

Regards,
Deepak Singhvi

[qml]

Deepak, what version are you on? 10.2.2 FP5?

[deepakjain2020]

Hi Kamil,

Product version is 10.2.20300.86 (assuming 10.2.2 FP3).

Regards,
Deepak Jain

[deepakjain2020]

Hi Kamil,

Approach which I discussed among our team is to get list of users in csv file i.e. (CAM ID and Username), and then load them into "}Clients" dimension using TI process.
If you have any alternate ideas, please share.

Regards,
Deepak Jain

[qml]

Approach which I discussed among our team is to get list of users in csv file i.e. (CAM ID and Username), and then load them into "}Clients" dimension using TI process.If you have any alternate ideas, please share.

If you have a well-defined user base then prepopulating the }Clients dimension with all the needed CAM IDs can be a good idea.

In 10.2.2 FP5 there is also a new config parameter CreateNewCAMClients that, when set to 'F' allows you to prevent the }Clients dimension being updated when new CAM users log on. The downside is that users won't be able to log on until you run a script to add them in. The upside is that you can get rid of a fair bit of on-logon locking and - in your case - probably prevent the server from crashing.

[deepakjain2020]

Thanks Kamil for sharing info