Server connections crashing
Peter
We have a client whose connections go down on a regular basis.
There seem to be good days where it happen less frequently and bad days.
The hardware guy and system manager says that the network was checked and is OK.
Of course he blames Firebird or our applications.
This is the only site where we have such a problem although this is our largest one.
There are 45 computers on the network but only 35 access the Firebird database.
There are 6 Firebird databases, one heavily accessed, two fairly light, the others infrequently.
With Firebird 2.5.9 Super Classic as well as SuperServer all connections crash at the same time
We have tried another computer as server, same problem
They have now installed a brand new server and the problem persists.
Server: Dell PowerEdge R650xs
CPU: Intel Xeon Silver 4314 CPU (10 processors)
Memory: 32 Gb
OS: Windows Server 2022 Standard
I have now installed Firebird in Classic mode. It still crashes but at least only one connection goes down if that happens.
All installations are the 64-bit version,
Any ideas from anyone would be appreciated
Peter Reber
Here is an extract of the Firebird. Log showing the error messages. The server name is: CapApps, and what puzzles me is the very first error message here. Why does Firebird which run on CapApps report that it is unable to complete the network request to itself?
CAPAPPS Fri Sep 09 13:10:18 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
CAPAPPS Fri Sep 09 13:28:42 2022
INET/inet_error: read errno = 10054, client address = 192.168.0.96/64246, user = JESSICA.-1.-1
CAPAPPS Fri Sep 09 13:28:42 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
CAPAPPS Fri Sep 09 13:35:20 2022
INET/inet_error: read errno = 10054, client address = 192.168.0.66/58288, user = DISPATCH.-1.-1
CAPAPPS Fri Sep 09 13:35:20 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
CAPAPPS Fri Sep 09 13:44:58 2022
INET/inet_error: read errno = 10054, client address = 192.168.0.85/61664, user = ARTDEPT.-1.-1
CAPAPPS Fri Sep 09 13:44:58 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
CAPAPPS Fri Sep 09 14:20:46 2022
INET/inet_error: read errno = 10054, client address = 192.168.0.103/51771, user = RECEPTION.-1.-1
CAPAPPS Fri Sep 09 14:20:46 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
CAPAPPS Fri Sep 09 14:21:15 2022
INET/inet_error: read errno = 10054, client address = 192.168.0.103/51778, user = RECEPTION.-1.-1
CAPAPPS Fri Sep 09 14:21:15 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
CAPAPPS Fri Sep 09 15:15:30 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
CAPAPPS Fri Sep 09 15:41:47 2022
Access violation.
The code attempted to access a virtual
address without privilege to do so.
This exception will cause the Firebird server
to terminate abnormally.
CAPAPPS Fri Sep 09 15:41:47 2022
Shutting down the server with 1 active connection(s) to 1 database(s), 0 active service(s)
CAPAPPS Fri Sep 09 15:41:52 2022
Firebird shutdown is still in progress after the specified timeout
CAPAPPS Fri Sep 09 15:41:52 2022
INET/inet_error: select in packet_receive errno = 10093, client address = 192.168.0.106/52970, user = LABADMIN.-1.-1
CAPAPPS Fri Sep 09 16:04:30 2022
INET/inet_error: read errno = 10054, client address = 192.168.0.84/54066, user = CREDITORS.-1.-1
CAPAPPS Fri Sep 09 16:04:30 2022
Unable to complete network request to host "CapApps".
Error reading data from the connection.
Mark Rotteveel
[..]
This one stood out to me:
> CAPAPPSFri Sep 09 15:41:47 2022
> Access violation.
>
> The code attempted to access a virtual
>
> address without privilege to do so.
>
> This exception will cause the Firebird server
>
> to terminate abnormally.
buggy UDFs are a likely culprit of causing Firebird server crashes.
Mark
--
Mark Rotteveel
Peter
Vlad Khorsun
Peter
Mark Rotteveel
> I will upgrade to FB 3 first as a potential problem in FB 2 will not be
> fixed anyway, that version being discontinued.
>
> One thing I struggle with is to find the relevant section for the FB3 to
> FB 2 data type mapping in the configuration file.
> I modified the COUNT() statements, BIGINT cast to INTEGER but may have
> missed one or two.
The DataTypeCompatibility setting was introduced in Firebird 4.0.
However, that wouldn't help against changes like this, it only maps
types introduced in a newer version to types available in an older
version. It doesn't account for changes like return types changing to
another type that was already available in that older version.
Mark
--
Mark Rotteveel
