xlate error causing process PANIC

[David Dillard]

One of our processes occasionally shuts down in a PANIC and I am having trouble figuring out what exactly the problem might be.

The engine log indicates that there is a problem in an xlate but I cannot narrow it down:

Code:

[msg :RecD:INFO/1:NEToutbound_xlate] Unable to get HL7 segment information: Segment ‘NOSEG’ not found
[msg :RecD:INFO/1:NEToutbound_xlate] Unable to load segment definition ‘NoSeg’.
[msg :RecD:INFO/1:NEToutbound_xlate] Unable to get HL7 segment information: Segment ‘NOSEG’ not found
[msg :RecD:INFO/1:NEToutbound_xlate] Unable to load segment definition ‘NoSeg’.
PANIC: “vsiSrc != ((struct VvSegInfo *) 0)”
PANIC: Calling “pti” for thread NEToutbound_cmd

I have tried running the last message the process was working on at the time it panic’d in all of the xlates but cannot find an error.  I’ve even tried sending the batch of messages into the engine again to try and recreate the panic but they just process fine withtout a problem.

If someone could point me in a direction to look that would be great.

Topic

[Charlie Bursell]

First turn on enable_all for both the process and Xlate so you can see what was going on when it crashed.

[Author]

Replies