https://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182012-04-17T16:41:23ZIssue TrackerRudder - Bug #2280: Error displaying node details: Server cannot be contacted at this timehttps://issues.rudder.io/issues/2280?journal_id=91172012-04-17T16:41:23ZNicolas CHARLESnicolas.charles@rudder.io
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Discussion</i></li><li><strong>Assignee</strong> changed from <i>François ARMAND</i> to <i>Jonathan CLARKE</i></li></ul><p>I guess it was around the time when the webapp was crippled by an enormous amount of logs and poor databases indexes, inducing a tool long answer from the server, and thus a timeout<br />I cannot reproduce it.<br />Would you have more details ?</p> Rudder - Bug #2280: Error displaying node details: Server cannot be contacted at this timehttps://issues.rudder.io/issues/2280?journal_id=92442012-04-23T14:07:34ZJonathan CLARKEjonathan.clarke@normation.com
<ul><li><strong>Status</strong> changed from <i>Discussion</i> to <i>Rejected</i></li></ul><p>Nicolas CHARLES wrote:</p>
<blockquote>
<p>I guess it was around the time when the webapp was crippled by an enormous amount of logs and poor databases indexes, inducing a tool long answer from the server, and thus a timeout<br />I cannot reproduce it.<br />Would you have more details ?</p>
</blockquote>
<p>Yes, that's absolutely right. This was due to a bug in the advanced reporting plugin that was basically hogging all CPU. Poor Rudder couldn't be expected to much better given the circumstances! I'll close this as rejected.</p>