Dear Riccardo, Thanks a lot for your prompt response!

When I run those commands here is what I get:

*ubuntu@primrose-med32compute001*:*~*$ sudo fuser -v /var/lib/dpkg/lock

                     USER        PID ACCESS COMMAND

/var/lib/dpkg/lock:  root       3316 F.... dpkg

*ubuntu@primrose-med32compute001*:*~*$ ps auxww | egrep 'dpkg|apt'

root      3223  0.0  0.1 115388 63232 ?        S    12:16   0:11 *apt*-get 
install -y python2.7 python-simplejson

root      3316  0.0  0.0  23592  4544 pts/1    Ss+  12:16   0:00 /usr/bin/
*dpkg* --status-fd 43 --configure --pending

root      3328  0.0  0.0  67640 18524 pts/1    S+   12:17   0:00 
/usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/*dpkg*/info/libssl1.1:amd64.postinst 
configure 1.1.0g-2ubuntu4.1

root      3334  0.0  0.0   4628  1792 pts/1    S+   12:17   0:00 /bin/sh 
/var/lib/*dpkg*/info/libssl1.1:amd64.postinst configure 1.1.0g-2ubuntu4.1

ubuntu    5371  0.0  0.0  17548  1084 pts/3    S+   19:02   0:00 grep -E 
--color=auto *dpkg*|*apt*

Just to mention that I ran setup several times and updated elasticluster in 
between.

Best regards,
Narcis


On Thursday, March 26, 2020 at 7:33:11 PM UTC+1, Riccardo Murri wrote:
>
> 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/e89b36ff-820c-492f-9ba1-9093796bceb6%40googlegroups.com.

Reply via email to