ERROR destroying environment with the local provider

Bug #1274197 reported by Matt Bruzek
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
juju-core
Triaged
High
Unassigned

Bug Description

I am running the latest (as of 01/29/2014) juju-core deb package from here http://162.213.35.54:8080/job/prepare-new-version/

I was able to bootstrap my local environment (previously could not without deb package) and deploy a charm. Upon trying to destroy the environment I get an error:

$ juju destroy-environment local
WARNING! this command will destroy the "local" environment (type: local)
This includes all machines, services, data and other resources.

Continue [y/N]? y
ERROR destroying environment: remove /etc/lxc/auto/mbruzek-local-machine-1.conf: no such file or directory

I have a clean up script that helps me clean up my local lxc environment. Which runs the following commans:
+ sudo lxc-stop --name mbruzek-local-machine-1
+ sudo lxc-destroy --name mbruzek-local-machine-1
+ sudo rm /etc/init/juju-agent-mbruzek-local.conf /etc/init/juju-db-mbruzek-local.conf

Now when I try to bootstrap a new local environment I am getting an error that I have not encountered before:
mbruzek@skull:~$ juju bootstrap -e local
ERROR cannot use 37017 as state port, already in use
mbruzek@skull:~$ juju status
ERROR Unable to connect to environment "local".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
environment is not bootstrapped

Can you suggest a work around? What can I do to use port 37017?

Curtis Hovey (sinzui)
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 1.18.0
tags: added: local-provider lxc trusty
Revision history for this message
Matt Bruzek (mbruzek) wrote :

Curtis and I talked on IRC. I don't have a resolution for this bug, but I have a few steps that will clear the error.

ps -ef | grep mongo (to find all the mongodb instances)
sudo kill <mongodb-pid>

This clears up the error on port 37017. It should be noted I still can not use the local provider.

I wanted to leave this information here, in case that helps anyone else clear the error, or if there are additional things I should be doing.

Ian Booth (wallyworld)
tags: added: destroy-environment
summary: - ERROR destroying environment
+ ERROR destroying environment with the local provider
Revision history for this message
Adam Stokes (adam-stokes) wrote :

+1 On killing the mongod process worked for me

tags: added: cloud-installer
Curtis Hovey (sinzui)
tags: added: mongodb
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.