|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 5178 | major | always | 08-16-12 02:23 | 08-22-12 15:30 | |
|
|
|||||
| Reporter: | nmmn | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.29 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.31 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |