You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
I'm running the oar-docker-compose "cluster". After logging via CLI to frontend I submitted successfully an interactive job:
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
andnode2
machines viaoarsh
(and by setting theOAR_JOB_ID
env. var.),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 useruser1
.NODE List is shown below:
The text was updated successfully, but these errors were encountered: