Hi Samuel, thanks for this hint - it seems to work now. We did not have any disruption til our rule insertion as you described. Apart from that we now have FW-1 SP7 and no problems at all (so far). Thanks to all of you for assistance. Regards, Best regards Gerd Lienemann Pilkington Gelsenkirchen IS Communications Tel +49 209 168 2620 Fax +49 209 168 2289 > -----Urspr�ngliche Nachricht----- > Von: Samuel Wuethrich [SMTP:[EMAIL PROTECTED]] > Gesendet am: Dienstag, 15. August 2000 14:47 > An: '#Checkpoint' > Betreff: RE: [FW1] [FW-1] eSafe CVP hangup with FW-1 SP6 > > I have had the same behaviour running eSafe on a Intel machine. The CPU > always gets to 100% utilization _after_ detecting a virus, malformed java > applet or something like this. The solution according to Aladdin was to > create a rule which allow eSafe sending its smtp alert (because we are > using > this) without checking itselfs for viruses. This new rules should be > placed > before any other rules doing smtp viruschecking. Don't know, why it > happens > like this, but it works now. > > Regards, > > sAM > > ~> -----Original Message----- > ~> From: #Checkpoint [mailto:[EMAIL PROTECTED]] > ~> Sent: Dienstag, 15. August 2000 12:04 > ~> To: [EMAIL PROTECTED] > ~> Subject: [FW1] [FW-1] eSafe CVP hangup with FW-1 SP6 > ~> Importance: High > ~> > ~> > ~> > ~> Hello all, > ~> > ~> we are nearly dispairing!!! > ~> > ~> After we upgraded our FW-1 4.0 to SP6 we have SEVERE > ~> problems with our eSafe > ~> protect gateway Version 2.1 (meanwhile build 99). Every > ~> one/two days the > ~> RSERVER.EXE process from eSafe jumps to 100% CPU utilization > ~> and the eSafe > ~> server was in "nearly hangup state" (nearly means: response > ~> time for a > ~> simple login approx. 20 - 30 MINUTES; so a restart is always > ~> required). > ~> > ~> As soon as this effect happens, no more scanning of our > ~> services http, ftp > ~> and smtp is possible (so these communications are blocked) > ~> and all mails are > ~> stored in directory $FWDIR/spool of our AIX system 4.2.1 > ~> (RS/6000 model P43, > ~> 128 MB memory). Everything (not really everything, as the > ~> http 1.1 eSafe > ~> problem caused lots of troubles, so we had to move to SP6 > ~> and modified the > ~> objects.C file as recommended in FW-1 release notes) worked > ~> fine BEFORE this > ~> upgrade to SP 6. > ~> > ~> We executed all advice from our consultant but without > ~> success (updating the > ~> eSafe software, deactivating the automatic update feature). > ~> So we will now > ~> do a specific debug which may bring us and our consultant > ~> more detailed > ~> information for the analysis. However, if there is ANYONE > ~> WHO KNOWS THIS > ~> PROBLEM PLEASE CONTACT US!!!!!!!! Thanks a lot in advance. > ~> > ~> Best regards, > ~> > ~> Best regards > ~> > ~> Gerd Lienemann > ~> > ~> Pilkington Gelsenkirchen > ~> IS Communications > ~> Tel +49 209 168 2620 > ~> Fax +49 209 168 2289 > ~> > ~> > ~> > ~> ============================================================= > ~> =================== > ~> To unsubscribe from this mailing list, please see the > ~> instructions at > ~> http://www.checkpoint.com/services/mailing.html > ~> ============================================================= > ~> =================== > ~> ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
