Firebird en 64 bits

[gescoto99]

El log de firebird contiene esto en repetidas ocasiones

INET/inet_error: select in packet_receive errno = 10038

[Casimiro Noteví]

Empezado por gescoto99

El log de firebird contiene esto en repetidas ocasiones

INET/inet_error: select in packet_receive errno = 10038

INET/inet_error: select in packet_receive errno = 10038


Please note that 10038 is not a Firebird error code, but rather one of network (TCP/IP) layer.

There are some known cases when this happens:

1. Windows RAS bug that disabled the
entire range of IP addresses. Fix available from Microsoft:

http://support.microsoft.com/default...b;en-us;884020

2. Some AdWare tools and firewall software install network monitors that can keep working even if you remove them later. There is a small utility that cleans this up:

http://www.snapfiles.com/get/winsockxpfix.html

[Casimiro Noteví]

También:

INET/inet_error: read errno = 10054 or 10038 or 10093
Multiple entries in interbase.log or firebird.log with errors 10054, 10038, 10093, etc. These errors are caused by network problems - check your hubs, network adapters, etc. It is not an InterBase or Firebird error in itself, but it may cause problems.
Recovery process:
In this case it will be technical support, not a recovery process. If you have this problem and cannot solve it, you can request our support services.
Time: 4 hours and more.
Probable % of saved data: 100%.

[Casimiro Noteví]

Otro, indica algo sobre firewall:

It seems, that the client crashes, when the function trys
to execute the stored procedure the second time,
because the first time there was an exception.

We use:

Firebird 1.5.2
Windows 2003 Server, Windows XP Professional SP1 +
SP2, ecc. (on every system the same error)
Delphi 5 + IPX 5.03
Description
SFID: 1249375# Submitted By: mkrauti Hello, we have a big problem: one of our applications crashes sometimes (up to 5 times a day) without exception. We searched the bug approximately 1 year, but we never found it. Now i've seen, that every time when it crashes, there is the following situation: 1. in Firebird.log is one of the following messages: PPSSERVER (Client) Mon Jul 18 10:39:04 2005 INET/inet_error: read errno = 10038 PPSSERVER (Client) Mon Jul 18 11:07:09 2005 INET/inet_error: select in packet_receive errno = 10038 PPSSERVER (Client) Tue Jul 26 14:27:29 2005 INET/inet_error: read errno = 10038 PPSSERVER (Client) Mon Aug 01 07:57:55 2005 INET/inet_error: read errno = 10038 2. our application logged this: 01.08.2005 07:57:55 IBErrorCode: 335544726 SqlCode: - 902 ErrorMessage: "Error reading data from the connection" in SecureExecSTP(stpPacklinieCounter). the function SecureExecSTP trys 15 times with a delay of 100ms to execute the StoredProcedure PROC_UPD_WORDLINIE_PA_COUNT with the following code: SET TERM ^ ; CREATE PROCEDURE PROC_UPD_WORDLINIE_PA_COUNT ( WOCOD CHAR(10), WOPPOS CHAR(4), WOPJAHR SMALLINT, WOLPOS SMALLINT, BLID INTEGER, BLSUBID SMALLINT, PAFIRST TIMESTAMP, PALAST TIMESTAMP, PACOUNT INTEGER, PALASTNUM INTEGER) AS begin update wordlinie set wol_pa_dtfirst = :PAFIRST, wol_pa_dtlast = :PALAST, wol_pa_count = :PACOUNT, wol_pa_last_num = :PALASTNUM where wo_cod = :WOCOD and wop_pos = :WOPPOS and wop_jahr = :WOPJAHR and wol_pos = :WOLPOS and bl_id = :BLID and bl_sub_id = :BLSUBID; end ^ SET TERM ; ^ GRANT SELECT,UPDATE ON WORDLINIE TO PROCEDURE PROC_UPD_WORDLINIE_PA_COUNT; GRANT EXECUTE ON PROCEDURE PROC_UPD_WORDLINIE_PA_COUNT TO SYSDBA; It seems, that the client crashes, when the function trys to execute the stored procedure the second time, because the first time there was an exception. We use: Firebird 1.5.2 Windows 2003 Server, Windows XP Professional SP1 + SP2, ecc. (on every system the same error) Delphi 5 + IPX 5.03

Show »


All Comments Work Log Change History Version Control Sort Order: [ Permlink | « Hide ]
Alice F. Bird - [14/Jun/06 09:37 AM ]
Date: 2005-10-11 13:48
Sender: mikhail_moscow
Logged In: YES
user_id=1359923

Problem resolved. After deinstalling MS firewall client firebird
was accept connection by tcp in classic mode.


[ Show » ]
Alice F. Bird - [14/Jun/06 09:37 AM ] Date: 2005-10-11 13:48 Sender: mikhail_moscow Logged In: YES user_id=1359923 Problem resolved. After deinstalling MS firewall client firebird was accept connection by tcp in classic mode.



[ Permlink | « Hide ]
Alice F. Bird - [14/Jun/06 09:37 AM ]
Date: 2005-10-11 11:47
Sender: mikhail_moscow
Logged In: YES
user_id=1359923

We have same problem after terminate long time executing
processes of classic server Firebird-1.5.2.4731 when server
process was stoped. From client and from local i can connect
using NetBeui, but TCP connection can't connect with
message 'Incorrect parameter of environment'
(russian 'Neverniy parameter sredy'). In firebird log message
FSERVER Tue Oct 11 12:11:30 2005
INET/inet_error: read errno = 10038
Reinstall of firebird is not change situation. In superserver
mode firebird work via TCP/IP. We have this problem at 2
servers with same symptoms.


[ Show » ]
Alice F. Bird - [14/Jun/06 09:37 AM ] Date: 2005-10-11 11:47 Sender: mikhail_moscow Logged In: YES user_id=1359923 We have same problem after terminate long time executing processes of classic server Firebird-1.5.2.4731 when server process was stoped. From client and from local i can connect using NetBeui, but TCP connection can't connect with message 'Incorrect parameter of environment' (russian 'Neverniy parameter sredy'). In firebird log message FSERVER Tue Oct 11 12:11:30 2005 INET/inet_error: read errno = 10038 Reinstall of firebird is not change situation. In superserver mode firebird work via TCP/IP. We have this problem at 2 servers with same symptoms.



[ Permlink | « Hide ]
Alice F. Bird - [14/Jun/06 09:37 AM ]
Date: 2005-08-31 20:05
Sender: dimitr
Logged In: YES
user_id=61270

I'm afraid we cannot help without a reproducable test case,
sorry.


[ Show » ]
Alice F. Bird - [14/Jun/06 09:37 AM ] Date: 2005-08-31 20:05 Sender: dimitr Logged In: YES user_id=61270 I'm afraid we cannot help without a reproducable test case, sorry.

[Casimiro Noteví]

También te aconsejo que pruebes a cambiar de la versión classicserver a superserver o viceversa, según tengas instalada.
Por probar.

[gescoto99]

Casimiro

Gracias por los tips, tenia classic la cambie a super server y ya funciona, ya puedo ver las bases desde el ibexpert.
Sin embargo requiero tener la version de classic ya que he visto que cuando el servidor tiene mas de 1 procesador es mejor el classic por que el server realentiza los procesos (aun cambiando el affinitymask)

Teniendo esta pista de que si funciona con super server, tendras alguna idea de por que no funciona con classic?

[Casimiro Noteví]

Empezado por gescoto99

Casimiro

Gracias por los tips, tenia classic la cambie a super server y ya funciona, ya puedo ver las bases desde el ibexpert.
Sin embargo requiero tener la version de classic ya que he visto que cuando el servidor tiene mas de 1 procesador es mejor el classic por que el server realentiza los procesos (aun cambiando el affinitymask)

Teniendo esta pista de que si funciona con super server, tendras alguna idea de por que no funciona con classic?

Normalmente es porque no está funcionando, simplemente, asegúrate de ello, lanza por ejemplo el isql, que lo encontrarás en el directorio de firebird/bin y haz alguna prueba, si funciona así, en local, es que estará funcionando bien.

De todas formas, si estás trabajando con windows no le sacarás ningún provecho a la versión classic, te aconsejo la versión superserver y que "ancles" firebird a algún procesador, mira el parámetro cpu-afinity (o algo así)

Si fuese Linux sí que te iría perfecto la classic con más de un procesador, le sacaría todo el rendimiento a los procesadores que tengas.

También creo recordar, que aunque sea en local, debes poner la ruta tcp completa, al mismo (localhost) 192.198.0.1:unidad\directorio\basedatos.fdb