juju / persistent-cookiejar

cookiejar is a fork of net/http/cookiejar that allows serialisation of the stored cookies
BSD 3-Clause "New" or "Revised" License
112 stars 75 forks source link

Error trying to deploy charms #11

Closed jmtz-telmex closed 8 years ago

jmtz-telmex commented 8 years ago

Hi,

I installed Openstack using Autopilot install. The instalation was fine and Openstack works well. The problem is the same when I try to connect to Ladscape-server to deploy juju-gui:

Executing from MAAS Server

export JUJU_HOME=~/.cloud-install/juju juju ssh landscape-server/0 sudo 'JUJU_HOME=/var/lib/landscape/juju-homes/sudo ls -rt /var/lib/landscape/juju-homes/ | tail -1 sudo -u landscape -E bash'

And from Landscape-server:

landscape@juju-machine-0-lxc-1:~$ juju deploy --to 0 juju-gui ERROR cannot load cookies: file locked for too long; giving up

How can I check what files are locked? What is the locked type and how fixit?

Regards,

cmars commented 8 years ago

Hi @jmtz-telmex, sorry to hear you're having trouble with autopilot. What version of Juju do you have (output from juju version and juju status would be helpful)?

jmtz-telmex commented 8 years ago

Hi @cmars , The Juju Version is: 1.25.3-trusty-amd64

The output fom juju status of openstack enviroment bootstraped with Landscape and juju:

environment: "1" machines: "0": agent-state: started agent-version: 1.25.3 dns-name: blade04.croma instance-id: /MAAS/api/1.0/nodes/node-7a6a40ae-d920-11e5-b04c-0017a4770400/ series: trusty containers: 0/lxc/0: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.11 instance-id: juju-machine-0-lxc-0 series: trusty hardware: arch=amd64 0/lxc/1: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.18 instance-id: juju-machine-0-lxc-1 series: trusty hardware: arch=amd64 0/lxc/2: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.19 instance-id: juju-machine-0-lxc-2 series: trusty hardware: arch=amd64 0/lxc/3: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.20 instance-id: juju-machine-0-lxc-3 series: trusty hardware: arch=amd64 0/lxc/4: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.21 instance-id: juju-machine-0-lxc-4 series: trusty hardware: arch=amd64

  0/lxc/5:
    agent-state: started
    agent-version: 1.25.3
    dns-name: 10.1.3.22
    instance-id: juju-machine-0-lxc-5
    series: trusty
    hardware: arch=amd64
hardware: arch=amd64 cpu-cores=24 mem=16384M
state-server-member-status: has-vote

"1": agent-state: started agent-version: 1.25.3 dns-name: blade05.croma instance-id: /MAAS/api/1.0/nodes/node-7aeb72e6-d920-11e5-b38a-0017a4770400/ series: trusty containers: 1/lxc/0: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.25 instance-id: juju-machine-1-lxc-0 series: trusty hardware: arch=amd64 1/lxc/1: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.27 instance-id: juju-machine-1-lxc-1 series: trusty hardware: arch=amd64 1/lxc/2: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.28 instance-id: juju-machine-1-lxc-2 series: trusty hardware: arch=amd64 1/lxc/3: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.29 instance-id: juju-machine-1-lxc-3 series: trusty hardware: arch=amd64 1/lxc/4: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.32 instance-id: juju-machine-1-lxc-4 series: trusty hardware: arch=amd64 1/lxc/5: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.35 instance-id: juju-machine-1-lxc-5 series: trusty hardware: arch=amd64 hardware: arch=amd64 cpu-cores=24 mem=16384M "2": agent-state: started agent-version: 1.25.3 dns-name: blade11.croma instance-id: /MAAS/api/1.0/nodes/node-8a4124ca-d920-11e5-90f1-0017a4770400/ series: trusty containers: 2/lxc/0: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.36 instance-id: juju-machine-2-lxc-0 series: trusty hardware: arch=amd64 2/lxc/1: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.37 instance-id: juju-machine-2-lxc-1 series: trusty hardware: arch=amd64 2/lxc/2: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.39 instance-id: juju-machine-2-lxc-2 series: trusty hardware: arch=amd64 2/lxc/3: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.41 instance-id: juju-machine-2-lxc-3 series: trusty hardware: arch=amd64 2/lxc/4: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.44 instance-id: juju-machine-2-lxc-4 series: trusty hardware: arch=amd64 2/lxc/5: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.47 instance-id: juju-machine-2-lxc-5 series: trusty hardware: arch=amd64 hardware: arch=amd64 cpu-cores=24 mem=49152M "3": agent-state: started agent-version: 1.25.3 dns-name: blade06.croma instance-id: /MAAS/api/1.0/nodes/node-adfa0458-d921-11e5-a791-0017a4770400/ series: trusty containers: 3/lxc/0: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.31 instance-id: juju-machine-3-lxc-0 series: trusty hardware: arch=amd64 3/lxc/1: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.34 instance-id: juju-machine-3-lxc-1 series: trusty hardware: arch=amd64 3/lxc/2: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.38 instance-id: juju-machine-3-lxc-2 series: trusty hardware: arch=amd64 3/lxc/3: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.40 instance-id: juju-machine-3-lxc-3 series: trusty hardware: arch=amd64 3/lxc/4: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.43 instance-id: juju-machine-3-lxc-4 series: trusty hardware: arch=amd64 3/lxc/5: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.46 instance-id: juju-machine-3-lxc-5 series: trusty hardware: arch=amd64 hardware: arch=amd64 cpu-cores=24 mem=16384M "4": agent-state: started agent-version: 1.25.3 dns-name: blade10.croma instance-id: /MAAS/api/1.0/nodes/node-8637fe08-d920-11e5-b04c-0017a4770400/ series: trusty containers: 4/lxc/0: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.42 instance-id: juju-machine-4-lxc-0 series: trusty hardware: arch=amd64 4/lxc/1: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.45 instance-id: juju-machine-4-lxc-1 series: trusty hardware: arch=amd64 4/lxc/2: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.49 instance-id: juju-machine-4-lxc-2 series: trusty hardware: arch=amd64 4/lxc/3: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.51 instance-id: juju-machine-4-lxc-3 series: trusty hardware: arch=amd64 4/lxc/4: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.53 instance-id: juju-machine-4-lxc-4 series: trusty hardware: arch=amd64 4/lxc/5: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.55 instance-id: juju-machine-4-lxc-5 series: trusty hardware: arch=amd64 hardware: arch=amd64 cpu-cores=24 mem=49152M "5": agent-state: started agent-version: 1.25.3 dns-name: blade09.croma instance-id: /MAAS/api/1.0/nodes/node-8244533c-d920-11e5-90f1-0017a4770400/ series: trusty containers: 5/lxc/0: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.48 instance-id: juju-machine-5-lxc-0 series: trusty hardware: arch=amd64 5/lxc/1: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.50 instance-id: juju-machine-5-lxc-1 series: trusty hardware: arch=amd64 5/lxc/2: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.52 instance-id: juju-machine-5-lxc-2 series: trusty hardware: arch=amd64 5/lxc/3: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.54 instance-id: juju-machine-5-lxc-3 series: trusty hardware: arch=amd64 5/lxc/4: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.56 instance-id: juju-machine-5-lxc-4 series: trusty hardware: arch=amd64 5/lxc/5: agent-state: started agent-version: 1.25.3 dns-name: 10.1.3.57 instance-id: juju-machine-5-lxc-5 series: trusty hardware: arch=amd64 hardware: arch=amd64 cpu-cores=24 mem=49152M services: ceilometer: charm: cs:trusty/ceilometer-16 exposed: false service-status: current: active message: Unit is ready since: 22 Feb 2016 06:30:12Z relations: amqp:

cmars commented 8 years ago

@jmtz-telmex #12 fixes this, we plan to get this into Juju 1.25.4 which should release this week.

The lock file error is temporary and intermittent. You should be able to get past it by retrying the juju command until successful. If you have a concurrent juju command running elsewhere (watch juju status for example) it might be best to stop it until the operation completes, if possible.