TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

Gary!

If your RS log is set to the default of 50,000 records and 90% DB
HighWaterMark then this could be the cause of your problem.  If you're in a
heavily trafficked environment, the DB will have problems synch'ing under
such circumstances.  You might want to try lowering the DB highwatermark%
and increasing the max log records (say 100,000 or so).

If you still encounter the problem, please contact Tech Support at
[EMAIL PROTECTED] (404-236-2700 / 1-888-447-4861)

Cheers,

==================================
Brian Fitch, IDS Support Engineer
Internet Security Systems, Inc.
==================================

-----Original Message-----
From: Gary McIntyre [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 17, 2001 12:00 PM
To: [EMAIL PROTECTED]
Subject: Re: RealSecure: Sync Problems



TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------

I have experienced similar problems with the 5.5 console running the 5.0
engines and sensors.  The Auto Sync works normally and downloads any
outstanding events once the threshold has been reached.  However, if any new
events have been generated since the Auto Sync started, it starts another
Auto Sync run to download the new events.  If any new events have been
generated since *that* Auto Sync started ...  and so on, until there are
absolutely no new events to download.  On a busy proxy server (for example),
this may never happen, and in the meanwhile, the other Auto Sync activities
may start to queue up...

Unfortunately, I have not found a solution to this one.  Stopping the DB
operation rarely works without freezing the entire console.  Restarting the
console *will* stop this, but who wants to restart the console every time
this happens?.  You can also pause that particular sensor (if the console
will let you) until the DB operation is complete, but the sensor is
essential blind for those few seconds and there is no way (that I know of)
to automate this.  Anyone else with better solutions than this?

Gary McIntyre

----- Original Message -----
From: ""Steve Robinson" <[EMAIL PROTECTED]>@LGS"
<IMCEANOTES-+22Steve+20Robinson+22+20+3Csfr+40mediaone+2Enet+3E+40LGS@e-comm
erce.com>
To: <[EMAIL PROTECTED]>; "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]>
Sent: Tuesday, January 16, 2001 5:36 PM
Subject: RE: RealSecure: Sync Problems


>
>
> TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message
to
> [EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
> problems!
> --------------------------------------------------------------------------
--
>
> Jeff,
>
> It sounds like the database is filling up faster than the sync can keep up
> with it.  Have you tuned the policy to eliminate noise? How fast are your
> logs on the console growing?  I would suggest setting this threshold up to
> around 125k to see if this is the problem
>
> Steve Robinson
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Jeferson Stabille
> Sent: Tuesday, January 16, 2001 5:40 AM
> To: [EMAIL PROTECTED]
> Subject: RealSecure: Sync Problems
>
>
>
> TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message
to
> [EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
> problems!
> --------------------------------------------------------------------------
--
>
> Hi,
>
> I'm having problems with Real Secure Sync process. After 25k log entries,
> Real Secure initializes the sync process normally. After that, Real Secure
> starts the sync process continously, for every new group of entries,
without
> waiting to reach the water mark again (25k log entries).
>
> My environment is composed by:
> - ISS Real Secure Management 5.0
> - ISS Real Secure NetWork Sensor 5.0
> - Windows NT 4.0 WKS + Sp6
> - SQL Server 7 as Database Server
>
> Best Regards,
> Jeferson Stabille
>
>
>
>
>
>




Reply via email to