| Hallo,
I have a Mac Os X server running a number of WebObjects Applications for two years now. In the morning the server was no longer reachable via ssh or via Apache.
The reason was a logfile of one Application instance which had the size of 211GB.
The instances are all scheduled nightly thus the file had piled up to that size from sometime early morning to Midday. As the webobjects logs are pure textfiles something must have gone completely wrong in this instance today to get that amount of output. Unfortunately this file had to be deleted at once (it blocked the disk) without a chance to have a look on it.
Another instance had this in the logfiles (some of this): 22192168 [WorkerThread64] WARN NSLog - <WOWorkerThread id=64 socket=null> IOException occurred while accepting server socket: java.net.SocketException: Too many open files in system 22192168 [WorkerThread65] WARN NSLog - <WOWorkerThread id=65 socket=null> IOException occurred while accepting server socket: java.net.SocketException: Too many open files in system
Has someone seen it and could this be the cause of my problem (I can image it filling a logfile when repeated often enough to a enourmous size)?
If this could be the cause, does someone know how to detect this bevore I get to a filesize of the logfile which kills the server? Or what is likely to be the reason of this. The App has been running stable for years, no large logfiles...
By the way, is there a way to detect the size of a textfile (logfile) and have a process send me a message that something goes wrong, when the file reaches a certain size?
Thanks a lot
Ute
|