Hi Stewart,
This task runs every 60 seconds to apply thresholds and possibly
raise events. If it ever takes longer than 60 seconds to complete
then the process is killed with signal 15 (SIGTERM) to make room for
the next one. You can check to see if this is happening by
examining the log file for the parent process /usr/local/inmon/server/
log/<today>/0000/inxtskd.log.
It is not a serious problem if it only happens occasionally. If it
is happening all the time then please contact support@inmon.com so we
can resolve the issue "offline".
regards,
neil
P.S. We have overhauled and reworked this aspect of the software for
ITSv5.
On Nov 15, 2005, at 1:33 AM, Jessop, Stuart wrote:
> I've been getting this error on my server since I installed it. I'm
> running 4.0.46 on RH 9 under VMWare. Anybody have ideas?
>
>
> thanks
>
> stu...
>
> -----Original Message-----
> From: InMonServer@hdqrkdseinmon1.marriott.com
> [mailto:InMonServer@hdqrkdseinmon1.marriott.com]
> Sent: Monday, November 14, 2005 7:27 PM
> To: Jessop, Stuart
> Subject: process event (severe) failed inxStreamMonitor
>
> Severity = severe
> Type = process
> Name = failed
> Value = inxStreamMonitor
> URL =
> http://hdqrkdseinmon1.marriott.com/its/query/Events?type=process
> Comment = module=runStreamMonitor,died_on_signal=15
Received on Tue Nov 15 08:20:27 2005
This archive was generated by hypermail 2.1.8 : 11/15/05 PST