[dev.icinga.com #2601] Segmentation fault in ido2db dbqueries.c #967
Comments
Updated by mfriedrich on 2012-05-11 14:03:56 +00:00 why was that limited anyway? |
Updated by mfriedrich on 2012-05-13 17:39:15 +00:00
ok, this was introduced with this commit in #2342
vs
|
Updated by mfriedrich on 2012-05-13 17:57:51 +00:00
can you test the fix in 'next' please? https://git.icinga.org/?p=icinga-core.git;a=shortlog;h=refs/heads/next |
Updated by mfriedrich on 2012-05-14 15:13:06 +00:00
my tests run ok, and it should hit the release, otherwise a revert of the feature will be necessary in order to compete with QA. re-open if more thoughts on that, my quickfix should do the trick for now. |
Updated by Tommi on 2012-05-14 18:05:00 +00:00 copy and paste should be disabled, at least for me :-((((. |
Updated by mfriedrich on 2012-05-14 18:12:54 +00:00 hmmm maybe you should change your settings to get all issues? at least i do get everything. |
Updated by mfriedrich on 2014-12-08 14:35:59 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/2601
Created by jmosshammer on 2012-05-11 11:10:10 +00:00
Assignee: jmosshammer
Status: Resolved (closed on 2012-05-14 15:13:06 +00:00)
Target Version: 1.7
Last Update: 2014-12-08 14:35:59 +00:00 (in Redmine)
this is probably related to #2342:
We still have problems with long outputs, causing pending states and active checks/notification disabled entries in the database.
As I didn't give real feedback to 2342, I debugged ido2db by myself and found the issue being a segmentation fault in the ido2db_query_insert_or_update_servicestatusdata_add function (dbqueries.c 3573):
3572 if (strlen((char*) data[4]) > IDO2DB_MYSQL_MAX_TEXT_LEN ) {
3573 ((char*) data[5])[IDO2DB_MYSQL_MAX_TEXT_LEN]=0;
Here, the length of data[4] is checked, but the char in data[5] is being truncated. I changed it to:
3572 if (strlen((char*) data[5]) > IDO2DB_MYSQL_MAX_TEXT_LEN ) {
3573 ((char*) data[5])[IDO2DB_MYSQL_MAX_TEXT_LEN]=0;
Which works fine
Changesets
2012-05-13 17:54:42 +00:00 by mfriedrich 3aa3c09
Relations:
The text was updated successfully, but these errors were encountered: