Fatal Error

[jim wood]

Guys,

My server crashed today and I got the following fatl error in the log:

7 FATAL 2010-01-25 08:00:04,611 TM1.System.File TM1 Server Abort: Write error on file "/prod/tgdata/TM1Planning/tm1s.log". Error = errno = 32

Any ideas? It looks like someting to do with usage tracking,

Jim.

[Steve Rowe]

I reckon disc full or maybe V scanner on file?

[Alan Kirk]

Guys,

My server crashed today and I got the following fatl error in the log:

7 FATAL 2010-01-25 08:00:04,611 TM1.System.File TM1 Server Abort: Write error on file "/prod/tgdata/TM1Planning/tm1s.log". Error = errno = 32

Any ideas? It looks like someting to do with usage tracking,

Jim.

I agree with Steve. It's not clear from the path whether that's a local drive or a network drive but if it's the latter it's possible that the network connection was lost as well. Basically it's the same issue; can't write to disk, will crash.

Crashing when it can't write rather than generating some sort of warning and letting the Admin fix the problem is one of TM1's less endearing features.

[jim wood]

Guys,

Thanks for confirming what I pretty much suspected. I have raised it with our IT Dept and they haven't seen any hard disk errors on the box and they are waiting for a response for opps regarding any other activity on the box. I'll let you know when (If they ever do) get back to me,

Jim.

PS. It's a local path Alan, a local Unix path.

[dumbom]

Check to see if theLockPagesInMemory=T in TM1s.cfg file. if this is the case, remove it and restart the server. this fixed it for me.

[tomok]

I would hope that after almost 5 years he'd have figured this one out.

[jim wood]

I would hope that after almost 5 years he'd have figured this one out.

I'm not even in the same country, nevermind the same job!!!

If memory serves, we traced it back to HDD ring fence issue on the server. as it was Unix, TM1 was ring fenced to only use certain resources. It shared the server witha couple of other apps,

Jim.