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

fbsvcmgr can not decode information buffer returned by gfix list limbo service [CORE6309] #6550

Closed
firebird-automations opened this issue May 18, 2020 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pcisar

In case of any error buffer that must contain special format of isc_info_svc_limbo_trans record contains instead text describing an error, status vector is in success state.

Commits: 706dc73 b06bd7c

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

reporter: Alexander Peshkov [ alexpeshkoff ] => Pavel Cisar [ pcisar ]

Component: GFIX [ 10004 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 3.0.6 [ 10889 ]

Fix Version: 4.0 RC 1 [ 10930 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Deferred

Test Details: Have issues about 3.x and 4.x (results differ from 2.5.x; FDB raises exception when number of limbo Tx is 255).
Sent letter to Alex, Pavel and Dmitry, 27.05.2020 10:58.
Waiting for reply.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: Deferred => Done successfully

Test Details: Have issues about 3.x and 4.x (results differ from 2.5.x; FDB raises exception when number of limbo Tx is 255).
Sent letter to Alex, Pavel and Dmitry, 27.05.2020 10:58.
Waiting for reply.

=>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

@pavel-zotov
Copy link

@@@ QA issue @@@

Currently only gfix -list properly works.
Command fbsvcmgr action_repair rpr_list_limbo_trans does not work and raises:

Could not reattach to database for transaction <N>.
-Original path: localhost/<port>:<path/to/database.fdb>

This can be illustrated (on Windows) by attached .zip.
Create directory "C:\temp\pytest-of-PashaZ\pytest-163\test_10" and unpack there files from this .zip.
Then use FB in Classic mode with port 3639 and try commands that are in .log files.
Only gfix -list localhost/3639:C:\temp\pytest-of-PashaZ\pytest-163\test_10\CORE_6309_A.FDB will work OK and show operations with 146 limbo transactions:

  Multidatabase transaction:
    Host Site: IMAGE-PC1
    Transaction 6
has been prepared.
        Remote Site: localhost/3639
        Database Path: localhost/3639:C:\temp\pytest-of-PashaZ\pytest-163\test_10\core_6309_a.fdb
    Host Site: IMAGE-PC1
    Transaction 6
has been rolled back.
...

Attempt to get same list using fbsvcmgr fails, e.g.:
fbsvcmgr localhost/3639:service_mgr action_repair rpr_list_limbo_trans dbname C:\temp\pytest-of-PashaZ\pytest-163\test_10\CORE_6309_A.FDB - fails with:

Could not reattach to database for transaction 6.
-Original path: localhost/3639:C:\temp\pytest-of-PashaZ\pytest-163\test_10\core_6309_a.fdb

core-6309_-_databases-in-limbo-and-logs.zip

NOTE.
Using ServerMode = Super leads to another problem: DB can remain opened after issuing some of fbsvcmgr commands.

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