Hello Maiken, all,
creation of CentOS 7.x and 6.x clusters with the default settings
(`slow_but_safer=no`, i.e., use "eatmydata" to speed up operations)
should now be fixed in the current "master" branch -- can you please
give it a try?
Ciao,
R
--
You received this message because you are
Very good, will do. Added the workaround as I remembered it from last time.
Thanks.
Maiken
> On 14 Jun 2019, at 21:31, Riccardo Murri wrote:
>
> Hello Maiken,
>
> sorry for the late reply - I am on vacation until end of June. Can
> you please open a bug at
>
Hello Maiken,
sorry for the late reply - I am on vacation until end of June. Can
you please open a bug at
https://github.com/gc3-uzh-ch/elasticluster/issues -- I will take a
look at it when I'm back.
Meanwhile, the workaround is to add:
safe_but_slower=yes
to your cluster's
Hi,
took a while, but I am finally trying the resize again now with
elasticluster version 1.3.dev15
Unfortunately I still see the eatmydata problem:
fatal: [computeb002]: FAILED! => {"changed": true, "msg": "non-zero return
code", "rc": 70, "stderr": "Shared connection to 158.39.48.117
I never got that far, but now at last I am ready to give it a try. I will
tell you how it went.
On Tuesday, May 7, 2019 at 10:53:22 PM UTC+2, Maiken Pedersen wrote:
>
> Hi,
> Very nice, thank you very much. I will give it a try tomorrow!
> Maiken
>
> > On 7 May 2019, at 21:50, Riccardo Murri
Hi,
Very nice, thank you very much. I will give it a try tomorrow!
Maiken
> On 7 May 2019, at 21:50, Riccardo Murri wrote:
>
> Hello Maiken,
>
> this bug should be fixed in the latest version of the "master" branch.
> To upgrade your Docker image, run:
>
>elasticluster.sh --pull --latest
Hello Maiken,
this bug should be fixed in the latest version of the "master" branch.
To upgrade your Docker image, run:
elasticluster.sh --pull --latest
Can you please try and confirm that the fix works? I'll tag 1.3.dev14
once I get confirmation.
Ciao,
R
--
You received this message
Hello Maiken,
> ./elasticluster.sh resize -a 0:compute $clustername -t slurm
>
> gives the following:
>
> fatal: [compute003]: FAILED! => {"changed": false, "module_stderr":
> "/usr/bin/python+eatmydata: line 3: /usr/bin/eatmydata: No such file or
> directory\n", "module_stdout": "", "msg":
Hi again,
so managed to get the newest version of elasticluster working through the
elasticluster.sh.
I am trying to resize my cluster.
Since the resize step failed at some point late in the setup step earlier,
I need to run it again.
./elasticluster.sh setup $clustername
or
