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

Rotated Trace files locked by engine [CORE5838] #6099

Closed
firebird-automations opened this issue May 31, 2018 · 12 comments
Closed

Rotated Trace files locked by engine [CORE5838] #6099

firebird-automations opened this issue May 31, 2018 · 12 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Sergey Borisov (bsv)

Attachments:
screenshot.PNG

Firebird 3.0.4 Classic on Windows OS running with system trace audit with log rotation param max_log_size = 50.

For many rotated files (not all) the engine still has a lock of the file, so they can not be opened for viewing. Within 6 hours we have 8 such files.

Commits: 27e4264

====== Test Details ======

Can not be implemented using current fbtest package: we have no ability to restart FB during tests for turning on/off system audit.
Probably will be implemented after developing additional batch scenario for this.

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Could you confirm that all such files are locked by idle Firebird Classic processes ?

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

assignee: Vlad Khorsun [ hvlad ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Sergey Borisov (bsv)

Yes, look the screenshot.
Firebird PID=2512 lock file fb_trace.2018-05-31T12-11-06.log.

@firebird-automations
Copy link
Collaborator Author

Modified by: Sergey Borisov (bsv)

Attachment: screenshot.PNG [ 13256 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Are you sure PID 2512 is idle ?

You may check it using monitoring tables.

Also, what happens with fb_trace.2018-05-31T12-11-06.log file when any audited event occurs in
attachment handled by PID 2512 (no need to disconnect it, just run some query, etc) ?

@firebird-automations
Copy link
Collaborator Author

Commented by: Sergey Borisov (bsv)

Yes, PID 2512 was in idle.
select A.Mon$state from mon$attachments A Where A.mon$server_pid in (2512)
return 0.

After running query and commiting transaction on that connection (PID 2512) , the lock disappeared.

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Thank for confirmation

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

Edited to clarify issue

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

description: Firebird 3.0.4 Classic on Windows OS runed with system trace audit with log rotation param max_log_size = 50.
Many rotated files (not all) is locked by firebird so, that it can not be opened for viewing. Within 6 hours we have 8 such files.

=>

Firebird 3.0.4 Classic on Windows OS running with system trace audit with log rotation param max_log_size = 50.

For many rotated files (not all) the engine still has a lock of the file, so they can not be opened for viewing. Within 6 hours we have 8 such files.

summary: Trace files monopoly locked by firebird => Rotated Trace files locked by engine

@firebird-automations
Copy link
Collaborator Author

Commented by: @hvlad

Fix is committed into v4.
Tested on Windows mostly, please test it carefully.

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

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

resolution: Fixed [ 1 ]

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: Can not be implemented using current fbtest package: we have no ability to restart FB during tests for turning on/off system audit.
Probably will be implemented after developing additional batch scenario for this.

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

No branches or pull requests

2 participants