Thank you very much for your quick reply! 

I installed parallel on an AWS EC2 (on a quite new, Linux 2 AMI) using yum, 
without realizing it was such an old version!

I will install the latest version from the tar file you mentioned.

Will also drop noswap option.

Thank you very much once again


> On Sep 21, 2018, at 1:48 AM, Hans Schou <ch...@schou.dk> wrote:
> 
> Hi Ihsan
> 
> > The version number: 20160222
> 
> That is quite an old version. You should upgrade to the newest version:
> 
> http://ftp.gnu.org/gnu/parallel/?C=M;O=D 
> <http://ftp.gnu.org/gnu/parallel/?C=M;O=D>
> 
> Remember, 'parallel' is just one Perl script, so an upgrade could be as 
> simple as downloading the tar-ball and replace that one file on your system.
> 
> > parallel -a commands --load 200% --noswap {}
> 
> My first guess: The "noswap" makes you run out of memory
> 
> ./hans
> 
> On Fri, Sep 21, 2018 at 3:23 AM Ihsan Ecemis <miece...@gmail.com 
> <mailto:miece...@gmail.com>> wrote:
> 
> Hello,
> 
> We started having GNU Parallel crashing on our production server with the 
> following message:
> 
> parallel: This should not happen. You have found a bug.
> Please contact <parallel@gnu.org <mailto:parallel@gnu.org>> and include:
> * The version number: 20160222
> * The bugid: loadavg_invalid_content: /home/ec2-user/.parallel/tmp/loadavg-:
> 
> * 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.
> 
> 
> We usually put a few hundreds commands into a file and then run them with 
> something like: 
> 
> parallel -a commands --load 200% --noswap {}
> 
> 
> Note that the same user may be running multiple parallel’s on the same server 
> at the same time (they are triggered by external events).  I hope a User is 
> not limited to running only 1 parallel process at a given time.
> 
> 
> Any help will be greatly appreciated.  In advance, thank you very much for 
> any clues in resolving this.
> 
> Thanks,
> 
> Ihsan.

Reply via email to