If the machine you’re installing Torque on doesn’t have an official FQDN, a simple work-around is to invent one and assign it to the machine’s network IP.
For example, if eth0 is assigned to 192.168.1.1, we can add the following line to /etc/hosts.
What made this not a fun experience was that I couldn’t find any notes from what I did the last time, which is rather unusual.
You see, every time I encounter a problem with a non-obvious solution I like to write a blog post about it.
Maybe that’s why I want to know more about the tight-lipped Van Camp and Bowman.
Well, that was all for the show, of course, but you can't deny that they're really good together.
Just imagine what the two must be like without the intrigue and drama.
Van Camp explained, "Josh and I keep it all very separate.
Check the logs (under /var/spool/torque) for whatever is failing.Usually it is because the commands look like they’re coming from an unauthorized user/machine, that is anything different from the string ‘[email protected] We’ll set this up with default 1-hour time limit and single-node requirement, but you don’t have to.# create default queue qmgr -c 'create queue batch' qmgr -c 'set queue batch queue_type = execution' qmgr -c 'set queue batch started = true' qmgr -c 'set queue batch enabled = true' qmgr -c 'set queue batch resources_default.walltime = ' qmgr -c 'set queue batch resources_default.nodes = 1' qmgr -c 'set server default_queue = batch' Finally, we need to configure the server to allow submissions from itself. Note that the submit_hosts lists cannot be made up to FQDNs!Eventually, job submission would be extended to other machines, adding them also as compute nodes on additional queues.To help myself if I ever need to do this again, and to help anyone else in the same situation, I’ll detail below what I did.