GFIX returns an error after correctly shutting down a database [CORE3548] #3904
Assignees
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
|
Commented by: @AlexPeshkoff I've tried both 2.1.5 and 2.5.1. Can't reproduce - gfix gives no errors. There is a single connection to database. What else to be tried? |
|
Commented by: @AlexPeshkoff BTW - what OS do you use? |
|
Commented by: Dmitry Kurbsky (kurbsky) Initially I found this on Windows 2000. Now I checked Windows XP SP2 with the same result. |
Modified by: Dmitry Kurbsky (kurbsky)Version: 2.5.2 [ 10450 ] environment: Windows 2000, Windows XP SP2 |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 RC 1 [ 10584 ] Fix Version: 2.5.5 [ 10670 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Dmitry Kurbsky (kurbsky)
When using TCP connection, gfix -shut full works fine.
When using local connection, gfix -shut full correctly transfer a database into full shutdown mode, but returns an error: "connection lost to database".
Only full shutdown is affected, not single or multi. On 2.1 only classic server is affected, but on 2.5 classic, superserver and superpclassic are.
Commits: 06cb59d 9976420 FirebirdSQL/fbt-repository@a58e906 FirebirdSQL/fbt-repository@f038bf9
The text was updated successfully, but these errors were encountered: