Subject | Re: [ib-support] Re: ibserver terminated abnormally (-1) |
---|---|
Author | Paul Reeves |
Post date | 2001-09-24T10:57:50Z |
roy@... wrote:
necessarily a direct connection between the 'select in packet_receive' error
and the termination of the server. It is an indicator that a tcp packet failed
to come across the wire correctly. As such the error raised should either then
be handled - either the packet is resent correctly or failing that, an error
sent to the client and the current transaction rolled back. At least that is
the theory.
I would agree with Claudio's suggestions - Check the database for corruption
and check the network.
Beyond that, I can't be of more help without spending time on more research.
Paul
--
Paul Reeves
http://www.ibphoenix.com
taking InterBase further
> snic2db.speednames.com (Server) Thu Sep 20 11:53:12 2001Hmmm. This doesn't throw any more light on the problem. There isn't
> INET/inet_error: select in packet_receive errno = 9
>
> snic2db.speednames.com (Server) Thu Sep 20 13:40:47 2001
> INET/inet_error: select in packet_receive errno = 9
>
> snic2db.speednames.com (Client) Thu Sep 20 13:48:43 2001
> /opt/interbase/bin/ibguard: bin/ibserver terminated
> abnormally (-1)
>
necessarily a direct connection between the 'select in packet_receive' error
and the termination of the server. It is an indicator that a tcp packet failed
to come across the wire correctly. As such the error raised should either then
be handled - either the packet is resent correctly or failing that, an error
sent to the client and the current transaction rolled back. At least that is
the theory.
I would agree with Claudio's suggestions - Check the database for corruption
and check the network.
Beyond that, I can't be of more help without spending time on more research.
Paul
--
Paul Reeves
http://www.ibphoenix.com
taking InterBase further