Subject | INET/inet_error is ofien raised with FB103SS |
---|---|
Author | Tsutomu Hayashi |
Post date | 2004-05-16T00:13:45Z |
Hi all
I use FirebirdSS 103 on Redhat Linux9. Server HW is Dell PE1600 Xeon*2 +
1GB mem.Client is Apache2 + PHP4.2.2 runnning on another server using
PHP's IB function.
I recieved many INET/inet_error in interbase.log like bellow.
INET/inet_error: read errno = 104
INET/inet_error: read errno = 110
INET/inet_error: select in packet_receive errno = 9
INET/inet_error: read errno = 9
These errors are raised only with FirebirdSS103 but FirebirdCS103 is
not. These errors are almost about os network problem.
#define EBADF 9 /* Bad file number */
#define ECONNRESET 104 /* Connection reset by peer */
#define ETIMEDOUT 110 /* Connection timed out */
I search on internet about these errors. I have seen some article about
these errors but these pointed out these errors caused by network HW
problem.
But but, FirebirdCS is almost OK, FirebirdSS is almost wrong. Is this
FirebirdSS's problem or not?
If these are caused by FirebirdSS's problem, can I solve these ploblem
not to change to FirebirdCS. Cause FirebirdCS dosen't have Service API,
remote maintenance is difficult.
best,
--
Tsutomu Hayashi in Japan
Mail : hayashi@...
Web : http://firebird.gr.jp/ (Japanese Only)
I use FirebirdSS 103 on Redhat Linux9. Server HW is Dell PE1600 Xeon*2 +
1GB mem.Client is Apache2 + PHP4.2.2 runnning on another server using
PHP's IB function.
I recieved many INET/inet_error in interbase.log like bellow.
INET/inet_error: read errno = 104
INET/inet_error: read errno = 110
INET/inet_error: select in packet_receive errno = 9
INET/inet_error: read errno = 9
These errors are raised only with FirebirdSS103 but FirebirdCS103 is
not. These errors are almost about os network problem.
#define EBADF 9 /* Bad file number */
#define ECONNRESET 104 /* Connection reset by peer */
#define ETIMEDOUT 110 /* Connection timed out */
I search on internet about these errors. I have seen some article about
these errors but these pointed out these errors caused by network HW
problem.
But but, FirebirdCS is almost OK, FirebirdSS is almost wrong. Is this
FirebirdSS's problem or not?
If these are caused by FirebirdSS's problem, can I solve these ploblem
not to change to FirebirdCS. Cause FirebirdCS dosen't have Service API,
remote maintenance is difficult.
best,
--
Tsutomu Hayashi in Japan
Mail : hayashi@...
Web : http://firebird.gr.jp/ (Japanese Only)