Hello Narcis,
> 2020-03-26 07:54:21 1603ae1b395c gc3.elasticluster[1] ERROR Command
> `ansible-playbook --private-key=/home/ubuntu/.ssh/id_rsa
> /home/elasticluster/share/playbooks/main.yml
> --inventory=/home/ubuntu/.elasticluster/storage/primrose.inventory --become
> --become-user=root -e @extra_vars.yml` failed with exit code 2.
This is the final, top-level error, the root cause would be in the
preceding lines; in this case, since the failure happened while
running Ansible, it would be in Ansible's output.
Looking at the complete output (good that you included it!), it seems
to me that all tasks on `medXXX` nodes fail with this error
(reformatted for readability):
Running installation command 'apt-get install -y python2.7
python-simplejson' ...
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/),
is another process using it?"
This typically happens on Debian/Ubuntu when you try to install a
package (`apt-get install`) while some other package is being
installed or upgraded.
It may be a transient error; just try again and see if it works now.
If it still fails, log into one of the failing nodes:
elasticluster ssh primrose -n med32compute002
then run these commands to see what is still holding the lock:
sudo fuser -v /var/lib/dpkg/lock
ps auxww | egrep 'dpkg|apt'
Thanks,
R
--
You received this message because you are subscribed to the Google Groups
"elasticluster" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticluster/CAJGE3zWxV%2BHKHkMnOe9z5Xa1JhRs1HNGverFFFa06MZV8CmbCQ%40mail.gmail.com.
