Start a Conversation

Unsolved

This post is more than 5 years old

622

May 26th, 2008 00:00

Anyone seen -OI crashing when audit file is 2GB?

I was looking at a SMARTS instance in the field that had had it's -OI crash. Suspiciously it appears to have had OI crash just after failing to write to an .audit file that was a few bytes smaller than 2GB.

Is there a limitation like this, or a way of working around it (if there is - e.g. like log file rollover)?

What made me suspicious - well it was this entry in the log ..

[20-May-2008 06:22:39 PM+567ms EDT] t@-1341129808 ICS_ActionScheduler::ICS-ActionScheduler #1
ICS-E-ARCHIVE_FILE_NEW_ALLOC-Archive entry file
'/opt/InCharge6/SAM/smarts/local/logs/TMOB-SIG-01-OI.archive' had errors
opening. Allocating new object.
-EFBIG-File too large

Any ideas?

89 Posts

May 26th, 2008 00:00

Hi,

well, i've never had such a big file, i got up to 1.2 ...
I do roll over all audit and archive files weekely in order to have small files and be capaple to look at them without having to open such huge files.
The best way to roll them over is just rename the file and a new one will be created automatically, set this in a task to do it, either when they grow up to a determinated size of on a specifid date ...
but if you look at powerlink you will find the exact error and solution under support knowlodge base case emc149093.

i hope this helps

cheers

F

54 Posts

July 2nd, 2008 02:00

Hi, Yes there is a limitation but not in the SMARTS software. We had the same problem on a unix solaris installation. The max file size was 2G (limitation on unix solaris). I'm not sure if you are running on unix as well. But I guess it could be a similar problem.
With the log rotation we could solve the problem.
Hope it helps...

53 Posts

August 13th, 2008 09:00

Ada is correct. It is an OS issue.
No Events found!

Top