Anonymous | Login | Signup for a new account | 01-05-2025 10:48 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0005178 | [Resin] | major | always | 08-16-12 02:23 | 08-22-12 15:30 | ||||
Reporter | nmmn | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.31 | Product Version | 4.0.29 | ||||
Product Build | |||||||||
Summary | 0005178: memory leak of resinctl status | ||||||||
Description |
We want to run resin in a cluster with corosync/pacemaker. This involves checking if the resin server is running properly. To do this, the cluster software calls /etc/init.d/resin status every 10 seconds. This leads to an out of memory error about every 50 minutes. If we call resin status manually in a loop, it happens faster. So there seems to be some kind of memory leak in the status code. We made sure this is the cause by starting resin on the same server manually and telling the cluster not to check its status. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
There are no notes attached to this issue. |
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
27 total queries executed. 25 unique queries executed. |