Actions
Bug #10430
closedBroken pages served by Rudder 4.1 with no explanation (missing JS/CSS due to unavailable LDAP server)
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
78
Name check:
Fix check:
Regression:
Description
Symptoms¶
root@server:~# rpm -qa | grep rudder-webapp rudder-webapp-4.1.0.rc2.git201703150133-1.SLES.11.noarch
I get, in the console:
[Report Only] Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-1BNJtQAi+u7koWiPaZnmB/XP12FM6dRgu7gQTBzadBM='), or a nonce ('nonce-...') is required to enable inline execution. index.html:92 Uncaught ReferenceError: $ is not defined at index.html:92 lift.js:1 Uncaught ReferenceError: jQuery is not defined at lift.js:1 at lift.js:1 lift.js:1 onDocumentReady function must be defined in settings consoleOrAlert @ lift.js:1 https://localhost:8381/favicon.ico Failed to load resource: the server responded with a status of 403 (Forbidden)
These is not attempt to load css or js files, except lift.js and socialwidgets.css.
Cause and related information¶
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 #10505) or a problem with the Postgres base.
In each case, the logs in `/var/log/rudder/webapp/YYYY_MM_DD.sderrout.log` will contain relevant information about whas went wrong.
Actions