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
REVOKE ALL ON ALL produces "connection lost to database" but... connection is alive (3.0 SS, config contains line "Providers = Loopback,Remote,Engine12") [CORE4953] #5244
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff Loopback provider efficiently disables use of providers, following him. It may be removed from configuration line, but if it's used it should better be last. I'm much surprised that you have attached to database successfully - on linux I can not succeed even with this. I suggest to close an issue due to configuration error needed to reproduce it. |
Commented by: @pavel-zotov Yes, on WI-V3.0.0.32070 there is no more such strange message (when line "Providers = Loopback,Remote,Engine12" present in firebird.conf). But on Classic and SuperClassic following output is produced when attempting just to establish connect (after pause ~5-7 seconds): isql /3330:C:\MIX\firebird\QA\fbt-repo\tmp\e30.fdb ==== And on SuperServer connect from SYSDBA is established OK, but then: C:\MIX\firebird\fb30>isql /3333:C:\MIX\firebird\QA\fbt-repo\tmp\e30.fdb Can these confusing messages be replaced with more clear ? |
Modified by: @AlexPeshkoff |
Commented by: @AlexPeshkoff Due to changes done to fix CORE5047 all problems, mentioned in the current issue, are gone. |
Commented by: @AlexPeshkoff Fixed simultaneously with CORE5047. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Cannot Reproduce [ 5 ] Fix Version: 3.0 RC2 [ 10048 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested Test Details: Line: Providers = Remote,Engine12,Loopback - must be added in firebird.conf in order to test this ticket issues, + restart FB. |
Modified by: @dyemanovFix Version: 3.0 RC2 [ 10048 ] => |
Submitted by: @pavel-zotov
Is related to CORE5047
Create new database and make following config:
AuthClient = Legacy_Auth
AuthServer = Legacy_Auth, Srp, Win_Sspi
Providers = Loopback,Remote,Engine12 ------------------------------------------------- ::: NB :::
RemoteServicePort = 3333
ServerMode = Super
UserManager = Legacy_UserManager
WireCrypt = Disabled
Restart FB and then do in ISQL:
C:\FBTESTING\qa\fbt-repo\tmp>C:\1INSTALL\FIREBIRD\fb30sS\isql.exe /3333:e30
Database: /3333:e30, User: SYSDBA
SQL> create user totally_new1 password 'qwertyui';
SQL> revoke all on all from totally_new1;
Statement failed, SQLSTATE = 08006
unsuccessful metadata update
-REVOKE failed
-connection lost to database
SQL> select mon$attachment_id, mon$user from mon$attachments;
MON$ATTACHMENT_ID 6
MON$USER SYSDBA
MON$ATTACHMENT_ID 4
MON$USER Cache Writer
MON$ATTACHMENT_ID 5
MON$USER Garbage Collector
PS.
Trouble in line "Providers = Loopback,Remote,Engine12" - when it is commented all become fine.
Message about 'lost connection' looks invalid because in fact connection staying alive.
WI-V3.0.0.32060
====== Test Details ======
Line: Providers = Remote,Engine12,Loopback - must be added in firebird.conf in order to test this ticket issues, + restart FB.
Unfortunately, these actions can not be done using fbt_run framework.
The text was updated successfully, but these errors were encountered: