Dataiku on Windows Linux Subsystem Fail

[Ricardo]

When I run /mnt/d/dataiku/DATA_DIR/bin/dss start I got: dss: DSS supervisor is not running *** dss : DSS supervisor failed to start.

Looking at /mnt/d/dataiku/DATA_DIR/run/supervisord.log I got:

2019-06-11 21:42:09,600 INFO RPC interface 'supervisor' initialized
2019-06-11 21:42:09,605 INFO daemonizing the supervisord process
2019-06-11 21:42:09,606 INFO set current directory: '/mnt/d/dataiku/DATA_DIR/run'
2019-06-11 21:42:09,609 INFO supervisord started with pid 3918
2019-06-11 21:42:10,623 INFO spawned: 'ipython' with pid 3921
2019-06-11 21:42:10,629 INFO spawned: 'nginx' with pid 3922
2019-06-11 21:42:10,636 INFO spawned: 'backend' with pid 3923
2019-06-11 21:42:15,637 INFO success: ipython entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2019-06-11 21:42:15,637 INFO success: nginx entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2019-06-11 21:42:20,936 INFO success: backend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2019-06-11 21:42:43,941 ERRO /mnt/d/dataiku/DATA_DIR/run/svd.sock:Server Error: , string index out of range: file: /mnt/d/dataiku/dataiku-dss-5.1.4/python.packages/supervisor/http.py line: 232
2019-06-11 21:45:30,662 INFO RPC interface 'supervisor' initialized
2019-06-11 21:45:30,683 INFO daemonizing the supervisord process
2019-06-11 21:45:30,684 INFO set current directory: '/mnt/d/dataiku/DATA_DIR/run'
2019-06-11 21:45:30,684 INFO supervisord started with pid 44
2019-06-11 21:45:31,723 INFO spawned: 'ipython' with pid 47
2019-06-11 21:45:31,728 INFO spawned: 'nginx' with pid 48
2019-06-11 21:45:31,734 INFO spawned: 'backend' with pid 49
2019-06-11 21:45:37,032 INFO success: ipython entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2019-06-11 21:45:37,032 INFO success: nginx entered RUNNING state, process has stayed up for > than 5 seconds (startsecs)
2019-06-11 21:45:41,930 INFO success: backend entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)

Any help?

[jereze]

Hi,

I've never tried to run Dataiku DSS on the Windows Subsystem for Linux (WSL). But on our installation page I can read the following:

"Please note that Dataiku DSS will not work properly if it is installed in a mounted directory accessible from Windows (ex: /mnt/c/). "

And in your message I see: /mnt/d/dataiku/

I guess that's the origin of your issue.

[Kjeanclaude]

The Key with Windows Subsystem for Linux (WSL) is that DSS should be installed in the Ubuntu (or your Linux system) user account to work. If you put the files somewhere else, it will not work.

====================== A DETAILED PROCESS ========================
1. Installation
cd ~/ or cd /home/<your user name>/
mkdir DSS
cd DSS/
wget https://cdn.downloads.dataiku.com/public/dss/9.0.1/dataiku-dss-9.0.1.tar.gz
tar xzf dataiku-dss-9.0.1.tar.gz
dataiku-dss-9.0.1/installer.sh -d DATA_DIR -p 11000

if dependencies are not installed:
sudo -i "~/DSS/dataiku-dss-9.0.1/scripts/install/install-deps.sh"

/home/<your user name>/DSS/DATA_DIR/bin/dss start

2. Installation checking
You can re-check its status using the following command:
/home/<your user name>/DSS/DATA_DIR/bin/dss status
You can look for startup error messages in log file:
/home/<your user name>/DSS/DATA_DIR/run/backend.log
==============================================

[tgb417]

@Kjeanclaude ,

Welcome to the Dataiku community. 

For my installation I’ve taken on a slight variant of what you are describing.  I created a separate account within my Ubuntu (running under WSL2). And I’m running DSS in that account.  And yes, I installed DSS in the home directory of this account (not on a mounted disk, pointing back to a windows NTFS formatted disk.)

Please note when we are using WSL2 we are coloring a bit outside of the lines. As far as I understand Dataiku does not support what we are trying to do.  

Related, I hear that WSL may not be particularly good about reclaiming disk space that gets allocated to its Linux volumes.  Has anyone run into any problems with this?

Second question.  Has anyone figured out how to get DSS to auto start up when your Linux environment starts in WSL2.  Last time I tried these instructions they failed for me.  It is my understanding that one of the strange things about WSL2 is it does not start applications in the same way that typical Linux might do with systemd.