https://issues.rudder.io/https://issues.rudder.io/themes/rudder7/favicon/favicon.ico?17096450182017-03-16T09:32:47ZIssue TrackerRudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=732662017-03-16T09:32:47ZAlexis Moussetalexis.mousset@rudder.io
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/73266/diff?detail_id=92232">diff</a>)</li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=734932017-03-21T14:40:47ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>User visibility</strong> changed from <i>First impressions of Rudder</i> to <i>Getting started - demo | first install | level 1 Techniques</i></li></ul><p>We are not able to reproduce it, so I'm closing it (ouf)</p> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=738082017-03-27T12:20:57ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-6 priority-16 priority-default closed" href="/issues/10505">Bug #10505</a>: During a migration from 4.0 to 4.1, ldap base was emptied</i> added</li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=738092017-03-27T12:25:18ZFrançois ARMANDfrancois.armand@rudder.io
<ul></ul><p>For record, and because it may happens commonly: now, CSS/JS/font are served by Rudder web-app directly, not the jetty server under it. So if the Rudder web-app doesn't starts correctly, then we don't have any CSS/JS. The cause of the bad start is most likelly a problem with the LDAP server (see for ex <a class="issue tracker-1 status-6 priority-16 priority-default closed" title="Bug: During a migration from 4.0 to 4.1, ldap base was emptied (Rejected)" href="https://issues.rudder.io/issues/10505">#10505</a>) or a problem with the Postgres base.</p>
<p>In each case, the logs in `/var/log/rudder/webapp/YYYY_MM_DD.sderrout.log` will contain relevant information about whas went wrong.</p> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=738102017-03-27T12:26:03ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Subject</strong> changed from <i>No css nor js on SLES 11</i> to <i>No css nor js on Rudder 4.1</i></li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=738212017-03-27T13:23:57ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/73821/diff?detail_id=93136">diff</a>)</li></ul><p>Adding the last comment in the ticket description to help people find the relevant information quicker.</p> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=738222017-03-27T13:24:33ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/73822/diff?detail_id=93137">diff</a>)</li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=740022017-03-28T14:31:29ZBenoît PECCATTEbenoit.peccatte@rudder.io
<ul><li><strong>Priority</strong> set to <i>78</i></li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=746812017-04-06T13:42:49ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Status</strong> changed from <i>Rejected</i> to <i>New</i></li><li><strong>Target version</strong> changed from <i>4.1.0</i> to <i>4.1.1</i></li><li><strong>Severity</strong> changed from <i>Critical - prevents main use of Rudder | no workaround | data loss | security</i> to <i>Major - prevents use of part of Rudder | no simple workaround</i></li><li><strong>Priority</strong> changed from <i>78</i> to <i>0</i></li></ul><p>I'm opening it again, because it is EXTREMELLY misleading to have. We should head to the page explaining that there is a problem, not a broken Rudder page.</p>
<p>I'm also changing the severity, because it is only a symptom of an other problem during the webapp init, so the missing css/js is not critical per se. But I'm letting it to "major", because Rudder seems very broken, and it is more than misleading.</p> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=746842017-04-06T14:11:24ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-6 priority-low2 closed parent" href="/issues/1974">Bug #1974</a>: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayed</i> added</li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=747102017-04-07T09:43:02ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-16 priority-default closed parent" href="/issues/10567">Bug #10567</a>: Infinite "rudder is loading" page if rudder-init didn't run</i> added</li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=752732017-04-14T15:11:51ZVincent MEMBRÉvme@rudder.io
<ul><li><strong>Target version</strong> changed from <i>4.1.1</i> to <i>4.1.2</i></li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=757582017-04-25T08:19:25ZJonathan CLARKEjonathan.clarke@normation.com
<ul><li><strong>Assignee</strong> deleted (<del><i>Alexis Mousset</i></del>)</li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=758522017-04-25T12:45:34ZJonathan CLARKEjonathan.clarke@normation.com
<ul><li><strong>Severity</strong> changed from <i>Major - prevents use of part of Rudder | no simple workaround</i> to <i>Critical - prevents main use of Rudder | no workaround | data loss | security</i></li><li><strong>Priority</strong> changed from <i>0</i> to <i>78</i></li></ul><p>This should probably cause the rudder web interface to return a 5xx error so that the Apache proxy front can display an appropriate error message. If the resources are not available, there's no point trying to display the page contents.</p>
<p>A lot of users have seen this recently while trying out Rudder and were completly stuck as to how to proceed. There <strong>does</strong> exist a simple workaround (usually), but it is <strong>not</strong> easily available, therefore bumping this to Critical - a new user just can't proceed with using Rudder when this bug occurs. Adding an error page that explains what to check, or which docs to read, would enable us to reduce this severity.</p> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=758542017-04-25T12:46:08ZJonathan CLARKEjonathan.clarke@normation.com
<ul><li><strong>Subject</strong> changed from <i>No css nor js on Rudder 4.1</i> to <i>Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)</i></li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=759192017-04-25T16:33:45ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>With the correction of <a class="issue tracker-1 status-5 priority-6 priority-low2 closed parent" title="Bug: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page... (Released)" href="https://issues.rudder.io/issues/1974">#1974</a>, this bug should not happen anymore. We still may have the problem linked to <a class="issue tracker-1 status-5 priority-16 priority-default closed parent" title="Bug: Infinite "rudder is loading" page if rudder-init didn't run (Released)" href="https://issues.rudder.io/issues/10567">#10567</a> (ie: infinite loading page). I'm closing that one as duplicate (of <a class="issue tracker-1 status-5 priority-6 priority-low2 closed parent" title="Bug: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page... (Released)" href="https://issues.rudder.io/issues/1974">#1974</a>)</p> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=759212017-04-25T16:33:58ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-1 status-5 priority-6 priority-low2 closed parent" href="/issues/1974">Bug #1974</a>: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayed</i>)</li></ul> Rudder - Bug #10430: Broken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)https://issues.rudder.io/issues/10430?journal_id=759222017-04-25T16:34:05ZFrançois ARMANDfrancois.armand@rudder.io
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-1 status-5 priority-6 priority-low2 closed parent" href="/issues/1974">Bug #1974</a>: If an error happen during boostrap, the webapp starts but is in a zombie state and the error page is not displayed</i> added</li></ul>