On 11-11-2016 16:23, Willem Jan Withagen wrote: > On 11-11-2016 13:50, Willem Jan Withagen wrote: >> Hi, >> >> As one of the last steps to complete my first run op porting I need to >> get ceph-disk working... >> But I'm getting a stall in test_activate for the OSD. why doesn't the >> activation of the OSD background and the script continues. > > Right, > > I was wrong.... After lots of prints and echos I have learned that > ceph-osd does daemonize and return to the shell right after that with > exit code 0 . > So there now everything is well. > > Question is now back my favourite problem: figuring python out. :( > Where between bin/ceph-osd and the command_check_call() things get hang up. Well, the plot thinkens.... and it gets weirder and weirder. Both ceph-osd, ceph-disk and coverage return. Just filled the python up with prints till I was sure.... Removing the timeout 360 from the commandline in test.sh actually gets the job done. So one way or another /usr/bin/timeout thinks that the process did not finish. And that is something I have not seen before. Looking at the pstree ceph-osd is a direct child of timeout. No more processes in between. So all intermediate work seems te be done. And I'm not sure why timeout thinks its children are not finished. Note that this is the only case where timeout starts acting up. I guess that I'm going to if-fi it for the time being... --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
