Subject | FB 2.0 RC1 crash |
---|---|
Author | manoel_sa |
Post date | 2006-06-21T18:42:18Z |
context:
- Firebird SS 2.0 RC1
- x86 (P4 HT)
- Suse 9.3
the server crashed because the log filled the filesystem
INET/inet_error: send errno = 32 (repeated continuously without any
time skew)
1. is there any way to limit the logsize ?
there have been other errors:
INET/inet_error: read errno = 104
INET/inet_error: read errno = 110
INET/inet_error: read errno = 9 (frequent)
INET/inet_error: select in packet_receive errno = 9
INET/inet_error: send errno = 104
the clients are Delphi apps using fbclient.dll (2.0.0.12484)
2. does FB handle "broken" clients gracefully ?
3. (this is a vague/impossible question but ...) any idea about the
order of concurrency for a 3GHz P4/1G ram/FB2 SS ? (ie num of
simultaneous clients/requests)
- Firebird SS 2.0 RC1
- x86 (P4 HT)
- Suse 9.3
the server crashed because the log filled the filesystem
INET/inet_error: send errno = 32 (repeated continuously without any
time skew)
1. is there any way to limit the logsize ?
there have been other errors:
INET/inet_error: read errno = 104
INET/inet_error: read errno = 110
INET/inet_error: read errno = 9 (frequent)
INET/inet_error: select in packet_receive errno = 9
INET/inet_error: send errno = 104
the clients are Delphi apps using fbclient.dll (2.0.0.12484)
2. does FB handle "broken" clients gracefully ?
3. (this is a vague/impossible question but ...) any idea about the
order of concurrency for a 3GHz P4/1G ram/FB2 SS ? (ie num of
simultaneous clients/requests)