[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [FW1] Re: log message queue is full
We are running into the same problem on a Sun E250 with FW-1 4.1 SP2. This suppose to be the latest release. The average outage is about 6 days apart. BTW, doing fwstop and fwstart won't help. I was manage to do fwstop before it locked up (at that time fwd already die) and fwstart will make it run for another 3 hours or so. But eventually it still hang. The answer is to reboot it regularly and looks like that is the only way to release something. I think there is a memory leak somewhere. Ken Date: Wed, 1 Nov 2000 16:24:49 -0600 From: Lou Sortman <[email protected]> Subject: Re: [FW1] log message queue is full I get this too. Unfortunately, the FAQ only mentions a case where the logger isn't fast enough. I suspect that in our case, it has quit altogether; as opposed to simply falling behind. Of course, when the problem comes up, I cannot get onto the machine to try starting the logging daemon. The console is unresponsive, which, I assume, is what you mean by "the firewall crashed". I'm trying to work out something to fwstop/fwstart when the problem is dected in the vain hope that it might actually fix it before the machine gets wedged. I'd rather it simply didn't happen in the first place. On Mon, Oct 02, 2000 at 01:29:46PM -0400, Ladie Geronimo wrote: > > HI! > > Have anyone encountered the same problem? I'm running CKPfw V4.0p5 > on a Solaris 2.6 and get this error message: > > unix: FW-1: log message queue is full > unix: FW-1: lost 512 log/trap messages > > Then, the firewall crashed. > > Any suggestion is appreciated. > > PS: Please reply to my email address and I'll summarize. > > TIA -- Ladie ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|