Bugcheck could happen when read-only database with non-zero linger is set to read-write mode [CORE5949] #6205
Comments
Modified by: Basil A. Sidorov (basid)security: Developers [ 10012 ] |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
|
Commented by: @hvlad The problem happens when read-only database with non-zero linger is set to read-write mode and 1. Prepare some database (S:\TEMP\R.FDB in my case) and set linger to, say, 60 sec 2. set database to read-only mode 3. run some transactions in database 4. set database to read-write mode Bugcheck is logged at firebird.log at this poin |
Modified by: @hvladsummary: security3.fdb and "internal Firebird consistency check" => Bugcheck could happen when read-only database with non-zero linger is set to read-write mode |
|
Commented by: @hvlad v4 is not affected |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0.5 [ 10885 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: Basil A. Sidorov (basid)
Change access mode to security3.fdb.
Set read-only is success:
fbsvcmgr xnet://service_mgr action_properties prp_access_mode prp_am_readonly dbname security.db
Try return to read-write (fbsvcmgr xnet://service_mgr action_properties prp_access_mode prp_am_readwrite dbname security.db) - bugcheck in firebird.log:
Database: C:\PROGRAM FILES\FB\3.0.4\SECURITY3.FDB
internal Firebird consistency check (next transaction older than oldest active transaction (266), file: cch.cpp line: 4830)
After bugchek many operation will hang. F.e. connect to Firebir server on stop Firebird service.
Bug can exploit any user on server console, who knows sysdba password.
If set linger to zero (default is 60 for security3.db):
echo alter database drop linger | isql xnet://security.db
or
echo alter database drop linger | isql security.db
on initial setup for security3.db, then mode changed without bugcheck.
Commits: d7790dc
The text was updated successfully, but these errors were encountered: