I see. This is the ownership info for /var/lib/ceph [nwatkins@cn67 ~]$ stat /var/lib/ceph File: `/var/lib/ceph' -> `/ram/var/lib/ceph' Size: 17 Blocks: 3 IO Block: 524288 symbolic link Device: 12h/18d Inode: 4429801211 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 10/ wheel) This is probably a rather non traditional environment that Ceph is being deployed onto. I talked with the sys admins and they were rather surprised by this. I guess we can take care of it on this end now that we see the issue. In general should the ceph-deploy tool version be paired up with the version of Ceph being deployed, or is it the case that for Hammer the file system uid/gid _should be_ 0 to avoid the unsupported --getgroup flag? Thanks! On Wed, Sep 2, 2015 at 3:32 PM, Travis Rhoden <trhoden@xxxxxxxxx> wrote: > Hi Noah, > > What is the ownership on /var/lib/ceph ? > > ceph-deploy should only be trying to use --setgroup if /var/lib/ceph is > owned by non-root. > > On a fresh install of Hammer, this should be root:root. > > The --setgroup flag was added to ceph-deploy in 1.5.26. > > - Travis > > On Wed, Sep 2, 2015 at 1:59 PM, Noah Watkins <noahwatkins@xxxxxxxxx> wrote: >> >> I'm getting the following error using ceph-deploy to setup a cluster. >> It's Centos6.6 and I'm using Hammer and the latest ceph-deploy. It >> looks like setgroup wasn't an option in Hammer, but ceph-deploy adds >> it. Is there a trick or older version of ceph-deploy I should try? >> >> - Noah >> >> [cn67][INFO ] Running command: sudo ceph-mon --cluster ceph --mkfs -i >> cn67 --keyring /var/lib/ceph/tmp/ceph-cn67.mon.keyring --setgroup 10 >> [cn67][WARNIN] too many arguments: [--setgroup,10] >> [cn67][DEBUG ] --conf/-c FILE read configuration from the given >> configuration file >> [cn67][WARNIN] usage: ceph-mon -i monid [flags] >> [cn67][DEBUG ] --id/-i ID set ID portion of my name >> [cn67][WARNIN] --debug_mon n >> [cn67][DEBUG ] --name/-n TYPE.ID set name >> [cn67][WARNIN] debug monitor level (e.g. 10) >> [cn67][DEBUG ] --cluster NAME set cluster name (default: ceph) >> [cn67][WARNIN] --mkfs >> [cn67][DEBUG ] --version show version and quit >> [cn67][WARNIN] build fresh monitor fs >> [cn67][DEBUG ] >> [cn67][WARNIN] --force-sync >> [cn67][DEBUG ] -d run in foreground, log to stderr. >> [cn67][WARNIN] force a sync from another mon by wiping local >> data (BE CAREFUL) >> [cn67][DEBUG ] -f run in foreground, log to usual >> location. >> [cn67][WARNIN] --yes-i-really-mean-it >> [cn67][DEBUG ] --debug_ms N set message debug level (e.g. 1) >> [cn67][WARNIN] mandatory safeguard for --force-sync >> [cn67][WARNIN] --compact >> [cn67][WARNIN] compact the monitor store >> [cn67][WARNIN] --osdmap <filename> >> [cn67][WARNIN] only used when --mkfs is provided: load the >> osdmap from <filename> >> [cn67][WARNIN] --inject-monmap <filename> >> [cn67][WARNIN] write the <filename> monmap to the local >> monitor store and exit >> [cn67][WARNIN] --extract-monmap <filename> >> [cn67][WARNIN] extract the monmap from the local monitor store and >> exit >> [cn67][WARNIN] --mon-data <directory> >> [cn67][WARNIN] where the mon store and keyring are located >> [cn67][ERROR ] RuntimeError: command returned non-zero exit status: 1 >> [ceph_deploy.mon][ERROR ] Failed to execute command: ceph-mon >> --cluster ceph --mkfs -i cn67 --keyring >> /var/lib/ceph/tmp/ceph-cn67.mon.keyring --setgroup 10 >> [ceph_deploy][ERROR ] GenericError: Failed to create 1 monitors >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
