ClearFoundation Tracker - ClearOS |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0001885 | ClearOS | app-network-detail-report - Network Detail Report | public | 2014-08-06 12:11 | 2020-09-03 04:46 |
|
| Reporter | NickH | |
| Assigned To | | |
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | closed | Resolution | suspended | |
| Platform | | OS | | OS Version | |
| Product Version | 6.5.0 | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0001885: app-network-detail-report causes runaway system-mysqld process |
| Description | Since the update of app-network-detail-report to 1.5.27 my system-mysqld process has run away causing a 100% CPU load. It is very similar to this thread: http://www.clearfoundation.com/component/option,com_kunena/Itemid,232/catid,12/func,view/id,61448/limit,10/limitstart,10/. [^]
Removing app-network-detail-report and app-network-detail-report-core on their own did not fix it. I also had to remove pmacct. |
| Steps To Reproduce | |
| Additional Information | I have not tried the suggestion by zombu2 in the thread as I don't know how to reverse it if it goes wrong and I'd prefer an official ClearOS solution. |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2014-08-06 12:11 | NickH | New Issue | |
| 2014-08-06 15:23 | user2 | Note Added: 0001264 | |
| 2014-08-06 15:23 | user2 | Status | new => feedback |
| 2014-08-07 09:00 | dloper | Note Added: 0001266 | |
| 2014-10-31 00:24 | intelliant | Note Added: 0001304 | |
| 2014-10-31 00:24 | intelliant | Note Edited: 0001304 | bug_revision_view_page.php?bugnote_id=1304#r147 |
| 2014-10-31 07:45 | intelliant | Note Added: 0001305 | |
| 2019-03-19 10:33 | NickH | Summary | app-network-detaill-report causes runaway system-mysqld process => app-network-detail-report causes runaway system-mysqld process |
| 2020-09-03 04:46 | NickH | Note Added: 0014631 | |
| 2020-09-03 04:46 | NickH | Status | feedback => new |
| 2020-09-03 04:46 | NickH | Status | new => closed |
| 2020-09-03 04:46 | NickH | Resolution | open => suspended |
|
Notes |
|
|
(0001264)
|
|
user2
|
|
2014-08-06 15:23
|
|
|
|
|
(0001266)
|
|
dloper
|
|
2014-08-07 09:00
|
|
Here is another related report:
"CPU trashing of system-mysqld seems related to /usr/sbin/networkdetail2db.
I have disabled this cron job for the mean time.
"There seems to be a stale lock on the process, as /var/log/syslog has many
instances of
"networkdetail2db: Unable to start script - currently running."
"I don't see where the lock is being stored.
I"nside the reports DB, the network_detail schema is missing indexes on at
least the following rows. I don't recall if I ever posted a bug report on
the rpm install for app-network-detail-*. Basically, IIRC, the post-install
script parses for the existance of a network* table from reports. However,
how it is written, the initialization of the database fails because the way
the regex is written, it's far too aggressive and finds app-network-*
first, then skips the db init." |
|
|
|
|
|
|
|
|
|
As reported by NickH, removal of pmacct is also required to get back to normal load. |
|
|
|
(0014631)
|
|
NickH
|
|
2020-09-03 04:46
|
|
|