bigjob bootstrap fails on india

[marksantcroos]

bigjob bootstrap fails on india

[andre-merzky]

FWIW, Matteo sees the same.

[marksantcroos]

After the fix I get the following error in the agent log:

Python version 2.7 loaded
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

[Errno 13] Permission denied: '/N/soft/python/2.7/lib/python2.7/site-packages/test-easy-install-19556.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/N/soft/python/2.7/lib/python2.7/site-packages/

Perhaps your account does not have write access to this directory? If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account. If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

For information on other options, you may wish to consult the
documentation at:

http://peak.telecommunity.com/EasyInstall.html

Please make the appropriate changes for your system and try again.

Traceback (most recent call last):
File "", line 59, in
NameError: name 'bigjob' is not defined

[marksantcroos]

I can work around this one by setting
"source $HOME/.bigjob/python/bin/activate"
in my .bashrc, but that’s probably not what we want.

On 25 Jan 2014, at 23:51 , Mark Santcroos [email protected] wrote:

After the fix I get the following error in the agent log:

Python version 2.7 loaded
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

[Errno 13] Permission denied: '/N/soft/python/2.7/lib/python2.7/site-packages/test-easy-install-19556.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

/N/soft/python/2.7/lib/python2.7/site-packages/

Perhaps your account does not have write access to this directory? If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account. If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

For information on other options, you may wish to consult the
documentation at:

http://peak.telecommunity.com/EasyInstall.html

Please make the appropriate changes for your system and try again.

Traceback (most recent call last):
File "", line 59, in
NameError: name 'bigjob' is not defined

[anjaniragothaman]

I'm seeing an issue:

[ethread@ip-10-9-147-80 ~]$ cat stderr-bj-7afcbd94-86c5-11e3-9c59-080027261dbf-agent.txt
Traceback (most recent call last):
File "/home/ethread/.bigjob/bigjob-bootstrap.py", line 2337, in
ret = subprocess.call(["virtualenv", "--version"])
File "/usr/lib64/python2.6/subprocess.py", line 478, in call
p = Popen(_popenargs, *_kwargs)
File "/usr/lib64/python2.6/subprocess.py", line 642, in init
errread, errwrite)
File "/usr/lib64/python2.6/subprocess.py", line 1234, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
Traceback (most recent call last):
File "/home/ethread/.bigjob/bigjob-bootstrap.py", line 2337, in
ret = subprocess.call(["virtualenv", "--version"])
File "/usr/lib64/python2.6/subprocess.py", line 478, in call
p = Popen(_popenargs, *_kwargs)
File "/usr/lib64/python2.6/subprocess.py", line 642, in init
errread, errwrite)
File "/usr/lib64/python2.6/subprocess.py", line 1234, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
Traceback (most recent call last):
File "", line 45, in
IOError: [Errno 2] No such file or directory: '/home/ethread/.bigjob/python/bin/activate_this.py'

Do I need to reinstall BJ to avoid this issue? Currently I'm running version 0.53

[anjaniragothaman]

Hi Mark,

I got it resolved with AndreL's help yesterday. I was following it up on
the "[bigjob-devel] issue 169 installation failure" mail thread started by
you!

Thanks
Anjani

On 27 January 2014 16:55, Mark Santcroos [email protected] wrote:

Reopened #169 #169.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/169
.

Thanks and Regards,
Anjani Bhargavi.R
If u have the willpower to do things nothing will be against u.

[marksantcroos]

Hi,

I’m reopening because of the env variable.

Gr,

Mark

On 27 Jan 2014, at 17:04 , anjaniragothaman [email protected] wrote:

Hi Mark,

I got it resolved with AndreL's help yesterday. I was following it up on
the "[bigjob-devel] issue 169 installation failure" mail thread started by
you!

Thanks
Anjani

On 27 January 2014 16:55, Mark Santcroos [email protected] wrote:

Reopened #169 #169.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/169
.

Thanks and Regards,
Anjani Bhargavi.R
If u have the willpower to do things nothing will be against u.
—
Reply to this email directly or view it on GitHub.

[anjaniragothaman]

Oh OK.

Thanks
Anjani

On 27 January 2014 17:05, Mark Santcroos [email protected] wrote:

Hi,

I’m reopening because of the env variable.

Gr,

Mark

On 27 Jan 2014, at 17:04 , anjaniragothaman [email protected]
wrote:

Hi Mark,

I got it resolved with AndreL's help yesterday. I was following it up on
the "[bigjob-devel] issue 169 installation failure" mail thread started
by
you!

Thanks
Anjani

On 27 January 2014 16:55, Mark Santcroos [email protected]
wrote:

Reopened #169 #169.

—
Reply to this email directly or view it on GitHub<
https://github.com/saga-project/BigJob/issues/169>
.

Thanks and Regards,
Anjani Bhargavi.R
If u have the willpower to do things nothing will be against u.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/169#issuecomment-33428668
.

Thanks and Regards,
Anjani Bhargavi.R
If u have the willpower to do things nothing will be against u.

[andre-merzky]

re Mark:

I can work around this one by setting
"source $HOME/.bigjob/python/bin/activate"
in my .bashrc, but that’s probably not what we want.

I used to do that, for other reasons, but in that case both bigjob and sinon agents can't run any tasks anymore (they then complain about an ssh key error, of all things). So that is indeed not a viable option...