| Subject | Re: Firebird 2.1.3 Freezing |
|---|---|
| Author | emb_blaster |
| Post date | 2010-02-12T12:18:48Z |
--- In firebird-support@yahoogroups.com, "bojanpasic" <bojanpasic@...> wrote:
These errors are caused by network problems.
Error 10054 is a winsock error for connection reset.
Since the server is up and running at the time of the problem,
it's an indication that should not be an FB issue but a network
issue. Check the following:
* How many times this errors keep repeating? they are like a pattern? or random ones?
* At the time of the problem, what's the traffic load? Check for traffic loads that can flood the network. Is there anything scheduled to flood the network at certain time?
* Check for network hardware problems such as bad switch, router,
hub, adapter, etc.
* also may be that you have more than one protocol bound to the same network card. Like TCP/IP, IPX/SPX, and RIP for IPX bound to the same ethernet card.
I saw this info sometime ago in borland network. Althougth, it should not cause 100% CPU load, unless your application is retrying (almost infinitely) to reach the host... but anyway, if theres many of this errors in log, you must take a look in it.
>"INET/inet_error: read errno = 10054"
> Hello!
>
>
> We recently migrated from FB 1.5 to 2.1.3 and now we are encountering some problems. Sometimes FB server starts using 100% of CPU and all applications stop responding. It's even impossible to stop the FB Server via control panel applet - we have to do it through Services. There are no errors in firebird.log when this happens. But there is one error that keeps repeating and was not present in 1.5: "INET/inet_error: read errno = 10054".
These errors are caused by network problems.
Error 10054 is a winsock error for connection reset.
Since the server is up and running at the time of the problem,
it's an indication that should not be an FB issue but a network
issue. Check the following:
* How many times this errors keep repeating? they are like a pattern? or random ones?
* At the time of the problem, what's the traffic load? Check for traffic loads that can flood the network. Is there anything scheduled to flood the network at certain time?
* Check for network hardware problems such as bad switch, router,
hub, adapter, etc.
* also may be that you have more than one protocol bound to the same network card. Like TCP/IP, IPX/SPX, and RIP for IPX bound to the same ethernet card.
I saw this info sometime ago in borland network. Althougth, it should not cause 100% CPU load, unless your application is retrying (almost infinitely) to reach the host... but anyway, if theres many of this errors in log, you must take a look in it.