TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
Hi
To add another voice to this. RS 5.0 XU 1.3 on Solaris 7 (U-10). I have
always (since 5.0) had the synch error on the last record but it seems to be
bogus - another sync and it clears the error. More of concern is the way the
network_engine just stops detecting anything - no coredump, no error
message, nothing - it just eats a lot more cpu (but not 100%) and I can sync
what there was detected before it goes in to never-never land.
Support suggested a Windows solution - re-install everything (this should
not be needed in UNIX-land) - but it, of course, makes no difference. Never
seems to be related to any particular event. Just stops and needs a kill -9
to bring it down.
Running cron jobs to detect a core or a non-existent process is easy (from
Solaris 7 see pkill, pgrep) but much harder to detect that an app is now
plain useless. Anyone else seeing this - I preferred coredumps as at least
they can be detected and restarted.
regards
Neil
>
> Welcome to the world of RealSecure. I have seen this problem numerious
> times. I have core dumps,and that still isn't resolved. I wrote a cron job
> to shutdown and start the end every hour, that seemed to help a bit.
> happened less often. Are you working with a high speed network?
>
> -----Original Message-----
> From: Baeder, Jason (GEIO)
> To: '[EMAIL PROTECTED]'
> Sent: 12/1/2000 4:40 PM
> Subject: Invalid records error when database synchs
>
>
> TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message
> to
> [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
> problems!
> ------------------------------------------------------------------------
> ----
>
> > All,
> >
> > I am using RS 5.0 MU 1.3; sensor is on Solaris 2.7.
> >
> > From time to time when synching the database, either manually or
> > automatically, the console has reported "Invalid Records were
> detected,
> > and skipped. Check the detector log database for corruption.
> > [ID=0xc725004]".
> >
> > As a remedy I have reinitialized the .par, .tag and .raw files, and
> > restarted the console with a skeleton of rsntclientlog.mdb. But the
> error
> > still continues.
> >
> > If I run a report preview, all of the events in the activity tree
> appear
> > in the report. I'm wondering if this is a bug I can ignore (??).
> Where
> > on the sensor can I check for signs of database corruption? What else
> can
> > I do to correct the problem?
> >
> > TIA,
> > Jason Baeder
> >
> > GE InterBusiness Operations
> > __________________________________________________
> > Jason Baeder
> > Systems Integrity
> > Phone: (301) 340-5074 Fax: 301-340-4639 DC 8*273-5074
> > Internet Email: [EMAIL PROTECTED]
> > 100 Edison Park Drive, 2-3B1, Gaithersburg, MD 20878
> >
> >
> >
>
>
>
>
