# PBS Pro passwordless configuration **URL:** \ **Category:** Users/Site Administrators\ **Created:** [November 8, 2018, 1:05pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286 "2018-11-08T13:05:41Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![liuxiaopiao](https://avatars.discourse-cdn.com/v4/letter/l/65b543/32.png) [@liuxiaopiao](https://community.openpbs.org/u/liuxiaopiao)\ **Post date:** [November 8, 2018, 1:05pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/1 "2018-11-08T13:05:41Z")
I have one PBS Pro cluster which has three vms: VM1: installed PBS pro server and start pbs service using user root. And has another user “test” which has the sudo permission. VM2: installed PBS pro execution package and start pbs service using user root. And has another user “test” which has the sudo permission. VM3: installed PBS pro client package using user root. And has another user “test” which has the sudo permission. Then I performed the below configuraitons: 1. VM1’s user root can passwordless access VM2 by “ssh root@VM2”. 2. VM2’s user root can passwordless access VM1 by “ssh root@VM1”. 3. VM1’s user root can passwordless access VM3 by “ssh test@VM3”. 4. VM2’s user root can passwordless access VM3 by “ssh test@VM3”. 5. VM3’s user test can passwordless access VM1 by “ssh root@VM1”. 6. VM3’s user test can passwordless access VM1 by “ssh root@VM2”. When I run " echo “sleep 60” | qsub " on VM3, the job couldn’t execute and mom logs looked like:’ > 11/08/2018 06:07:00;0080;pbs\_mom;Fil;sys\_copy;command: /bin/scp -Brvp /var/spool/pbs/spool/13.pbstest1.OU test@pbsproclientserver:/home/STDIN.o13 status=1, try=1 > 11/08/2018 06:07:31;0080;pbs\_mom;Fil;sys\_copy;command: /opt/pbs/sbin/pbs\_rcp -rp /var/spool/pbs/spool/13.pbstest1.OU test@pbsproclientserver:/home/STDIN.o13 status=1, try=2 > 11/08/2018 06:07:42;0080;pbs\_mom;Fil;sys\_copy;command: /bin/scp -Brvp /var/spool/pbs/spool/13.pbstest1.OU test@pbsproclientserver:/home/STDIN.o13 status=1, try=3 > 11/08/2018 06:08:13;0080;pbs\_mom;Fil;sys\_copy;command: /opt/pbs/sbin/pbs\_rcp -rp /var/spool/pbs/spool/13.pbstest1.OU test@pbsproclientserver:/home/STDIN.o13 status=1, try=4 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;Unable to copy file /var/spool/pbs/spool/13.pbstest1.OU to pbsproclientserver:/home/STDIN.o13 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;pbsproclientserver: Connection refused > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;[in.oraclevcn.com](http://in.oraclevcn.com), user test, command scp -v -r -p -t /home/STDIN.o13 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;OpenSSH\_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Reading configuration data /etc/ssh/ssh\_config > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: /etc/ssh/ssh\_config line 58: Applying options for \* > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Connecting to pbsproclientserver [10.0.0.15] port 22. > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Connection established. > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_type: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_cert: Permission denied > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_cert: Permission denied > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_cert: Permission denied > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_cert: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_type: Permission denied > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_type: Permission denied > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_type: Permission denied > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_private\_type: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_cert: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_cert: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_cert: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_cert: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_rsa type 1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_rsa-cert type -1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_dsa type -1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_dsa-cert type -1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_ecdsa type -1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_ecdsa-cert type -1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_ed25519 type -1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: key\_load\_public: No such file or directory > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: identity file /home/test/.ssh/id\_ed25519-cert type -1 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Enabling compatibility mode for protocol 2.0 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Local version string SSH-2.0-OpenSSH\_7.4 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Remote protocol version 2.0, remote software version OpenSSH\_7.4 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: match: OpenSSH\_7.4 pat OpenSSH\* compat 0x04000000 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Authenticating to pbsproclientserver:22 as ‘test’ > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: SSH2\_MSG\_KEXINIT sent > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: SSH2\_MSG\_KEXINIT received > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: kex: algorithm: curve25519-sha256 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: kex: host key algorithm: ecdsa-sha2-nistp256 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: kex: server-\>client cipher: [chacha20-poly1305@openssh.com](mailto:chacha20-poly1305@openssh.com) MAC: compression: none > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: kex: client-\>server cipher: [chacha20-poly1305@openssh.com](mailto:chacha20-poly1305@openssh.com) MAC: compression: none > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: kex: curve25519-sha256 need=64 dh\_need=64 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: kex: curve25519-sha256 need=64 dh\_need=64 > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: expecting SSH2\_MSG\_KEX\_ECDH\_REPLY > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;debug1: Server host key: ecdsa-sha2-nistp256 SHA256:2U4Z1gS93Kdl8uaEhp2tY95Np9IsSQgcknRtoglGigs > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;Host key verification failed. > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;lost connection But I could run the below command on VM2(Mom host) successfully: > /bin/scp -Brvp /var/spool/pbs/spool/13.pbstest1.OU test@pbsproclientserver:/home/STDIN.o13 So my question is that: 1. how to figure out the above error? 2. Which kind of passwordless configuration I need to configure? Thanks a lot for the help! ---
**Author:** ![mkaro](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/mkaro/32/85_2.png) [@mkaro](https://community.openpbs.org/u/mkaro)\ **Post date:** [November 8, 2018, 7:27pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/2 "2018-11-08T19:27:16Z")
Hello @liuxiaopiao, Thanks for posting your question! First off, you shouldn’t need passwordless access as root between any of your VMs. You will need it for the test user. The first message that needs investigation is this: > [@liuxiaopiao](#): > > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;pbsproclientserver: Connection refused Try using scp to copy a file from the execution host to the system from which you submitted the job. Use the -v option on scp if you need verbose output to help debug any issues. The other message that seems out of place is: > [@liuxiaopiao](#): > > 11/08/2018 06:08:34;0004;pbs\_mom;Fil;13.pbstest1.OU;Host key verification failed. This message is actually coming from scp, and it indicates a problem with authentication between the two systems involved. Make sure you don’t have any firewalls blocking packets between the systems. Do so with caution, of course, and make sure you only open the ports you need unless you are on a totally secure network. I don’t think you have any issues with name resolution or your execution host setup, because the job apparently ran. That’s another common problem we see. Thanks, Mike ---
**Author:** ![liuxiaopiao](https://avatars.discourse-cdn.com/v4/letter/l/65b543/32.png) [@liuxiaopiao](https://community.openpbs.org/u/liuxiaopiao)\ **Post date:** [November 9, 2018, 12:41am UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/3 "2018-11-09T00:41:45Z")
Hi Mike, Thanks so much for your reply. So the passwordless need to be configured in the three VMs and under user “test”. If the user “test” can passwordless ssh to any other VMs, the workflow should be working as design. Is this correct? So can I get one conclusion that the PBS pro cluster needs to have the same user on all the VMs in this cluster? Thanks a lot! ---
**Author:** ![mkaro](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/mkaro/32/85_2.png) [@mkaro](https://community.openpbs.org/u/mkaro)\ **Post date:** [November 9, 2018, 12:52am UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/4 "2018-11-09T00:52:03Z")
That’s the correct conclusion. However there was one thing I forgot to mention before… now that your test account is configured properly, you want to run the following qmgr command: set server flatuid = True That tells PBS that the same accounts exist across your cluster. Please do let us know if that fixes your problem. Thanks, Mike ---
**Author:** ![liuxiaopiao](https://avatars.discourse-cdn.com/v4/letter/l/65b543/32.png) [@liuxiaopiao](https://community.openpbs.org/u/liuxiaopiao)\ **Post date:** [November 9, 2018, 1:07am UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/5 "2018-11-09T01:07:12Z")
Thanks Mike so much. I will follow your guide and try it again. And another question to bother you is that: so how to communicate between server and execution nodes? The communication depends on the passwordless ssh? It seemed not secure enough? Could you please help me understand this when you have bandwidth? Thanks a lot! ---
**Author:** ![mkaro](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/mkaro/32/85_2.png) [@mkaro](https://community.openpbs.org/u/mkaro)\ **Post date:** [November 9, 2018, 5:14pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/6 "2018-11-09T17:14:47Z")
Hello @liuxiaopiao, PBS Pro uses external tools (i.e. rcp or scp) to handle file transfers. Communication between PBS Pro components utilizes sockets directly, so there is no need to configure ssh keys for this purpose. For example, during job launch… - The server contacts the scheduler to begin a scheduling cycle - The scheduler responds to the server with the job IDs to run and the nodes assigned - The server contacts the MoM on the first node assigned to a job (we call mother superior) and sends it the data it needs including the full node list, the job script, etc. - Mother superior contacts the other nodes assigned to the job (the sisterhood) and relays the job information - The job begins execution on mother superior It is only after the job exits that mother superior will invoke scp as the user to copy output back to the node from which the job was submitted. The user can tell PBS not to transfer the output files (keep them on the execution host) by specifying the -k parameter to qsub. Thanks, Mike ---
**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\ **Post date:** [November 9, 2018, 8:06pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/7 "2018-11-09T20:06:11Z")
+1 @mkaro @liuxiaopiao 1. Please configure hostbased passwordless-ssh configuration, as user key based would have issues, if keys are deleted accidentally Ref: [https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Host-based\_Authentication](https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Host-based_Authentication) 2. Please add the below lines to your /etc/pbs.conf file PBS\_RCP=/bin/false #so that rcp communication is not used PBS\_SCP=/usr/bin/scp PBS\_RSHCOMMAND=/usr/bin/ssh [after adding these , restart the pbs services] 1. Please make sure the hostname resolution is correct (forward and reverse) nslookup hostname nslookup ipaddress ---
**Author:** ![liuxiaopiao](https://avatars.discourse-cdn.com/v4/letter/l/65b543/32.png) [@liuxiaopiao](https://community.openpbs.org/u/liuxiaopiao)\ **Post date:** [November 10, 2018, 12:34am UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/8 "2018-11-10T00:34:25Z")
Thanks you both so much for the detailed info. @mkaro @adarsh So this is my understanding for pbs pro: 1. passwordless-ssh(recommendation is hostbased) is used only when mother superior invokes scp as the user to copy output back to the node from which the job was submitted. If the set server flatuid as True, we need to make sure: 2. if we don’t want to let mother superior do scp/rcp to copy output back, actually we don’t need to configure any passwordless-ssh between any mother superior and any client server which jobs were submitted. Could you please help check if my understanding is correct or not? Thanks a lot! ---
**Author:** ![mkaro](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/mkaro/32/85_2.png) [@mkaro](https://community.openpbs.org/u/mkaro)\ **Post date:** [November 10, 2018, 8:54pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/9 "2018-11-10T20:54:21Z")
That sounds correct to me. If you have shared filesystems, you may also want to employ the $usecp configuration parameter for MoM. Please refer to section 15.7 of the PBS Pro 18.2 administrator’s guide. It covers the material discussed in this thread. You may download it here: [https://www.pbsworks.com/SupportGT.aspx?d=PBS-Professional,-Documentation](https://www.pbsworks.com/SupportGT.aspx?d=PBS-Professional,-Documentation) EDIT: Also see section 8.9 of the admin guide ---
**Author:** ![liuxiaopiao](https://avatars.discourse-cdn.com/v4/letter/l/65b543/32.png) [@liuxiaopiao](https://community.openpbs.org/u/liuxiaopiao)\ **Post date:** [November 11, 2018, 7:41am UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/10 "2018-11-11T07:41:38Z")
Thanks so much @mkaro. Will learn from the admin guide ---
**Author:** ![tomdeakin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/tomdeakin/32/261_2.png) [@tomdeakin](https://community.openpbs.org/u/tomdeakin)\ **Post date:** [February 19, 2020, 1:57pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/11 "2020-02-19T13:57:33Z")
I’m having a similar issue cropping up, but only intermittently. Users have SSH keys set up, so everything should be password less. I can scp from the compute node to the headnode manually. The errors I see are: ``` 02/17/2020 15:43:53;0080;pbs_mom;Fil;sys_copy;command: /bin/scp -Brvp /var/spool/pbs/spool/339.mgmt.OU @login:/nfs/home//name.out status=1, try=1 02/17/2020 15:44:24;0080;pbs_mom;Fil;sys_copy;command: /opt/pbs/sbin/pbs_rcp -rp /var/spool/pbs/spool/339.mgmt.OU @login:/nfs/home//name.out status=1, try=2 02/17/2020 15:44:35;0080;pbs_mom;Fil;sys_copy;command: /bin/scp -Brvp /var/spool/pbs/spool/339.mgmt.OU @login:/nfs/home//name.out status=1, try=3 02/17/2020 15:45:06;0080;pbs_mom;Fil;sys_copy;command: /opt/pbs/sbin/pbs_rcp -rp /var/spool/pbs/spool/339.mgmt.OU @login:/nfs/home//name.out status=1, try=4 02/17/2020 15:45:27;0004;pbs_mom;Fil;339.mgmt.OU;Unable to copy file /var/spool/pbs/spool/339.mgmt.OU to login:/nfs/home//name.out 02/17/2020 15:45:27;0004;pbs_mom;Fil;339.mgmt.OU;login: Connection refused ``` There is then a section showing scp -v, which successfully connects but shows lots of `key_load_public: No such file or directory` errors, although the keys are there, and executing the scp command manually works. The log ends with this: ``` 02/17/2020 15:45:27;0004;pbs_mom;Fil;339.mgmt.OU;Host key verification failed. 02/17/2020 15:45:27;0004;pbs_mom;Fil;339.mgmt.OU;lost connection 02/17/2020 15:45:27;0100;pbs_mom;Job;339.mgmt;Job files not copied: Unable to copy file /var/spool/pbs/spool/339.mgmt.OU to login:/nfs/home//name.out >>> error from copy login: Connection refused ``` Does anyone have any idea what might be the cause and what the workaround/fix might be? ---
**Author:** ![vstumpf](https://avatars.discourse-cdn.com/v4/letter/v/dbc845/32.png) [@vstumpf](https://community.openpbs.org/u/vstumpf)\ **Post date:** [February 19, 2020, 6:44pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/12 "2020-02-19T18:44:30Z")
When you’re testing manually, are you the user or root? The pbs\_mom will run the scp/rcp commands as the user who submitted the job. ---
**Author:** ![adarsh](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@adarsh](https://community.openpbs.org/u/adarsh)\ **Post date:** [February 19, 2020, 10:05pm UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/13 "2020-02-19T22:05:54Z")
In the /etc/pbs.conf of Server and Compute node please add these lines in the same order PBS\_RCP=/bin/false PBS\_SCP=/usr/bin/scp PBS\_RSHCOMMAND=/usr/bin/ssh and restart the pbs services in the /etc/ssh/ssh\_config , set StrictHostKeyChecking no It seems when user(s) login then they have to accept the hostkey and this is blocking the file copy (guessing). Please try as that user on the compute node, run this command /bin/scp -Brvp /var/spool/pbs/spool/339.mgmt.OU @login:/nfs/home//name.out If this is causing issue check with combination of -Brvp is failing, then write a wrapper to /usr/bin/scp (scp.sh) which corrects this and add that line to /etc/pbs.conf agains PBS\_SCP=/usr/bin/scp\_wrapper.sh ---
**Author:** ![tomdeakin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/tomdeakin/32/261_2.png) [@tomdeakin](https://community.openpbs.org/u/tomdeakin)\ **Post date:** [February 20, 2020, 11:32am UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/14 "2020-02-20T11:32:33Z")
I tested manually as the user. ---
**Author:** ![tomdeakin](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/tomdeakin/32/261_2.png) [@tomdeakin](https://community.openpbs.org/u/tomdeakin)\ **Post date:** [February 20, 2020, 11:48am UTC](https://community.openpbs.org/t/pbs-pro-passwordless-configuration/1286/15 "2020-02-20T11:48:26Z")
> in the /etc/ssh/ssh\_config , set StrictHostKeyChecking no > It seems when user(s) login then they have to accept the hostkey and this is blocking the file copy (guessing). I see, this could be it. If there is a prompt to OK the host address that would stop any script working probably, unless they went onto the node manually to fix it. I’m surprised the `-B` option doesn’t do this. I’ll try setting this on the compute nodes and seeing what happens… Thanks for the help.