Re: radosgw segfault in 0.56

2013-01-07 Thread Sylvain Munaut
Hi, happened to me using ubuntu packages. usually when you upgrade a package it calls all its dependencies, for ceph you have to update one by one. did you try that ? All ceph packages are up to date. Same happens with a custom compiled radosgw from git Cheers, Sylvain -- To

Re: radosgw segfault in 0.56

2013-01-07 Thread Sylvain Munaut
Ok, I tracked this down ... I'm using lighttpd as a FastCGI front end and it doesn't set SCRIPT_URI environment. So the line 1123 in rgw/rgw_rest.cc : s-script_uri = s-env-get(SCRIPT_URI); Tries to assign NULL to s-script_uri which crashes with the particularly unhelpful stack trace I pasted

Re: radosgw segfault in 0.56

2013-01-07 Thread Wido den Hollander
On 01/07/2013 12:04 PM, Sylvain Munaut wrote: Ok, I tracked this down ... I'm using lighttpd as a FastCGI front end and it doesn't set SCRIPT_URI environment. So the line 1123 in rgw/rgw_rest.cc : s-script_uri = s-env-get(SCRIPT_URI); Tries to assign NULL to s-script_uri which crashes with

Re: radosgw segfault in 0.56

2013-01-07 Thread Sylvain Munaut
Hi, As far as I know relying on SCRIPT_URI is rather dangerous since it's not always there. There better should be an if/else-satement surrounding that code having it defaulting to something else if SCRIPT_URI isn't available. I've opened a bug and proposed a patch setting the default value

Re: radosgw segfault in 0.56

2013-01-07 Thread Caleb Miles
Hi all, Created branch wip-3735 to capture Sylvain's patch. On Mon, Jan 7, 2013 at 7:21 AM, Sylvain Munaut s.mun...@whatever-company.com wrote: Hi, As far as I know relying on SCRIPT_URI is rather dangerous since it's not always there. There better should be an if/else-satement surrounding

Re: radosgw segfault in 0.56

2013-01-07 Thread Sylvain Munaut
Hi, Yeah, it's missing a guard here. Strange, I remember fixing this and others, but I can't find any trace of that. I think setting it to empty string is ok, though we may want to explore other fixes (configurable?) -- it affects the Location field in S3 POST response. Yes, I've seen it's

Re: radosgw segfault in 0.56

2013-01-07 Thread Yehuda Sadeh
On Mon, Jan 7, 2013 at 1:04 PM, Sylvain Munaut s.mun...@whatever-company.com wrote: Ok, I tracked this down ... I'm using lighttpd as a FastCGI front end and it doesn't set SCRIPT_URI environment. So the line 1123 in rgw/rgw_rest.cc : s-script_uri = s-env-get(SCRIPT_URI); Tries to

radosgw segfault in 0.56

2013-01-03 Thread Sylvain Munaut
Hi, I've just updated a test cluster to 0.56 and I'm getting a segfault when doing requests on radosgw : root@ceph /var/log/ceph # /usr/bin/radosgw -n client.radosgw.gateway -f *** Caught signal (Segmentation fault) ** in thread 7fee095f8700 ceph version 0.56

Re: radosgw segfault in 0.56

2013-01-03 Thread Lorieri
Hi Sylvain, happened to me using ubuntu packages. usually when you upgrade a package it calls all its dependencies, for ceph you have to update one by one. did you try that ? cheers On Thu, Jan 3, 2013 at 1:54 PM, Sylvain Munaut s.mun...@whatever-company.com wrote: Hi, I've just updated a