tm1msg.log error in 9.0 SP3

[Sandhya Kumar]

Hi,

Our TM1 server went down twice today with the below error in tm1msg.log:

2009/11/18 21:03:08:Out of Memory - Clients will not log out, auto aborting
'
'
'
2009/11/19 00:12:49:Out of Memory - Last client gone, aborting

Could someone help me on finding the cause of this error? Our server has 16GB RAM and we have not faced this problem before.

Thanks~

[Martin Ryan]

Unfortunately 16GB is not a massive amount anymore, particularly if there are less than ideal feeders and rules in play. I would investigate the cause that is suggested by the log, i.e. that you've hit the RAM limit and the server has crashed. Have a look at RAM levels during run time and see if it's close to the limit. Unfortunately, afaik, there is no way to retrospectively see RAM levels, they must be watched real time.

My guess, if this has never been an issue before, is that you have a cube that has some poorly written feeders/rules that are getting triggered and causing a blow out in RAM. You can check the level of each of the cubes using the properties window in server explorer.

Martin

[Steve Rowe]

But... I'm guessing that the Sandhya is on 64 bit (otherwise why have 16GB of RAM)

In 64bit Windows OS (again an assumption) there is no upper limit to the size of the server in the same way that there is in the 32 bit world. So a 64 bit server should not crash with this message assuming you are running 64 bit TM1 too.

A guess could be that the Sandhya is running 32 bit TM1 on a 64 bit and is bound by the 4 GB limit?

Can you tell us more about your operating environment?
Cheers,

[David Usherwood]

There is, still, a limit on the RAM which a 64 bit server can take - but it's rather high - 16 terabytes. Of course you can't buy this in 2009, but remember who said 'why would anybody need more than 640meg?'.

And I can confirm, having seen it happen an hour ago in a place in Wales you will remember well, that when a 64bit server runs out of physical RAM, and no pagefile is set, it will crash. (It has a pagefile now ).

[Alan Kirk]

There is, still, a limit on the RAM which a 64 bit server can take - but it's rather high - 16 terabytes. Of course you can't buy this in 2009, but remember who said 'why would anybody need more than 640meg?'.

{Cough} At the risk of dating us all, 640k

It was back in the days when someone came close to swooning away when they found out that I had an Amiga with a big ol' 3 megabytes of RAM on board.

[Martin Ryan]

But doesn't the physical amount of memory on a 64 bit box limit it? If there's only 16GB of RAM and the model hits 16.1GB won't that cause a crash of the type described? Or does it error in a different way? I've yet to have a 64 bit server hit the physical RAM limit, so I don't know how the error would show up.

Though your suggestion of 32 bit software on 64 bit software does sound more likely.

Martin

[Alan Kirk]

But... I'm guessing that the Sandhya is on 64 bit (otherwise why have 16GB of RAM)

Multiple sessions on the one box. But you're right, it would be useful to know.

But doesn't the physical amount of memory on a 64 bit box limit it? If there's only 16GB of RAM and the model hits 16.1GB won't that cause a crash of the type described?

I doubt it. 64 bit servers can use virtual memory the same as 32 bit ones can:

The total amount of memory that is available to programs is the amount of physical memory in the computer in addition to the size of the pagefile.

http://support.microsoft.com/kb/294418

It would slow the server down (since it would no longer be in (real) memory), but shouldn't crash it. As far as I know applications don't "know" whether they're using physical or virtual memory.

[lotsaram]

But doesn't the physical amount of memory on a 64 bit box limit it? If there's only 16GB of RAM and the model hits 16.1GB won't that cause a crash of the type described?

In my experience no. In Windows x86 the OS imposes a 2Gb (or 3Gb) upper limit per application, if TM1 breaches the limit then we all know what happens. But in x64 there is no "upper per application limit" if the amount of physical RAM is insufficient then TM1 will page and generate huge swap files, but it won't crash per se (although this is a moot point as once TM1 starts running on a mix of page files and physical RAM everything slows to the point of the application becoming completely unusable requiring a restart to fix.)

[Sandhya Kumar]

Thanks all!!

Before I finish reading all of them, my server is 64-bit and so is TM1 installed in it..

[David Usherwood]

First, my apologies for my senior moment - 640k was indeed the famous limit.
But, as posted with that erroneous statement - when 64 bit first came out I enquired about the upper limit and was told it was, indeed, 16 terabytes. You can't buy a server with that amount of RAM now, but watch this space.
And I can definitely confirm (can't I, Gareth) that when a 64 bit box running a set of TM1 servers wants more RAM than Windows can provide, the TM1 service wanting the RAM will keel over.