[453] in Moira

home help back first fref pref prev next nref lref last post

Re: prlogger update failed (MOIRA)

daemon@ATHENA.MIT.EDU (Richard Basch)
Fri Sep 11 16:30:12 1992

Date: Fri, 11 Sep 92 16:29:24 -0400
To: kim@MIT.EDU
Cc: jis@MIT.EDU, mar@MIT.EDU, op@MIT.EDU
Cc: moiradev@MIT.EDU
In-Reply-To: Kim Carney's message of Fri, 11 Sep 92 15:16:42 EDT,
From: "Richard Basch" <basch@MIT.EDU>


   From: kim@Athena.MIT.EDU
   Date: Fri, 11 Sep 92 15:16:42 EDT
	. . .
   I'm not sure why. Using the dcm logs I've traced it to the following:
   Sep 11 02:50:39 <27763> dcm:  running /u1/sms/bin/prlogger.gen
   Sep 11 02:50:40 <27763> Fatal error 1330
   Sep 11 02:50:40 <27763> dcm: Unknown code sms 255 /u1/sms/bin/prlogger.gen exited
   Sep 11 02:50:40 <27763> dcm: DCM building config files for prlogger: Unknown code sms 255

   prlogger.gen is a binary.  I'm not sure where to look for moira source. I've 
   looked around in moiradev, but I don't have permission on the src directory.

   I've reset the error for now.

I thought everything on the Moira server was also in "opssrc", but it
seems that prlogger.dc is the exception.

Anyway, I could not locate the error message in the code, but
interestingly enough, error 1330, according to Ingres manuals, indicates:
	Illegal context of %0 without preceding CONNECT statement. Exiting...
According to /usr/rtingres/files/error.1, it is merely:
	Illegal context of %0

I would suspect the "Fatal error 1330" was printed prior to the
successful setup of the error handler within prlogger.dc, though this
seems rather strange since the first SQL statement is a CONNECT and the
second is the setup of the error handler.

Disclaimer: I am just as confused as you, so this information may simply
be a result of looking down the wrong path.

-Richard

home help back first fref pref prev next nref lref last post