spot-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diego Ortiz <daort...@apache.org>
Subject Re: Help on Spot installation (following Slack discussion with Nate)
Date Mon, 10 Apr 2017 15:24:49 GMT
Yeah, please make sure your user has write permissions on spot-oa/ and
spot-oa/ui/ dirs. Also veritfy that your system has Internet access as it
will try to download npm dependencies, by the time it tries to create those
min.js files you should already have a node_modules/ dir with several
packages in it.

On Mon, Apr 10, 2017, 1:55 AM Dimitris Papadopoulos <
dpapadopoulos91@gmail.com> wrote:

> Thx Diego,
>
> It seems that I can't npm install properly, i get "permission denied" while
> trying to create the *.min.js. Below is the output:
>
>
> spotuser@master:~/spot-oa/ui$ npm install
>
> > spot_ui@1.1.0 postinstall /home/spotuser/spot-oa/ui
> > npm run build-all
>
>
> > spot_ui@1.1.0 build-all /home/spotuser/spot-oa/ui
> > npm run build-flow && npm run build-dns && npm run build-proxy &&
npm run
> build-ingest-summary
>
>
> > spot_ui@1.1.0 build-flow /home/spotuser/spot-oa/ui
> > cd flow/ && npm run build-all && cd ../
>
>
> > spot_ui_flow@1.1.0 build-all /home/spotuser/spot-oa/ui/flow
> > npm run build-suspicious && npm run build-threat-investigation &&
npm run
> build-storyboard
>
>
> > spot_ui_flow@1.1.0 build-suspicious /home/spotuser/spot-oa/ui/flow
> > browserify js/suspicious.js | uglifyjs -cm > js/suspicious.bundle.min.js
>
> sh: 1: cannot create js/suspicious.bundle.min.js: Permission denied
> npm ERR! code ELIFECYCLE
> npm ERR! errno 2
> npm ERR! spot_ui_flow@1.1.0 build-suspicious: `browserify js/suspicious.js
> | uglifyjs -cm > js/suspicious.bundle.min.js`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the spot_ui_flow@1.1.0 build-suspicious script
> 'browserify js/suspicious.js | uglifyjs -cm > js/suspicious
> .bundle.min.js'.
> npm ERR! Make sure you have the latest version of node.js and npm
> installed.
> npm ERR! If you do, this is most likely a problem with the spot_ui_flow
> package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     browserify js/suspicious.js | uglifyjs -cm >
> js/suspicious.bundle.min.js
> npm ERR! You can get information on how to open an issue for this project
> with:
> npm ERR!     npm bugs spot_ui_flow
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR!     npm owner ls spot_ui_flow
> npm ERR! There is likely additional logging output above.
> npm WARN Local package.json exists, but node_modules missing, did you mean
> to install?
>
> npm ERR! A complete log of this run can be found in:
> npm ERR!     /home/spotuser/.npm/_logs/2017-04-10T08_38_55_374Z-debug.log
> npm ERR! code ELIFECYCLE
> npm ERR! errno 2
> npm ERR! spot_ui_flow@1.1.0 build-all: `npm run build-suspicious && npm
> run
> build-threat-investigation && npm run build-story
> board`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the spot_ui_flow@1.1.0 build-all script 'npm run
> build-suspicious && npm run build-threat-investigation &&
> npm run build-storyboard'.
> npm ERR! Make sure you have the latest version of node.js and npm
> installed.
> npm ERR! If you do, this is most likely a problem with the spot_ui_flow
> package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     npm run build-suspicious && npm run build-threat-investigation
> && npm run build-storyboard
> npm ERR! You can get information on how to open an issue for this project
> with:
> npm ERR!     npm bugs spot_ui_flow
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR!     npm owner ls spot_ui_flow
> npm ERR! There is likely additional logging output above.
> npm WARN Local package.json exists, but node_modules missing, did you mean
> to install?
>
> npm ERR! A complete log of this run can be found in:
> npm ERR!     /home/spotuser/.npm/_logs/2017-04-10T08_38_55_383Z-debug.log
> npm ERR! code ELIFECYCLE
> npm ERR! errno 2
> npm ERR! spot_ui@1.1.0 build-flow: `cd flow/ && npm run build-all &&
cd
> ../`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the spot_ui@1.1.0 build-flow script 'cd flow/ && npm
> run
> build-all && cd ../'.
> npm ERR! Make sure you have the latest version of node.js and npm
> installed.
> npm ERR! If you do, this is most likely a problem with the spot_ui package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     cd flow/ && npm run build-all && cd ../
> npm ERR! You can get information on how to open an issue for this project
> with:
> npm ERR!     npm bugs spot_ui
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR!     npm owner ls spot_ui
> npm ERR! There is likely additional logging output above.
>
> npm ERR! A complete log of this run can be found in:
> npm ERR!     /home/spotuser/.npm/_logs/2017-04-10T08_38_55_392Z-debug.log
> npm ERR! code ELIFECYCLE
> npm ERR! errno 2
> npm ERR! spot_ui@1.1.0 build-all: `npm run build-flow && npm run build-dns
> && npm run build-proxy && npm run build-ingest-sum
> mary`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the spot_ui@1.1.0 build-all script 'npm run build-flow
> && npm run build-dns && npm run build-proxy && npm
> run build-ingest-summary'.
> npm ERR! Make sure you have the latest version of node.js and npm
> installed.
> npm ERR! If you do, this is most likely a problem with the spot_ui package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     npm run build-flow && npm run build-dns && npm run build-proxy
> && npm run build-ingest-summary
> npm ERR! You can get information on how to open an issue for this project
> with:
> npm ERR!     npm bugs spot_ui
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR!     npm owner ls spot_ui
> npm ERR! There is likely additional logging output above.
>
> npm ERR! A complete log of this run can be found in:
> npm ERR!     /home/spotuser/.npm/_logs/2017-04-10T08_38_55_401Z-debug.log
>
> npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~0.3.1
> (node_modules/watchify/node_modules/chokidar/node_modules/fse
> vents):
> npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
> fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (c
> urrent: {"os":"linux","arch":"x64"})
> npm WARN spot_ui@1.1.0 license should be a valid SPDX license expression
> npm ERR! Linux 3.13.0-112-generic
> npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
> npm ERR! node v7.8.0
> npm ERR! npm  v4.2.0
> npm ERR! code ELIFECYCLE
> npm ERR! errno 2
> npm ERR! spot_ui@1.1.0 postinstall: `npm run build-all`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the spot_ui@1.1.0 postinstall script 'npm run
> build-all'.
> npm ERR! Make sure you have the latest version of node.js and npm
> installed.
> npm ERR! If you do, this is most likely a problem with the spot_ui package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     npm run build-all
> npm ERR! You can get information on how to open an issue for this project
> with:
> npm ERR!     npm bugs spot_ui
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR!     npm owner ls spot_ui
> npm ERR! There is likely additional logging output above.
>
> npm ERR! Please include the following file with any support request:
> npm ERR!     /home/spotuser/.npm/_logs/2017-04-10T08_38_55_436Z-debug.log
> spotuser@master:~/spot-oa/ui$
>
>
> 2017-04-10 0:18 GMT+03:00 Diego Ortiz <daortizh@apache.org>:
>
> > The "npm install" command is the one that runs the build command to
> create
> > those min.js files, please re-run it from spot-oa/ui/ dir.
> >
> > El sáb., 8 de abr. de 2017 a la(s) 12:19, Chokha Palayamkottai <
> > chokha@integralops.com> escribió:
> >
> > Hi Dimitris,
> >
> > Yes, I had the same issue. Unfortunately , I haven't spend a lot of time
> > on this since I have been busy with ingest. I was planning to use the
> > compiled .min.js files from the docker image and see if it helped.
> > Hopefully we can get some direction from the community.
> >
> > -Chokha.
> >
> > On 4/8/17 3:05 PM, Dimitris Papadopoulos wrote:
> > > Hi Chokha,
> > >
> > > It seems u were right, I can't find any .min.js inside the js/ dir.
> Mine
> > > looks like this:
> > >
> > > spotuser@master:~/spot-oa/ui/flow/js$ ls -l
> > > total 28
> > > drwxr-xr-x 2 root root 4096 Apr  4 10:40 components
> > > drwxr-xr-x 2 root root 4096 Apr  4 10:40 constants
> > > drwxr-xr-x 2 root root 4096 Apr  4 10:40 lib
> > > drwxr-xr-x 2 root root 4096 Apr  4 10:40 stores
> > > -rwxr-xr-x 1 root root 3229 Apr  4 10:40 storyboard.js
> > > -rwxr-xr-x 1 root root 3839 Apr  4 10:40 suspicious.js
> > > -rwxr-xr-x 1 root root 1719 Apr  4 10:40 threat-investigation.js
> > > spotuser@master:~/spot-oa/ui/flow/js$
> > >
> > > How did you fix this?
> > >
> > > Dimitris
> > >
> > > 2017-04-08 19:27 GMT+03:00 Chokha Palayamkottai <
> chokha@integralops.com
> > >:
> > >
> > >> I ran into this issue couple weeks back and I believe it had to do
> with
> > >> SPOT UI build process. It wasn't generating the minified js files.
> Your
> > >> issue could probably be different but please verify if your build
> > >> process generated the *.min,js files.
> > >> https://github.com/apache/incubator-spot/tree/master/spot-oa/ui
> > >>
> > >> -Chokha.
> > >>
> > >> On 4/8/17 12:08 PM, Dimitris Papadopoulos wrote:
> > >>> Hi Diego,
> > >>>
> > >>> Thx for the quick response.
> > >>>
> > >>> Yes, I'm running it from oa-spot/. I just re-pasted the output of 
ps
> > >> -ax |
> > >>> grep ipython at the end of this mail.
> > >>> Here are the screenshots (@Alan: thx for the info).
> > >>> Screenshot1: http://imgur.com/wR4g86M
> > >>> Screenshot2: http://imgur.com/MHA0sQQ
> > >>>
> > >>> The thing is that when I set up CDH on the 4 pseudo-nodes (master,
> > >>> s1,s2,s3), I realized that some of their assigned roles (I used the
> > >>> auto-assign option for the CDH roles)  didn't match the requirements
> > for
> > >>> each Spot node, as described in the documentation.
> > >>> Thus, I used only 3 nodes as described below:
> > >>>
> > >>> *pseudo-node name | Spot node name:*
> > >>> master      | MASTER1, MASTER2, OA
> > >>> s3             | EDGE
> > >>> s2             |WORKER
> > >>>
> > >>> I know that the above setup wasn't going to provide any real
> > >> functionality,
> > >>> but then again I was testing the steps before moving to a real
> cluster.
> > >>>
> > >>>
> > >>> spotuser@master:~/spot-oa$ ps -ax | grep ipython
> > >>> 5953 ?        Sl     1:36 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --
> > >>> cluster-id  --log-to-file --log-level=20
> > >>> 5962 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --
> > >>> cluster-id  --log-to-file --log-level=20
> > >>> 5963 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --
> > >>> cluster-id  --log-to-file --log-level=20
> > >>> 5966 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --
> > >>> cluster-id  --log-to-file --log-level=20
> > >>> 5969 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --
> > >>> cluster-id  --log-to-file --log-level=20
> > >>> 5974 ?        Sl     0:52 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --clus
> > >>> ter-id  --log-to-file --log-level=20
> > >>> 5976 ?        Sl     0:51 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --clus
> > >>> ter-id  --log-to-file --log-level=20
> > >>> 5981 ?        Sl     0:49 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --clus
> > >>> ter-id  --log-to-file --log-level=20
> > >>> 5998 ?        Sl     0:50 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_ia --clus
> > >>> ter-id  --log-to-file --log-level=20
> > >>> 10914 ?        S      0:00 /usr/bin/python /usr/local/bin/ipython
> > >> notebook
> > >>> --no-mathjax --profile=ia --port=8889 --ip=0.0.0.0
> > >>> --no-browser --NotebookApp.extra_static_paths=["ui/ipython/"]
> > >>> 12417 ?        S      0:00 /usr/bin/python /usr/local/bin/ipython
> > >> notebook
> > >>> --no-mathjax --profile=ia --port=8889 --ip=0.0.0.0
> > >>> --no-browser --NotebookApp.extra_static_paths=["ui/ipython/"]
> > >>> 19058 ?        Sl     1:34 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>> lt --cluster-id  --log-to-file --log-level=20
> > >>> 19066 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>> lt --cluster-id  --log-to-file --log-level=20
> > >>> 19067 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>> lt --cluster-id  --log-to-file --log-level=20
> > >>> 19070 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>> lt --cluster-id  --log-to-file --log-level=20
> > >>> 19074 ?        Sl     0:00 /usr/bin/python -m
> > IPython.parallel.controller
> > >>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>> lt --cluster-id  --log-to-file --log-level=20
> > >>> 19084 ?        Sl     0:52 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_default -
> > >>> -cluster-id  --log-to-file --log-level=20
> > >>> 19092 ?        Sl     0:51 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_default -
> > >>> -cluster-id  --log-to-file --log-level=20
> > >>> 19102 ?        Sl     0:49 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_default -
> > >>> -cluster-id  --log-to-file --log-level=20
> > >>> 19118 ?        Sl     0:49 /usr/bin/python -m IPython.parallel.engine
> > >>> --profile-dir /home/spotuser/.ipython/profile_default -
> > >>> -cluster-id  --log-to-file --log-level=20
> > >>> 26655 lxc/tty1 R+     0:00 grep --color=auto ipython
> > >>> 26719 ?        R    156:55 /usr/bin/python /usr/local/bin/ipython
> > >> notebook
> > >>> --no-mathjax --profile=ia --port=8889 --ip=0.0.0.0
> > >>> --no-browser --NotebookApp.extra_static_paths=["ui/ipython/"]
> > >>>
> > >>>
> > >>>
> > >>> 2017-04-08 18:03 GMT+03:00 Ross, Alan D <alan.d.ross@intel.com>:
> > >>>
> > >>>> No attachments here.  You can upload to imgur or somewhere else
and
> > then
> > >>>> post the link to the screenshot.
> > >>>>
> > >>>> -----Original Message-----
> > >>>> From: Diego (ChInO) [mailto:elchinillo@gmail.com]
> > >>>> Sent: Saturday, April 8, 2017 6:48 AM
> > >>>> To: dev@spot.incubator.apache.org
> > >>>> Subject: Re: Help on Spot installation (following Slack discussion
> > with
> > >>>> Nate)
> > >>>>
> > >>>> Hi,
> > >>>>
> > >>>> I just want to make sure you are running ipython from the right
> place.
> > >>>> Could you please confirm you are running it from spot-oa/ dir?
> > >>>>
> > >>>> Btw, I don't see any screenshot :p
> > >>>>
> > >>>> On Fri, Apr 7, 2017, 11:05 PM Dimitris Papadopoulos <
> > >>>> dpapadopoulos91@gmail.com> wrote:
> > >>>>
> > >>>>> It appears i hadnt added myself to the dev mailing list.
> > >>>>>
> > >>>>> Hi again,
> > >>>>>
> > >>>>> First things first, let me recap our discussion so far:
> > >>>>>
> > >>>>> -We are trying to install Spot on a server with pseudo-distributed
> > >> nodes.
> > >>>>> -Each one of the nodes is actually an *lxc,* while the server
runs
> on
> > >>>>> *Ubuntu 14.04*.
> > >>>>> -We started by installing CDH 10, following the cloudera site
> > >>>>> instructions and it seems to be working as intented.
> > >>>>> -We went on to install Spot, following the installation
> instructions
> > >>>>> as provided in the documentation webpage. Some parts (mainly
where
> > >>>>> .conf files are mentioned) seem to be a bit vague for us, so
we 've
> > >>>>> probably not configured the nodes right.
> > >>>>> -It seems that we haven't  managed to get Spot running (when
we
> enter
> > >>>>> the ".../files/ui/flow/suspicious.html." we get an unresponsive
> page
> > >>>>> [Screenshot1] and we would like to fix that asap.
> > >>>>> -I have submitted two screenshots, one of the suspicious tab
> > >>>>> [Screenshot1]  and one of the ".../tree" view which lets me
> navigate
> > >>>>> normally through the files [Screenshot2]. At the end of the
message
> > is
> > >>>>> the result from the ps -ax | grep ipython
> > >>>>>
> > >>>>> We are probably asking too much effort from your side, but
we could
> > >>>>> really benefit from a clean installation tutorial (video-blog-text
> > >>>>> format) that install all dependencies and sets all the
> configuration
> > >>>>> values for each one of the nodes. We could ofc provide a server
for
> > >>>>> this purpose. Dempnstrating a Spot installation in a
> > >>>>> pseudo-distributed configuration could help us set it up on
a large
> > >>>> distributed-computing infrastructure.
> > >>>>> Thank you so much for your time,
> > >>>>> Dimitris
> > >>>>>
> > >>>>> -------------------------------------------------------------------
> > >>>>> spotuser@master:~$ ps -ax | grep ipython
> > >>>>> 5953 ?        Sl     0:41 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia -- cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5962 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia -- cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5963 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia -- cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5966 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia -- cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5969 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia -- cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5974 ?        Sl     0:22 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia --clus ter-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5976 ?        Sl     0:21 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia --clus ter-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5981 ?        Sl     0:20 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia --clus ter-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 5998 ?        Sl     0:21 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_ia --clus ter-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 10914 ?        S      0:00 /usr/bin/python /usr/local/bin/ipython
> > >>>>> notebook --no-mathjax --profile=ia --port=8889 --ip=0.0.0.0
> > >>>>> --no-browser --NotebookApp.extra_static_paths=["ui/ipython/"]
> > >>>>> 12417 ?        S      0:00 /usr/bin/python /usr/local/bin/ipython
> > >>>>> notebook --no-mathjax --profile=ia --port=8889 --ip=0.0.0.0
> > >>>>> --no-browser --NotebookApp.extra_static_paths=["ui/ipython/"]
> > >>>>> 19058 ?        Sl     0:38 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>>>> lt --cluster-id  --log-to-file --log-level=20
> > >>>>> 19066 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>>>> lt --cluster-id  --log-to-file --log-level=20
> > >>>>> 19067 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>>>> lt --cluster-id  --log-to-file --log-level=20
> > >>>>> 19070 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>>>> lt --cluster-id  --log-to-file --log-level=20
> > >>>>> 19074 ?        Sl     0:00 /usr/bin/python -m
> > >> IPython.parallel.controller
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_defau
> > >>>>> lt --cluster-id  --log-to-file --log-level=20
> > >>>>> 19084 ?        Sl     0:21 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_default - -cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 19092 ?        Sl     0:21 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_default - -cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 19102 ?        Sl     0:20 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_default - -cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 19118 ?        Sl     0:20 /usr/bin/python -m
> IPython.parallel.engine
> > >>>>> --profile-dir /home/spotuser/.ipython/profile_default - -cluster-id
> > >>>>> --log-to-file --log-level=20
> > >>>>> 23679 lxc/tty1 S+     0:00 grep --color=auto ipython
> > >>>>> 26719 ?        S     65:15 /usr/bin/python /usr/local/bin/ipython
> > >>>>> notebook --no-mathjax --profile=ia --port=8889 --ip=0.0.0.0
> > >>>>> --no-browser --NotebookApp.extra_static_paths=["ui/ipython/"]
> > >>>>> spotuser@master:~$
> > >>>>>
> > >>>>>
> > >>>>>
> > >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message