Re: [slurm-users] "command not found"

2017-12-15 Thread John Hearns
David, the common practice is to install blast, or any other application software packages, on a drive which is to be exported via NFS to the compute nodes. Or indeed a section on your parallel filesystem (BeeGFS, GPFS, Lustre etc.) You might call such an area /opt//opt/shared or /cm/shared (At

Re: [slurm-users] "command not found"

2017-12-15 Thread david vilanova
Thanks manuel, The shared folder between master and slave sounds like a good option. I’ll go and try that one, Thanks El El vie, 15 dic 2017 a las 12:36, Manuel Rodríguez Pascual < manuel.rodriguez.pasc...@gmail.com> escribió: > Hi David, > > The command to be executed must be present on the node

Re: [slurm-users] "command not found"

2017-12-15 Thread Manuel Rodríguez Pascual
Hi David, The command to be executed must be present on the node where the script is run. When you submit a job in Slurm only the script is copied to the slave node, so the data and binaries must be there prior to the script execution. The are many alternatives to deal with this situation depend

[slurm-users] "command not found"

2017-12-15 Thread david
Hi, when running a sbatch script i get "command not found". The command is blast (quite used bioinformatics tool). The problem comes from the fact that the blast binary is installed in the master node  but not on the other nodes. When the job runs on another node the binary is not found.