local provider mongo error on utopic

[Ian Booth]

mongo won't start when using the local provier on utopic

May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] MongoDB starting : pid=2472 port=37017 dbpath=/home/jamespage/.juju/local/db 64-bit host=hendrix
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] db version v2.4.9
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] git version: nogitversion
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] build info: Linux panlong 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013 x86_64 BOOST_LIB_VERSION=1_55
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] allocator: tcmalloc
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] options: { auth: true, bind_ip: "0.0.0.0", dbpath: "/home/jamespage/.juju/local/db", noprealloc: true, port: 37017, smallfiles: true, sslOnNormalPorts: true, sslPEMKeyFile: "/home/jamespage/.juju/local/server.pem", sslPEMKeyPassword: "<password>", syslog: true }
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] exception in initAndListen std::exception: boost::filesystem::status: Permission denied: "/home/jamespage/.juju/local/db", terminating
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170
May 19 14:57:18 hendrix mongod.37017[2472]: dbexit:
May 19 14:57:18 hendrix mongod.37017[2472]:
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] shutdown: going to close listening sockets...
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] shutdown: going to flush diaglog...
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.170 [initandlisten] shutdown: going to close sockets...
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.171 [initandlisten] shutdown: waiting for fs preallocator...
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.171 [initandlisten] shutdown: lock for final commit...
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.171 [initandlisten] shutdown: final commit...
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.171 [initandlisten] shutdown: closing all files...
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.171 [initandlisten] closeAllFiles() finished
May 19 14:57:18 hendrix mongod.37017[2472]: Mon May 19 14:57:18.171
May 19 14:57:18 hendrix mongod.37017[2472]: dbexit: really exiting now
May 19 14:57:18 hendrix mongod.37017[2472]:

[Andrew Wilkins (axwalk)]

I was able to bootstrap 1.18.3 on the daily utopic desktop ISO. I just had to install juju-core, juju-local and mongodb-server (I think the last is unnecessary from 1.19).

Do you have a cloud instance with utopic on that exhibits the issue and that I can access?

[Robie Basak (racb)]

I've reproduced this on a cloud instance. I'll send you access details privately.

To reproduce, I:

Started a Utopic cloud instance (on OpenStack).

sudo apt-get update && eatmydata apt-get dist-upgrade
# copy in juju-core_1.18.4+bzr2293-0ubuntu1*.deb
dpkg -i *.deb
sudo apt-get -f install
mkdir -p ~/.juju
cat > ~/.juju/environments.yaml << EOF
default: local-test
environments:
  local-test:
    type: local
    admin-secret: c46629f0935c757a46b26946ac244f3f
EOF
juju bootstrap --debug 2>&1|tee juju-bootstrap.log

[Andrew Wilkins (axwalk)]

I wasn't able to get into your instance, so I started up a Utopic cloud instance of my own in canonistack, lcy02. I had to install mongodb-server as in my previous comment, but then it all just worked.

I don't know where the deb you mentioned is, so I tested with the latest in ppa:juju/stable. Where can I find juju-core_1.18.4+bzr2293-0ubuntu1*.deb? Perhaps that is broken.

[Robie Basak (racb)]

Sorry, I made an error in the details I sent you privately - now updated.

I've also uploaded the packages I'm using to ppa:racb/experimental. These are exactly the same as the current juju-core packaging in Utopic, except that they have bzr2293 pulled in (and a minor dep8 test change that isn't relevant here) and are rebuilt against Utopic. This is because we know the packaging in Utopic to be broken due to bug 1314686, so we will need to upload a new juju-core to Utopic to fix that (and then SRU to Trusty), but preparing such an update fails due to this bug. My PPA version is a close to what I'd expect to upload to Utopic.

A key difference here is that juju-local depends on juju-mongodb, not mongodb-server. But this arrangement did work previously in Trusty, based on the same packaging.

[Andrew Wilkins (axwalk)]

Okay, so it appears that juju will use juju-mongodb on trusty, but *only* on trusty. It should be trusty+. I will fix this in the morning.

[Robie Basak (racb)]

Stuck in utopic-proposed due to bug 1329295.

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju-core - 1.18.4-0ubuntu1

---------------
juju-core (1.18.4-0ubuntu1) utopic; urgency=medium

  * New upstream release, including essential fixes for supporting Utopic and
    all future releases:
    - Support Utopic and future releases by using distro-info-data over
      hardcoded defaults (LP: #1314686).
    - Correctly use juju-mongodb on Trusty and all future releases, rather than
      hardcoding Trusty as special (LP: #1321025).
  * Depend on distro-info so that Juju can use its data in preference to
    hard-coded defaults (LP: #1325025).
  * d/tests/*:
    - Remove hardcoding of precise.
    - Use --upload-tools to reduce external dependencies on local and manual provider testing.
    - Add stderr logging.
    - New test for manual provider against localhost.
    - Mark tests breaks-testbed and isolation-machine so that they do not step on each other.
    - Add "future release" testing for both local and manual providers.
 -- Robie Basak <email address hidden> Fri, 06 Jun 2014 15:53:28 +0000