On Wed, Nov 23, 2016 at 5:23 AM, Pierre Poujade <[email protected]> wrote: > Hi, > > I wanted to see how parallel behaves when one of the hosts is down. > root@nope is down (host doesn't exist on the network and won't resolve), > scanner-helper is up and running. > > $ parallel --controlmaster --filter-hosts --eta -j2 -S > root@nope,:,user@scanner-helper sleep ::: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 > 2 2 2 2 2 > parallel: Warning: Could not figure out > parallel: Warning: number of cpus on user@scanner-helper. Using 1. > parallel: Warning: Could not figure out > parallel: Warning: number of cpus on user@scanner-helper. Using 1. > parallel: This should not happen. You have found a bug. > Please contact [email protected] and include: > * The version number: 20160922 > * The bugid: host check too many col0: user@scanner-helper /bin/bash: > parallel: command not found > * The command line being run > * The files being read (put the files on a webserver if they are big) > > If you get the error on smaller/fewer files, please include those instead. > > If I remove the --filter-hosts, I don't get the warning but of course I'm > getting output about root@nope that can't be contacted.
The problem is that parallel is not installed on user@scanner-helper. But that should clearly have a better error message. /Ole
