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

oarsh issue #7

Open
nikosT opened this issue Apr 8, 2022 · 2 comments
Open

oarsh issue #7

nikosT opened this issue Apr 8, 2022 · 2 comments

Comments

@nikosT
Copy link
Contributor

nikosT commented Apr 8, 2022

I'm running the oar-docker-compose "cluster". After logging via CLI to frontend I submitted successfully an interactive job:

user1@frontend:/$ oarsub -I -l nodes=2
# INFO:  Moldable instance:  1  Estimated nb resources:  2  Walltime:  3600
OAR_JOB_ID= 2
Interactive mode: waiting...
Starting...
Connect to OAR job 2 via the node node1
user1@node1:~$  

Without closing this CLI, on another CLI, I logged in to the frontend again, then I checked that job is running, however, I get no access to any of the node1 and node2 machines via oarsh (and by setting the OAR_JOB_ID env. var.),

user1@frontend:/$ oarstat -f
Job id    S User     Duration          System message
--------- - -------- ----------------- ------------------------------------------------
2         R user1       0:05:22 R=2,J=I,Q=default                               
user1@frontend:/$ OAR_JOB_ID=2 oarsh node1
oarsh: Permission denied, seems like job 2 is not yours.

If I run oarsh inside any of the reserved nodes, then I get access, but not through the frontend. Additionally, the job as shown above belongs to the same user user1.

NODE List is shown below:

user1@node1:~$ cat $OAR_NODEFILE 
node1
node2
@adfaure
Copy link
Contributor

adfaure commented Apr 8, 2022

Hello,

I can reproduce the error. I will look at it, in the meantime you can use oarsub -C <jobid> to connect to the job.

@nikosT
Copy link
Contributor Author

nikosT commented Apr 8, 2022

Yes, I did and it works. I think the issue has to do with the fact that the way the oar-docker-compose is implemented, the containers do no share the same "file system". So, if a file is created in /home/user1 then it is visible only from the "machine" it was created and NOT all the containers.

nikosT added a commit to nikosT/oar3 that referenced this issue Apr 8, 2024
New allocation policies introduced
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

2 participants