gfix -shut single -force 0 ..... not working as documented with 2.5.3 & 2.5.4 [CORE4742] #5047
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
|
Commented by: Sean Leyne (seanleyne) This really should have been posted to the support mailing list, first. 1- Are you using SYSBDA user for the shutdown? 2- Are the other connections using non-SYSDBA connections? |
|
Commented by: John Price (jprice) Using SYSDBA for the shutdown, all other connections were non-SYSDBA users. versions prior to 2.5.3 work as expected, only from 2.5.3 on is this an issue. |
|
Commented by: John Price (jprice) Just discovered an even more concerning issue, when restoring a database using 2.5.3 or 2.5.4 Firebird will allow non SYSDBA users to connect |
|
Commented by: @dyemanov What architecture you used - SS or CS? |
Modified by: John Price (jprice)environment: Windows 7 and Windows 8.1, Firebird 2.5.4.26856_0_x64.exe & 2.5.3.26780_0_x64.exe => Windows 7 and Windows 8.1, Firebird 2.5.4.26856_0_x64.exe & 2.5.3.26780_0_x64.exe (super server) |
|
Commented by: John Price (jprice) Super Server (default install options, only control applet not selected) |
Modified by: @hvladassignee: Dmitry Yemanov [ dimitr ] => Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.7 [ 10770 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred Test Details: Found trouble on *SuperServer* (both on 2.5 and 3.0) - see CORE5364: Wait for comments in CORE5364. |
Submitted by: John Price (jprice)
Votes: 2
When using the command 'gfix -shut single -force 0 -user user -password password my-database'
gfix hangs if their is more than one or two connections open to the database and only returns if
and when you close the connections or their is some activity on them, the "force" option does not work,
using -force with a non zero value is the same.
Seems to work ok in versions 2.1, 2.5.0 and 2.5.2 as per the documentation, any connected user are disconnected.
Commits: dce03a2
====== Test Details ======
Found trouble on *SuperServer* (both on 2.5 and 3.0) - see CORE5364:
one may to issue 'gfix -online normal' for database with shutdown mode = 'single' and existing DBA-attachment,
and then one may to connect to this database as another DBA and begin to work w/o alerting 1st SYSDBA about it!
Wait for comments in CORE5364.
The text was updated successfully, but these errors were encountered: