On 11-11-2016 16:44, Loic Dachary wrote: > > > On 11/11/2016 16:30, Willem Jan Withagen wrote: >> On 11-11-2016 16:21, Sage Weil wrote: >>> On Fri, 11 Nov 2016, Loic Dachary wrote: >>>> Hi, >>>> >>>> FYI when the init system is unknown, it runs ceph-osd directly instead of delegating to the init system. >>>> >>>> https://github.com/ceph/ceph/blob/master/src/ceph-disk/ceph_disk/main.py#L3468 >>>> >>>> The reason why it does not daemonize is unclear to me. >>> >>> Does ceph-osd daemonize if you run it manually from the command line? >> >> Yup, >> >> created a small wrapper to see what happened in there, and I actually >> see the wrapper exiting. Only this happy event does not make it thru to >> the python friends. :( And after 360 sec timeout kills the lot. > > Couldy you show the command line you're using to manually run the OSD ? I suspect the arguments are not the same: the python script populates the CEPH_ARGS environment variable. > > Just a thought ;-) Hi Loic, Yup, there is a lot of coverage stuff in between.... I have not really manually run the ceph-osd command, but wrapped it in: #!/bin/bash shopt -s -o pipefail echo "$@" > /tmp/ceph-osd.$$.out /usr/srcs/Ceph/work/ceph/build/bin/ceph-osd.bin "$@" | \ tee -a /tmp/ceph-osd.$$.out status=$? echo ceph-osd done >> /tmp/ceph-osd.$$.out exit $status ==== And this actually logs 'done' in the logfile. So the ceph-osd actually returns, and so does the wrapper. As options is logs: --cluster=ceph --id=0 --osd-data=testdir/test-ceph-disk/dir --osd-journal=testdir/test-ceph-disk/dir/journal I could also log: ENV and rerun. --WjW -- 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
