Write on scoket 127 failed: 32 Broken pipe

[William Grow]

Hi,

 I am getting an error message from the engine that I don’t know the meaning for.  The message reads as follows

08/31/2005 11:50:23 [icl:tcpi:ERR /0: series_xlate] write on socket 127 failed: 32: Broken Pipe

I read from an earlier post that the solution could be to rebuild the icl database.  Is this needed here as well ? If so, can someone explain why?

Topic

[Charlie Bursell]

Looks like the socket for intercommunications between the Xlate engine and the engine got lost.  You know its the Xlate engine because the thread reporting it is the Xlate thread xlate_series.

You can run netstat -an | grep 127 and see what the status on that port is or you could simply try to init the ICL database, hcidbinit -i.  

As to why it happens.  Why does a lot of stuff happen with every OS?  It is not necessarily Cloverleaf, it could be the TCP/IP stack or other things.  No such thing as a perfect OS or a perfect app.

If it happens frequently, contact Support.

[William Grow]

One thing that I didn’t mention was that this xlate is the largest xlate that I have ever seen in my life in the sense that both the xlate is extremely long and the xlt tclprocs called are also long with a lot of logic. I am adding to that additional information that wildcard routes are being used to route ADT through this one xlate for about 8 facilities.   The decision to handle the routes this way was an administrative decision. Would that have anything to do with this because there isn’t anything using port 127.

[Charlie Bursell]

Don’t know without evaluating it which I don’t have tiem for right now.

If it is that complex, I would redo it.  It will cost you a lot in Maintenance hours

[Author]

Replies