#back to user su a***** wget https://downloads.dataiku.com/public/studio/4.0.9/dataiku-dss-4.0.9.tar.gz tar xzf dataiku-dss-4.0.9.tar.gz mkdir /home/a*****/dataikudata dataiku-dss-4.0.9/installer.sh -d /home/a*****/dataikudata/dss_data -p 11000 /home/a*****/dataiku_datadir/dss_data/bin/dss start
the "permission denied" error on "/var/log/nginx/error.log" is expected and can be safely ignored. It is a warning from nginx that the compiled-in log file is not writable, but this only applies to the very beginning of the startup sequence before the DSS-generated configuration file is loaded.
You can check with '/home/a*****/dataikudata/dss_data/bin/dss status' that all the DSS components started correctly. If that is not the case, further error details should be in the corresponding log file in dss_data/run
However you mention that no other log lines are in nginx.log, though, so most probably the nginx component could start correctly. I would look for a network-level error then: firewall blocking this port on the local host? or a connectivity problem between browser and host?
Ways to dig into it would include: - checking that the http service works locally with: "curl http://localhost:11000" on the DSS host - checking the exact network error seen by the browser, maybe in its console, or by accessing the DSS URL from a command line tool eg curl on the user workstation - using ssh port-forwarding on port 11000 from the user workstation to the DSS server to check whether it allows connection (bypassing any firewall)
Details on the above available on request, of course Hope this helps Patrice Bertin Dataiku
Great. Note that if preferable for your environment, you can leave the firewall running and only open the DSS port with: sudo firewall-cmd --add-port=11000/tcp sudo firewall-cmd --add-port=11000/tcp --permanent # to persist after reboot
the first step of the investigation would be to retrieve the exact error message observed when connecting to the DSS URL from the user workstation (unknown host? connection refused? connection timed out? etc) Connecting from a browser will usually give you a high-level error message, which may be informative enough. Otherwise, the best is probably to try to connect from the end-user workstation with a command-line tool (eg: curl http://DSS_HOST:11000) as this would typically show the real error.
You may want to check for: - a local firewall running on the DSS host (and blocking port 11000) - a network firewall on the path between the user browser and the DSS host (that includes cloud infrastructure firewall aka "security groups" when running on a cloud instance) - a proxy configured on the user browser - a local security package on the user workstation
- I do not understand what you mean by "the file is autogenerated, do not edit manually". Running "curl http://localhost:11000" directly from the server is intended to check whether DSS works and can be queried locally. If this command returns raw HTML (as opposed to: fails with an error) it means that DSS works and that the problem lies in the network transport between the browser and port 11000 of this host. I would check for firewall issues first.
- it is expected that port 80 is not working. Except if you manually set up a reverse proxy (this is described in our online doc) DSS is running on port 11000, and nothing is configured on port 80
- checking that the http service works locally with: "curl http://localhost:11000" on the DSS host This file is autogenerated, do not edit manually - checking the exact network error seen by the browser, maybe in its console, or by accessing the DSS URL from a command line tool eg curl on the user workstation This file is autogenerated, do not edit manually - using ssh port-forwarding on port 11000 from the user workstation to the DSS server to check whether it allows connection (bypassing any firewall) port 80 itself not working - i cannot see nginx welcome page ; i suspect permission issue or installation did not work on nginx as it installed