-
-
Notifications
You must be signed in to change notification settings - Fork 221
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
The message Unknown tag (4) in isc_svc_query() results
appears when fbtracemgr is interrupted by Ctrl-C [CORE3769]
#4113
Comments
Modified by: @dyemanovVersion: 2.5.1 [ 10333 ] Version: 2.5.0 [ 10221 ] Component: SVCMGR [ 10141 ] Component: TRACEMGR [ 10140 ] |
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Commented by: @AlexPeshkoff It's not good idea to add links to national forums from interantional tracker. Please provide reproducible test case here, preferably using only native firebird tools. |
Commented by: @AlexPeshkoff Pavel, will test case be provided or should I close as 'cannot reproduce'? |
Commented by: @pavel-zotov Alex, just now I have encountered this problem again, on our production. |
Commented by: @dyemanov Alex, is the test case really needed? As far as I see, our utilities don't check for isc_info_data_not_ready being returned from isc_svc_query(). The example of how it could be handled can be found in GBAK. What other info is needed? |
Commented by: @pavel-zotov I got it! create the following script named 'ibe.sql': commit; Then run isql utility in some folder (in my case: /var/db/firebird/test) and do these commands in it: Then connect from windows workstation to this database - let this session have name #1: session #1 session #2 (PUTTy console): session #1 SQL> in ibe.sql; RDB$RELATION_NAMEMON$ATTACHMENTS -- And this is "THE END". No further activity, all databases are hangs. Trace console: -------- start of trace console ----- 2012-03-27T19:35:33.8100 (5151:0x7fb3f1b6c648) START_TRANSACTION 2012-03-27T19:35:33.8140 (5151:0x7fb3f1b6c648) EXECUTE_STATEMENT_START Statement 35: 2012-03-27T19:35:33.8140 (5151:0x7fb3f1b6c648) EXECUTE_STATEMENT_FINISH Trace config file ('zaudit.conf'): log_statement_start true #log_trigger_start true bash-4.1$ lsof /var/db/firebird/test/test.fdb top -p 5151 top - 19:45:31 up 12 days, 17:13, 5 users, load average: 46.86, 37.16, 23.01 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND top -p $(pgrep fbtracemgr) top - 19:47:04 up 12 days, 17:14, 5 users, load average: 47.15, 39.89, 25.36 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND session # 3 (just for illustration: try to create another one database): PS. All these processes (fb_inet, fbtracemgr) can be cancelled only via kill -9, rather than kill -15. |
Commented by: @AlexPeshkoff Dmitry, adding code to process data_not_ready condition is very simple to do. But I want to know conditions under which it happens (looks like it may happen only during services manager shutdown). And the worst detail - it happens sometimes, i.e. looks like we have a kind of races here. Before hiding them at client side I want to understand how do they happen and can it be dangerous or not. |
Commented by: @AlexPeshkoff Pavel, sorry - I've tried to reproduce your hang, but no luck. The only difefrence is that instead of remote windows workstation (do not have one) I've used one more linux tty. Do not think that client makes much difference here. Everything works fine for me. PS. How is it related with initial problem? |
Commented by: @AlexPeshkoff No. |
Commented by: @AlexPeshkoff Pavel, may be you have some special firebird.conf settings? |
Commented by: @pavel-zotov I've tried this on: There were only few changes in firebird.conf, namely: # set 05.03.2012 1630, after change mode to SC: # to be increased after 12.03.2012 (check connects count and memo consumption before doing that!) # 28-11-2011 1747 # 28-11-2011 1747 # enabled 05-oct-2010 19:03 due to errors in firebird.log # 16.11.2010 15:15: # increased 12.03.2012: #LockHashSlots =3169 |
Commented by: @AlexPeshkoff Have no testcase to check, but this fix should help |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.2 [ 10450 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @pavel-zotov
Under some conditions fbtracemgr can output the following message when interrupt by Ctrl-C:
Unknown tag (4) in isc_svc_query() results
In particular I got this message when pressed Ctrl-C after tracing IBE for select count(*) from some_table.
Details (in russian): http://www.sql.ru/forum/actualutils.aspx?action=gotomsg&tid=838190&msg=12132939
Commits: 2c27cf6 57293c3
The text was updated successfully, but these errors were encountered: