The web page cannot load resource files such as images when starting redash

tengjiuying · June 29, 2019, 1:11am

Issue Summary

When I typed localhost:5000 in firefox, the following page appeared

At this point the following errors will pop up in the docker-compose up：

server_1 | ERROR in webpack [/app/redash/handlers/webpack.py:19]:
server_1 | Unable to load webpack manifest
server_1 | --------------------------------------------------------------------------------
server_1 | Traceback (most recent call last):
server_1 | File “/app/redash/handlers/webpack.py”, line 16, in get_asset
server_1 | with open(WEBPACK_MANIFEST_PATH) as fp:
server_1 | IOError: [Errno 2] No such file or directory: ‘/app/redash/handlers/…/…/client/dist/asset-manifest.json’

I don’t know what’s wrong, so I hope someone can help me. Thank you

Technical details:

Redash Version:
Browser/OS:centos7
How did you install Redash:

Install docker
Install nodejs
git clone GitHub - getredash/redash: Make Your Company Data Driven. Connect to any data source, easily visualize, dashboard and share your data.
docker-compose up
npm install
Create tables docker -compose run --rm server create_db
docker -compose run --rm postgres psql -h postgres -U postgres -c “create database tests”
docker -compose -f docker -compose.yml up -d

But when I run NPM install it’s wrong：
npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.
npm WARN deprecated @mapbox/gl-matrix@0.0.1: This
npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm WARN deprecated @babel/polyfill@7.4.4: As of Babel 7.4.0, this
npm WARN deprecated package has been deprecated in favor of directly
npm WARN deprecated including core-js/stable (to polyfill ECMAScript
npm WARN deprecated features) and regenerator-runtime/runtime
npm WARN deprecated (needed to use transpiled generator functions):
npm WARN deprecated
npm WARN deprecated > import “core-js/stable”;
npm WARN deprecated > import “regenerator-runtime/runtime”;
npm WARN deprecated browserslist@1.7.7: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated flatten@1.0.2: I wrote this module a very long time ago; you should use something else.

justinclift · June 29, 2019, 11:11am

It definitely looks like something went wrong with the installation process.

If you’re ok with re-doing it, since you’re using CentOS 7 maybe try this setup.sh script?

github.com

justinclift/redash/blob/redash-centos7/setup/setup.sh

#!/usr/bin/env bash
# This script sets up dockerized Redash on CentOS 7 and Ubuntu 18.04.
set -u

REDASH_BASE_PATH=/opt/redash
COMPOSE_PATH=/usr/local/bin/docker-compose
COMPOSE_VERSION="1.24.0"

distro=unknown
install_docker(){
    # Check for CentOS vs Ubuntu, then install Docker as appropriate
    which yum >/dev/null 2>&1
    if [ $? -eq 0 ]; then
        distro=centos7
        sudo yum -y update
        sudo yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
        sudo curl -L -o /etc/yum.repos.d/docker-ce.repo https://download.docker.com/linux/centos/docker-ce.repo
        sudo chown root:root /etc/yum.repos.d/docker-ce.repo
        sudo restorecon -Fv /etc/yum.repos.d/docker-ce.repo
        sudo yum -y install docker-ce pwgen yajl

This file has been truncated. show original

It’s a CentOS 7 specific version of the setup script, and I’ve used it a few times over the past few months for new installations. It “just works”.

Well, for me it has, and a few other people have mentioned using it as well.

arikfr · June 30, 2019, 6:48am

It looks like you didn’t run npm run build to create the static assets.

Although if this is a non development deployment, I recommend @justinclift’s script.

tengjiuying · July 1, 2019, 5:53am

Do I need to reinstall centos7?If I need to reinstall centos7, can I just run the setup.sh file after installation?thank you

justinclift · July 1, 2019, 2:13pm

If you’re doing this in a VM or similiar system where reinstalling CentOS isn’t going to be a bunch of effort, then I’d recommend that just so this follows a 100% known good path.

If reinstalling CentOS would be painful though… then you’ll probably be ok to just delete the Redash images and containers from your docker instance, then run setup.sh again.

Out of curiosity, are you comfortable reading through shell scripting? If you are… then the setup.sh script itself isn’t too complex. Instead of running it directly, you can run the commands from it one by one manually, which should let you catch anything weird right away.

tengjiuying · July 3, 2019, 3:54pm

Thank you very much. Setup. sh can be used successfully. I am very sorry for the late reply because I am busy preparing for the exam these days.

justinclift · July 3, 2019, 4:11pm

It’s no worries at all. Glad you got it working.

Good luck with your exams!

nop4ss · July 6, 2019, 9:36pm

me too.

husky@1.3.1 install /frontend/node_modules/husky
node husky install

husky > setting up git hooks
Can’t find .git, skipping Git hooks installation.
Please check that you’re in a cloned repository or run ‘git init’ to create an empty Git repository and reinstall husky.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

added 2060 packages from 1094 contributors and audited 96985 packages in 704.498s
found 24 vulnerabilities (17 moderate, 7 high)
run npm audit fix to fix them, or npm audit for details
Removing intermediate container 767f306b2f2c

▼Categories

▼Tags

The web page cannot load resource files such as images when starting redash

Issue Summary

Technical details: