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
Random crash 64bit fb_inet_server. Possible collation issue [CORE6054] #6304
Comments
Commented by: ERCAN P. (programlama_akinsoft.com.tr) I am trying to attach screenshot. |
Commented by: ERCAN P. (programlama_akinsoft.com.tr) WinDgb output sceentshot added.. I can send zipped dump file to a developer. |
Modified by: ERCAN P. (programlama_akinsoft.com.tr)Attachment: DbgX.Shell_2019-04-26_16-41-47.png [ 13341 ] |
Commented by: @hvlad Provide us with download link, please |
Commented by: ERCAN P. (programlama_akinsoft.com.tr) You can download from this link. |
Commented by: @hvlad Send pwd to mailto:hvlad@users.sourceforge.net, please |
Commented by: @hvlad Thanks, Is it reproducible ? I want to verify patch. |
Commented by: @hvlad Call stack of crashing thread # Call Site Looks like global_temp_collation_name (see frame 02) contains garbage left from previous failed attempt to parse some query. |
Commented by: ERCAN P. (programlama_akinsoft.com.tr) Hello, We solved crash temporarily yesterday by removing php service directory. Same service implemented as http://asp.net mvc (the time crash begin). We checked network logs and saw some search engines access the old php directory. We removed the complete directory for try and problem gone. We investigated running sql and there was an sql query which try to select recently removed column. It is reproducible (by activating php page) |
Modified by: Sean Leyne (seanleyne)status: Open [ 1 ] => Resolved [ 5 ] resolution: Won't Fix [ 2 ] |
Commented by: ERCAN P. (programlama_akinsoft.com.tr) Hello Mr. Sean. Why did you flag this report as "Wont Fix" ? We (three senior developers) spent nearly 2 weeks to solve this problem. If Mr. Vlad send us a patch we will be happy to try and send the result. |
Commented by: Sean Leyne (seanleyne) Ercan, Sorry, you posted that the problem was caused by external function (php service directory), as such there was no Firebird change required. Separately, there was no mention that Vlad had provided a patch. |
Modified by: Sean Leyne (seanleyne)status: Resolved [ 5 ] => Reopened [ 4 ] assignee: Vlad Khorsun [ hvlad ] resolution: Won't Fix [ 2 ] => |
Commented by: ERCAN P. (programlama_akinsoft.com.tr) Thank you Mr Sean. Yes we solved problem temporarily. But it is not a real solution. Other developers may suffer from same problem in the future. |
Commented by: @hvlad The minimal reproducible sample: 1. prepare table SQL> create table c (id int, f1 varchar(32) character set win1251 collate win1251); 2. run bad query with COLLATE clause SQL> select * from c where f2 collate win1251_ua = 'x'; 3. run query with string constant and charset introducer SQL> select * from c where f1 = _utf8 'x'; Here we see wrong error message with empty collation name. |
Commented by: @hvlad Fix is committed, please try next snapshot build |
Commented by: ERCAN P. (programlama_akinsoft.com.tr) Thank you Mr. Vlad. I think php service produced "column unknown" error and new http://asp.net service run query with _utf8 keyword (query built by .net provider). Same time we got a lot of "COLLATION for CHARACTER SET UTF8 is not defined" error feedback from our users before closing php service. |
Modified by: @pavel-zotovstatus: Reopened [ 4 ] => Reopened [ 4 ] QA Status: No test => Done successfully |
Modified by: @hvladstatus: Reopened [ 4 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.9 [ 10862 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: ERCAN P. (programlama_akinsoft.com.tr)
Attachments:
DbgX.Shell_2019-04-26_16-41-47.png
Hello. We are facing crash issue for about 10 days. Server has about 20 DB and is under load in working hours. Event Viewer shows unexpected terminations of server process. I have windbg dump file and it has sensitive information.
Commits: 8df4b76
The text was updated successfully, but these errors were encountered: