From Brian.Chapman at utah.edu Tue Aug 11 15:55:36 2015 From: Brian.Chapman at utah.edu (Brian E Chapman) Date: Tue, 11 Aug 2015 19:55:36 +0000 Subject: [Girder-users] Girder Vagrant box fails to build on NPM Message-ID: Hi, I just forked and cloned the Girder repository on github. When I try to bring up the Girder vagrantbox, it fails on the NPM install: TASK: [run npm install] ******************************************************* <127.0.0.1> ESTABLISH CONNECTION FOR USER: vagrant <127.0.0.1> REMOTE_MODULE npm path=/vagrant <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o Port=2222 -o IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && echo $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347' <127.0.0.1> PUT /var/folders/bn/hc7234pd2cd0gxz98dn0zq_40000gn/T/tmpyO2q46 TO /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o Port=2222 -o IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 /bin/sh -c 'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm; rm -rf /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/ >/dev/null 2>&1' failed: [default] => {"cmd": "/usr/bin/npm install", "failed": true, "rc": 1} stderr: npm ERR! girder at 1.3.1 postinstall: `grunt init && grunt` npm ERR! Exit status 3 npm ERR! npm ERR! Failed at the girder at 1.3.1 postinstall script. npm ERR! This is most likely a problem with the girder package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! grunt init && grunt npm ERR! You can get their info via: npm ERR! npm owner ls girder npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.13.0-55-generic npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! cwd /vagrant npm ERR! node -v v0.10.37 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /vagrant/npm-debug.log npm ERR! not ok code 0 Wondering if others have been able to work through this. Brian ? Brian E. Chapman, Ph.D. Associate Professor Department of Radiology University of Utah -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brian.Chapman at utah.edu Tue Aug 11 16:22:52 2015 From: Brian.Chapman at utah.edu (Brian E Chapman) Date: Tue, 11 Aug 2015 20:22:52 +0000 Subject: [Girder-users] Girder Vagrant box fails to build on NPM In-Reply-To: References: Message-ID: As a follow-up to my previous e-mail, if I ssh to the vagrant machine and manually complete the steps in the playbook.yml file everything seems to install and I?m able to run Girder. Don?t know what this implies as far as the source of the error, but that it seemed useful to know. Brian From: Brian Chapman > Date: Tuesday, August 11, 2015 at 1:55 PM To: "girder-users at public.kitware.com" > Subject: Girder Vagrant box fails to build on NPM Hi, I just forked and cloned the Girder repository on github. When I try to bring up the Girder vagrantbox, it fails on the NPM install: TASK: [run npm install] ******************************************************* <127.0.0.1> ESTABLISH CONNECTION FOR USER: vagrant <127.0.0.1> REMOTE_MODULE npm path=/vagrant <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o Port=2222 -o IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && echo $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347' <127.0.0.1> PUT /var/folders/bn/hc7234pd2cd0gxz98dn0zq_40000gn/T/tmpyO2q46 TO /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o Port=2222 -o IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 /bin/sh -c 'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm; rm -rf /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/ >/dev/null 2>&1' failed: [default] => {"cmd": "/usr/bin/npm install", "failed": true, "rc": 1} stderr: npm ERR! girder at 1.3.1 postinstall: `grunt init && grunt` npm ERR! Exit status 3 npm ERR! npm ERR! Failed at the girder at 1.3.1 postinstall script. npm ERR! This is most likely a problem with the girder package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! grunt init && grunt npm ERR! You can get their info via: npm ERR! npm owner ls girder npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.13.0-55-generic npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! cwd /vagrant npm ERR! node -v v0.10.37 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /vagrant/npm-debug.log npm ERR! not ok code 0 Wondering if others have been able to work through this. Brian ? Brian E. Chapman, Ph.D. Associate Professor Department of Radiology University of Utah -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick.reynolds at kitware.com Tue Aug 11 16:32:24 2015 From: patrick.reynolds at kitware.com (Patrick Reynolds) Date: Tue, 11 Aug 2015 16:32:24 -0400 Subject: [Girder-users] Girder Vagrant box fails to build on NPM In-Reply-To: References: Message-ID: Hi Brian, Thanks for the report, and I'm glad you were able to get your Vagrant Box up and running. Could you open a bug on the issue tracker so that you can follow our progress in fixing it (https://github.com/girder/girder/issues/new)? Thanks, Patrick Reynolds Technical Leader Kitware, Inc. 919 869 8848 On Tue, Aug 11, 2015 at 4:22 PM, Brian E Chapman wrote: > As a follow-up to my previous e-mail, if I ssh to the vagrant machine and > manually complete the steps in the playbook.yml file everything seems to > install and I?m able to run Girder. Don?t know what this implies as far as > the source of the error, but that it seemed useful to know. > > Brian > > > From: Brian Chapman > Date: Tuesday, August 11, 2015 at 1:55 PM > To: "girder-users at public.kitware.com" > Subject: Girder Vagrant box fails to build on NPM > > Hi, > > I just forked and cloned the Girder repository on github. When I try to > bring up the Girder vagrantbox, it fails on the NPM install: > > TASK: [run npm install] > ******************************************************* > <127.0.0.1> ESTABLISH CONNECTION FOR USER: vagrant > <127.0.0.1> REMOTE_MODULE npm path=/vagrant > <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o > ControlMaster=auto -o ControlPersist=60s -o > ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o > StrictHostKeyChecking=no -o Port=2222 -o > IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" > -o KbdInteractiveAuthentication=no -o > PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey > -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 > /bin/sh -c 'mkdir -p > $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && chmod a+rx > $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && echo > $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347' > <127.0.0.1> PUT /var/folders/bn/hc7234pd2cd0gxz98dn0zq_40000gn/T/tmpyO2q46 > TO /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm > <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o > ControlMaster=auto -o ControlPersist=60s -o > ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o > StrictHostKeyChecking=no -o Port=2222 -o > IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" > -o KbdInteractiveAuthentication=no -o > PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey > -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 > /bin/sh -c 'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python > /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm; > rm -rf > /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/ > >/dev/null 2>&1' > failed: [default] => {"cmd": "/usr/bin/npm install", "failed": true, "rc": > 1} > stderr: > npm ERR! girder at 1.3.1 postinstall: `grunt init && grunt` > npm ERR! Exit status 3 > npm ERR! > npm ERR! Failed at the girder at 1.3.1 postinstall script. > npm ERR! This is most likely a problem with the girder package, > npm ERR! not with npm itself. > npm ERR! Tell the author that this fails on your system: > npm ERR! grunt init && grunt > npm ERR! You can get their info via: > npm ERR! npm owner ls girder > npm ERR! There is likely additional logging output above. > npm ERR! System Linux 3.13.0-55-generic > npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" > npm ERR! cwd /vagrant > npm ERR! node -v v0.10.37 > npm ERR! npm -v 1.4.28 > npm ERR! code ELIFECYCLE > npm ERR! > npm ERR! Additional logging details can be found in: > npm ERR! /vagrant/npm-debug.log > npm ERR! not ok code 0 > > Wondering if others have been able to work through this. > > Brian > ? > Brian E. Chapman, Ph.D. > Associate Professor > Department of Radiology > University of Utah > > > _______________________________________________ > Girder-users mailing list > Girder-users at public.kitware.com > http://public.kitware.com/mailman/listinfo/girder-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Brian.Chapman at utah.edu Tue Aug 11 16:33:46 2015 From: Brian.Chapman at utah.edu (Brian E Chapman) Date: Tue, 11 Aug 2015 20:33:46 +0000 Subject: [Girder-users] Girder Vagrant box fails to build on NPM In-Reply-To: References: Message-ID: Sure. Brian From: Patrick Reynolds > Date: Tuesday, August 11, 2015 at 2:32 PM To: Brian Chapman > Cc: "girder-users at public.kitware.com" > Subject: Re: [Girder-users] Girder Vagrant box fails to build on NPM Hi Brian, Thanks for the report, and I'm glad you were able to get your Vagrant Box up and running. Could you open a bug on the issue tracker so that you can follow our progress in fixing it (https://github.com/girder/girder/issues/new)? Thanks, Patrick Reynolds Technical Leader Kitware, Inc. 919 869 8848 On Tue, Aug 11, 2015 at 4:22 PM, Brian E Chapman > wrote: As a follow-up to my previous e-mail, if I ssh to the vagrant machine and manually complete the steps in the playbook.yml file everything seems to install and I?m able to run Girder. Don?t know what this implies as far as the source of the error, but that it seemed useful to know. Brian From: Brian Chapman > Date: Tuesday, August 11, 2015 at 1:55 PM To: "girder-users at public.kitware.com" > Subject: Girder Vagrant box fails to build on NPM Hi, I just forked and cloned the Girder repository on github. When I try to bring up the Girder vagrantbox, it fails on the NPM install: TASK: [run npm install] ******************************************************* <127.0.0.1> ESTABLISH CONNECTION FOR USER: vagrant <127.0.0.1> REMOTE_MODULE npm path=/vagrant <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o Port=2222 -o IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 /bin/sh -c 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && chmod a+rx $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347 && echo $HOME/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347' <127.0.0.1> PUT /var/folders/bn/hc7234pd2cd0gxz98dn0zq_40000gn/T/tmpyO2q46 TO /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm <127.0.0.1> EXEC ssh -C -tt -vvv -o UserKnownHostsFile=/dev/null -o ControlMaster=auto -o ControlPersist=60s -o ControlPath="/Users/brian/.ansible/cp/ansible-ssh-%h-%p-%r" -o StrictHostKeyChecking=no -o Port=2222 -o IdentityFile="/Users/brian/Code/girder/.vagrant/machines/default/virtualbox/private_key" -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=vagrant -o ConnectTimeout=10 127.0.0.1 /bin/sh -c 'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/npm; rm -rf /home/vagrant/.ansible/tmp/ansible-tmp-1439320042.19-167413397287347/ >/dev/null 2>&1' failed: [default] => {"cmd": "/usr/bin/npm install", "failed": true, "rc": 1} stderr: npm ERR! girder at 1.3.1 postinstall: `grunt init && grunt` npm ERR! Exit status 3 npm ERR! npm ERR! Failed at the girder at 1.3.1 postinstall script. npm ERR! This is most likely a problem with the girder package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! grunt init && grunt npm ERR! You can get their info via: npm ERR! npm owner ls girder npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.13.0-55-generic npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! cwd /vagrant npm ERR! node -v v0.10.37 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /vagrant/npm-debug.log npm ERR! not ok code 0 Wondering if others have been able to work through this. Brian ? Brian E. Chapman, Ph.D. Associate Professor Department of Radiology University of Utah _______________________________________________ Girder-users mailing list Girder-users at public.kitware.com http://public.kitware.com/mailman/listinfo/girder-users -------------- next part -------------- An HTML attachment was scrubbed... URL: