Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scripts/test.sh: line 103: third_party/node-0.10.1/bin/npm: Permission denied #32

Closed
GoogleCodeExporter opened this issue Aug 14, 2015 · 7 comments

Comments

@GoogleCodeExporter
Copy link

While Installing oppia I have the following error
scripts/test.sh: line 103: third_party/node-0.10.1/bin/npm: Permission denied
I followed the exact same procedure but instead of getting my localhost started 
I am getting the above error. 


What version of the product are you using? On what operating system?
I am using npm version 1.4.1 and downloaded the latest oppia code from git. 
Ubuntu 12.04 LTS



Original issue reported on code.google.com by maithani...@gmail.com on 14 Aug 2013 at 4:00

Attachments:

@GoogleCodeExporter
Copy link
Author

Very puzzling. I've touched start.sh recently and that might have changed 
something. Does running test.sh directly causes the same problem (just so we 
can tell what broke it).

We should be using the version of node and npm that's installed in third_party. 
Node is 0.10.1 and my installation says npm is 1.2.15. Your output says you are 
using node 0.6.12 and npm 1.1.4, so that explains why its failing, but I can't 
tell why it's not using the node / npm from third_party.

A quick thing you can try is wipe out third_party directory and retry. Also 
third_party/node-0.10.1/bin/npm is a soft link, so you might want to check the 
permission of the link target too.

Original comment by kash...@google.com on 14 Aug 2013 at 4:29

@GoogleCodeExporter
Copy link
Author

tried but no result, I removed the third_party directory, again run the 
start.sh command, and also changed the permission using chmod +x 
third_party/node-0.10.1/bin/npm but nothing worked, while using chmod +x 
third_party/node-0.10.1/bin/npm there was no output. 
P.S I am newbie, anything else I need to try

Original comment by maithani...@gmail.com on 14 Aug 2013 at 4:54

@GoogleCodeExporter
Copy link
Author

Thanks for trying and reporting back.

One more quick thing you can try. Looks like you are finding your local 
installation of node (and possibly npm) instead of the ones in third_party. 
This might help to force it to use the one in third_party:

PATH=`pwd`/third_party/node-0.10.1/bin:$PATH; sh scripts/test.sh

Another way to try this -- you can edit scripts/start.sh and comment out this 
line:

sh scripts/test.sh

by inserting "#" to the beginning of the line as 

#sh scripts/test.sh

and run it as

sh scripts/start.sh


Original comment by kash...@google.com on 14 Aug 2013 at 6:58

@GoogleCodeExporter
Copy link
Author

OP: Did any of these fixes work for you? I noticed from the OpenHatch IRC logs 
that you got this issue resolved. We would be interested to know the 
resolution, so that we can try and ensure that this does not happen for other 
users.

Original comment by s...@seanlip.org on 15 Aug 2013 at 4:51

@GoogleCodeExporter
Copy link
Author

All I did, I re-installed the same in my home directory of ubuntu. That's it 

Original comment by maithani...@gmail.com on 15 Aug 2013 at 5:19

@GoogleCodeExporter
Copy link
Author

Thanks; marking as resolved.

One question of clarification: by 'the same', do you mean that you reinstalled 
the updated version of node in your home directory (so you are still using your 
local installation of node instead of the one in third_party, but the local 
installation is in a different place)?

Original comment by s...@google.com on 15 Aug 2013 at 5:46

  • Changed state: WontFix

@GoogleCodeExporter
Copy link
Author

I actually cloned the oppia into my home directory, then run the start 
scripts.sh command and voila! All hail good lord :D it worked. That's all

Original comment by maithani...@gmail.com on 17 Aug 2013 at 2:51

lkbhitesh07 pushed a commit that referenced this issue Apr 4, 2024
* Add emulator mode

* Fix backend tests

* Fix backend tests

* Fix backend tests

* Fix backend tests

* Add docstirngs

* Fix formatting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant