|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4001 | major | always | 04-16-10 10:16 | 05-18-10 15:19 | |
|
|
|||||
| Reporter: | emil | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | high | OS Version: | |||
| Status: | closed | Product Version: | 4.0.6 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.7 | ||
|
|
|||||
| Summary: | 0004001: runaway watchdog process | ||||
| Description: |
(rep by Jamie Novak) I am unable to determine what?s causing it, but the WatchdogManager process spins out of control and uses between 150-200% of the CPU and never backs off. No useful information is logged in the watchdog-manager.log regardless of what I set the log level to. (Should I be doing something different with our logging? Is my config just sending some of it to the bit bucket instead of somewhere that I can see it?) When I start up just the web-tier, everything runs fine. I?m able to access our simple static HTML file that says ?welcome to this server?. The moment I attempt to start one of our clusters in addition to that, however, the watchdog begins chewing up CPU and never stops. The clustered site starts up and is accessible, but there?s obviously something wrong at the watchdog level that I can?t figure out. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | may be related to the keepalive select manager timing out prematurely | ||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |