Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lost Connection with Firebird Server [CORE968] #1371

Closed
firebird-automations opened this issue Oct 23, 2006 · 17 comments
Closed

Lost Connection with Firebird Server [CORE968] #1371

firebird-automations opened this issue Oct 23, 2006 · 17 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: S?bastien DEJEAN (sdejean)

It happens during both the GBAK resore process directly on the server (so no network connection, just a localhost network connection) and a when executing long query or long procedure (on my client)
For example on a 400000 records table, i launch en update on all records, but i always get a :

Unable to complete network request to host "IP address".
Error reading data from the connection.

I get a similar error while inserting many records:

Unable to complete network request to host "IP address".
Error writing data to the connection.

Commits: 6d77a71 dfef55e

====== Test Details ======

Debug builds are not used on test running process.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

What's in firebird.log?

@firebird-automations
Copy link
Collaborator Author

Commented by: S?bastien DEJEAN (sdejean)

on flamerobin i've got :

Starting transaction...
Preparing query: EXECUTE PROCEDURE UPDATE_CA_KEYS
Prepare time: 00:00:00.
Plan not available.

Executing...
*** IBPP::SQLException ***
Context: Statement::Execute( EXECUTE PROCEDURE UPDATE_CA_KEYS )
Message: isc_dsql_execute2 failed

SQL Message : -902
Unsuccessful execution caused by a system error that precludes
successful execution of subsequent statements

Engine Code : 335544721
Engine Message :
Unable to complete network request to host "IP address".
Error reading data from the connection.

Execute time: 00:05:32.

if firebird.log :

arthur (Server) Tue Oct 24 18:59:52 2006
GDS Assertion failure: ../src/jrd/os/posix/isc_ipc.cpp 207
arthur (Client) Tue Oct 24 18:59:52 2006
/opt/firebird2/bin/fbguard: bin/fbserver terminated abnormally (-1)
arthur (Client) Tue Oct 24 18:59:52 2006
/opt/firebird2/bin/fbguard: guardian starting bin/fbserver
arthur (Client) Tue Oct 24 18:59:52 2006
/opt/firebird2/bin/fbguard: guardian could not open /var/run/firebird/S14firebird.pid for writing, error 2

@firebird-automations
Copy link
Collaborator Author

Commented by: S?bastien DEJEAN (sdejean)

I test the 2.0 final release and i have the same problem.
does anyone have this same issue ?
thanks

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

In log I see:
arthur (Server) Tue Oct 24 18:59:52 2006
GDS Assertion failure: ../src/jrd/os/posix/isc_ipc.cpp 207

It means you use DEBUG version of server, not release. DEBUG builds are not supposed to be used in production. They are used by developers to fix some specific issues with firebird. They are MUCH slower compared with production builds (10 times will be a good estimation). In many cases when release tries to recover in any way, debug asserts. Be sure this is not what you need working with real database.

On the other hand, assertion that I see in the log is certainly not good thing. At the first look at source code I have not found a place where it might happen. On the other hand, technic used to make calls to ISC_inhibit() / ISC_enable() match is 'slightly' old and shoudl be replaced with newer one.
And it will be very interesting to have a look at backtrace of core, created when assertion in isc_ipc took place.

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

Added classes automatically making calls to inhibit/enable match.

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.1 [ 10041 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

When this issue was classified as critical, shouldn't we backport it into 2.0.x ? It was reported on 2.0 RC5, so it's strange it slipped the 2.0.1 maintenance. You should either downgrade it from critical or schedule the fix also for 2.0.2.

@firebird-automations
Copy link
Collaborator Author

Commented by: @AlexPeshkoff

backported to 2_0_Release

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Re-opened just to update the ticket information.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Resolved [ 5 ] => Reopened [ 4 ]

resolution: Fixed [ 1 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Reopened [ 4 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.0.2 [ 10130 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Fix Version: 2.1 Alpha 1 [ 10150 ]

Fix Version: 2.1.0 [ 10041 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 11273 ] => Firebird [ 14301 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test => Cannot be tested

Test Details: Debug builds are not used on test running process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment