Bug 463858
Summary: | cacti segfault | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> |
Component: | cacti | Assignee: | Mike McGrath <mmcgrath> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | bugzilla77, fedora, jorton, mmcgrath, rpm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-07-14 14:30:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Orion Poplawski
2008-09-24 22:57:51 UTC
#3 0x00ba38b6 in zend_do_fcall_common_helper_SPEC (execute_data=0xbee480d8) ... #22741 0x00ba38b6 in zend_do_fcall_common_helper_SPEC (execute_data=0xbfa40518) at /usr/src/debug/php-5.2.6/Zend/zend_vm_execute.h:234 this is a recursive function call in the PHP script, which will kill the interpreter. Okay, tracked this down to db_fetch_row in database.php: function db_fetch_row($sql, $log = TRUE) { global $cnn_id; $sql = str_replace("\n", "", str_replace("\r", "", str_replace("\t", " ", $sql))); if (($log) && (read_config_option("log_verbosity") == POLLER_VERBOSITY_DEBUG)) { cacti_log("DEBUG: SQL Row: \"" . $sql . "\"\n", FALSE); } $cnn_id->SetFetchMode(ADODB_FETCH_ASSOC); $query = $cnn_id->Execute($sql); if (($query) || ($cnn_id->ErrorNo() == 1032)) { if (!$query->EOF) { $fields = $query->fields; $query->close(); return($fields); } }else if (($log) || (read_config_option("log_verbosity") == POLLER_VERBOSITY_DEBUG)) { cacti_log("ERROR: SQL Row Failed!, Error:'" . $cnn_id->ErrorNo() . "', SQL:\"" . str_replace("\n", "", str_replace("\r", "", str_replace("\t", " ", $sql))) . "\"", FALSE); } } If the query fails (due to database errors) we enter a recursive loop because we call read_config_option which calls db_fetch_row, which fails and so on. This only happens when there is a problem with the database (as was my case). In normal operation this doesn't occur. seems DUP of https://bugzilla.redhat.com/show_bug.cgi?id=480500 This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |