Looks like ceph-deploy 1.5.20 thinks your Ubuntu 15.10 wily system is
an Upstart-based system, and it's systemd instead.
- Ken
On Fri, Nov 13, 2015 at 7:51 AM, Robert Shore <rshore@xxxxxxxxxxxxxxxx> wrote:
> OS: Linux b260-space-pc62 4.2.0-18-generic #22-Ubuntu SMP Fri Nov 6 18:25:50
> UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> (wily werewolf)
>
> Command: ceph-deploy mon create-initial
>
> Log fragment:
> [ceph_deploy.conf][DEBUG ] found configuration file at:
> /home/dfs/.cephdeploy.conf
> [ceph_deploy.cli][INFO ] Invoked (1.5.20): /usr/bin/ceph-deploy mon
> create-initial
> [ceph_deploy.mon][DEBUG ] Deploying mon, cluster ceph hosts b260-space-pc39
> b260-space-pc61 b260-space-pc62
> [ceph_deploy.mon][DEBUG ] detecting platform for host b260-space-pc39 ...
> [b260-space-pc39][DEBUG ] connection detected need for sudo
> [b260-space-pc39][DEBUG ] connected to host: b260-space-pc39
> [b260-space-pc39][DEBUG ] detect platform information from remote host
> [b260-space-pc39][DEBUG ] detect machine type
> [ceph_deploy.mon][INFO ] distro info: Ubuntu 15.10 wily
> [b260-space-pc39][DEBUG ] determining if provided host has same hostname in
> remote
> [b260-space-pc39][DEBUG ] get remote short hostname
> [b260-space-pc39][DEBUG ] deploying mon to b260-space-pc39
> [b260-space-pc39][DEBUG ] get remote short hostname
> [b260-space-pc39][DEBUG ] remote hostname: b260-space-pc39
> [b260-space-pc39][DEBUG ] write cluster configuration to
> /etc/ceph/{cluster}.conf
> [b260-space-pc39][DEBUG ] create the mon path if it does not exist
> [b260-space-pc39][DEBUG ] checking for done path:
> /var/lib/ceph/mon/ceph-b260-space-pc39/done
> [b260-space-pc39][DEBUG ] done path does not exist:
> /var/lib/ceph/mon/ceph-b260-space-pc39/done
> [b260-space-pc39][INFO ] creating keyring file:
> /var/lib/ceph/tmp/ceph-b260-space-pc39.mon.keyring
> [b260-space-pc39][DEBUG ] create the monitor keyring file
> [b260-space-pc39][INFO ] Running command: sudo ceph-mon --cluster ceph
> --mkfs -i b260-space-pc39 --keyring
> /var/lib/ceph/tmp/ceph-b260-space-pc39.mon.keyring
> [b260-space-pc39][DEBUG ] ceph-mon: set fsid to
> 74e0d24e-8cd7-4e17-bd9c-d504fc709c31
> [b260-space-pc39][DEBUG ] ceph-mon: created monfs at
> /var/lib/ceph/mon/ceph-b260-space-pc39 for mon.b260-space-pc39
> [b260-space-pc39][INFO ] unlinking keyring file
> /var/lib/ceph/tmp/ceph-b260-space-pc39.mon.keyring
> [b260-space-pc39][DEBUG ] create a done file to avoid re-doing the mon
> deployment
> [b260-space-pc39][DEBUG ] create the init path if it does not exist
> [b260-space-pc39][DEBUG ] locating the `service` executable...
> [b260-space-pc39][INFO ] Running command: sudo initctl emit ceph-mon
> cluster=ceph id=b260-space-pc39
> [b260-space-pc39][WARNING] initctl: Unable to connect to Upstart: Failed to
> connect to socket /com/ubuntu/upstart: Connection refused
> [b260-space-pc39][ERROR ] RuntimeError: command returned non-zero exit
> status: 1
> [ceph_deploy.mon][ERROR ] Failed to execute command: initctl emit ceph-mon
> cluster=ceph id=b260-space-pc39
> [ceph_deploy.mon][DEBUG ] detecting platform for host b260-space-pc61 ...
>
> The same log pattern (with the error) repeats for the other 2 hosts.
>
> Any suggestions? More info?
>
> _______________________________________________
> ceph-users mailing list
> ceph-users@xxxxxxxxxxxxxx
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
