Help!
Our server restarts every 4-6hrs, before a termination -1 occures, there are
some errors - here's the log:

N9001050 (Client) Tue Aug 29 09:31:22 2000
/opt/interbase/bin/ibguard: bin/ibserver terminated abnormally (-1)

N9001050 (Client) Tue Aug 29 09:31:22 2000
/opt/interbase/bin/ibguard: guardian starting bin/ibserver

N9001050 (Server) Tue Aug 29 10:32:09 2000
INET/inet_error: read errno = 104

N9001050 (Server) Tue Aug 29 10:32:09 2000
INET/inet_error: read errno = 104

N9001050 (Server) Tue Aug 29 10:32:24 2000
INET/inet_error: read errno = 104

N9001050 (Server) Tue Aug 29 11:00:35 2000
gds__alloc: memory pool corrupted

N9001050 (Server) Tue Aug 29 11:01:45 2000
gds__free: attempt to release bad block


N9001050 (Server) Tue Aug 29 11:01:45 2000
gds__alloc: memory pool corrupted


N9001050 (Server) Tue Aug 29 11:03:08 2000
INET/inet_error: read errno = 104

N9001050 (Server) Tue Aug 29 11:03:10 2000
INET/inet_error: read errno = 104

N9001050 (Server) Tue Aug 29 11:17:17 2000
INET/inet_error: read errno = 104

N9001050 (Server) Tue Aug 29 11:17:26 2000
INET/inet_error: read errno = 104

N9001050 (Server) Tue Aug 29 11:37:36 2000
gds__free: attempt to release bad block

N9001050 (Server) Tue Aug 29 11:37:36 2000
gds__alloc: memory pool corrupted

N9001050 (Server) Tue Aug 29 12:57:00 2000
gds__alloc: memory pool corrupted

N9001050 (Server) Tue Aug 29 13:30:58 2000
gds__free: attempt to release bad block

N9001050 (Server) Tue Aug 29 13:49:56 2000
INET/inet_error: read errno = 104

Obviously ther are some bad connection due to WINSOCKET (WIn95/98), marked
as ERR 104. This occured in IB4 too and we fixed the problem by a scheduled
killing dead processes... But in IB6SS achitecture - how to solve this new
problem of restarts? IB4 is too slow no, but was stable... the stations
don't hang up (by killing dead processes).

Any tip would be nice...
Hans




_______________________________________________
Ib-architect mailing list
Ib-architect@...
http://mers.com/mailman/listinfo/ib-architect