Subject | RE: [firebird-support] Read error in the log file |
---|---|
Author | Craig |
Post date | 2004-10-21T13:04:23Z |
Thanks for the reply Helen. Interestingly, the database and the
application reside on the same machine. The network print option is one
I have not considered, so I will look into that.
Regards,
Craig de Kock
GM: Product Development
Barloworld Optimus
Tel +2711 286 1580 Fax +2711 445 1810 Cell 082 772 7840
www.barloworldoptimus.com
-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: 21 October 2004 02:40 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Read error in the log file
At 02:12 PM 21/10/2004 +0200, you wrote:
means someone crashed out of an application program without
disconnecting;
sometimes it indicates a fault in cabling or a network card or
router; occasionally it might indicate that the server crashed; and
sometimes it might happen from the server receiving a dirty packet and
getting no response on a request to resend - this might be a fairly
frequent occurrence in a hybrid network where a workstation is doing
double
duty as a db client and a Windows print server, for example.
Unless you see lots of them, or you have persistent network problems,
it's
not something to worry about.
./heLen
Yahoo! Groups Links
application reside on the same machine. The network print option is one
I have not considered, so I will look into that.
Regards,
Craig de Kock
GM: Product Development
Barloworld Optimus
Tel +2711 286 1580 Fax +2711 445 1810 Cell 082 772 7840
www.barloworldoptimus.com
-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: 21 October 2004 02:40 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Read error in the log file
At 02:12 PM 21/10/2004 +0200, you wrote:
>What would the following line in the firebird log file indicate?It's the "connection reset by peer" message from the network. It often
>
>INET/inet_error: read errno = 10054
>
>We are running FB 1.5 classic server on a Win2k server.
>
>Any help or comments would be appreciated.
means someone crashed out of an application program without
disconnecting;
sometimes it indicates a fault in cabling or a network card or
router; occasionally it might indicate that the server crashed; and
sometimes it might happen from the server receiving a dirty packet and
getting no response on a request to resend - this might be a fairly
frequent occurrence in a hybrid network where a workstation is doing
double
duty as a db client and a Windows print server, for example.
Unless you see lots of them, or you have persistent network problems,
it's
not something to worry about.
./heLen
Yahoo! Groups Links