-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guarantee failed: [size > 0 && _val[0] == resource_parts_sep_char[0]] resource path must start with a '/' Edit #40
Comments
This maybe shouldn't be a guarantee since it seems to not like the http On Sunday, November 11, 2012, Michel wrote:
|
My faith in software is restored! I have a sane backtrace (from 1.2.5 precise):
|
So, I have a fix that does something smarter than failing a guarantee at http://newton:8080/ui#review:id=60 . Unfortunately I don't know how to track down whatever made the bad request. @neumino -- if I push the guarantee fix, do you think you could find the source of the request? |
Euh, I'm not sure to understand what you are talking about. Are you refering to these warnings
If yes, I just did a little more testing. The warnings appear only when I'm doing a request to /ajax/stats (I did request this page manually). Also I get some "errors" in /ajax/stats like for example
A little more about my server
Changing the chmod didn't solve the problem (I added rwx for everyone - and I did restart the server). |
Ah, I see, I was confused about the scope of the problem. The problem I was addressing was the guarantee fail that resulted in a crash. We now fail to parse the tcp message if the path is malformed rather than failing a guarantee. The next question is "what was sending the malformed path?", but if you were point to /ajax/stats by hand maybe you just mistyped. I'll work on the proc/net/dev stuff. |
The web ui triggers the same warnings. If I don't have a web ui opened, I don't get any warnings. |
The guarantee failure and the warnings are two separate problems I think. If the web UI is causing the guarantee to fail, it's sending a malformed path and needs to be fixed; if the web UI is causing these /proc/net/dev warnings, that's something we need to fix on the server. |
About the guarantee failure, I got a second crash two days ago, but this time I almost certain that I didn't have a web ui opened. About the warnings, the web UI is causing the /proc/net/dev warnings. |
So, theoretically the call to |
So, here's the current state of this bug:
@jdoliner -- I seem to remember you knowing something about the perfmons. Is there any chance you'd be willing to take this bug, or alternately pair program it with me so that I learn how the perfmons work? |
I still get the warnings about /proc/net/dev after an update. I can give you access to my server tomorrow. It's probably going to be easier that way. |
Alright, I think I know the root of the /proc/net problem. It looks like you're running a kernel with grsecurity patches, which prevents non-root users from reading /proc/net by default. There's theoretically a configuration option CONFIG_GRKERNSEC_PROC_USER somewhere that controls this, but I didn't want to start messing around with your server config. @srh - OS X doesn't have /proc at all, right? What are we planning to do for the port? Maybe we should just do that by default and solve this problem for people with hardened kernels. That just leaves the perfmon stuff, which I'd like to talk to @jdoliner about. I'll try to wake up earlier tomorrow and do that. |
What's the state of affairs here? It looks like the original bug has been fixed, in which case we should probably create a new one for /proc stuff (if that's still an issue). |
The guarantee failure is (I think) fixed. The /proc stuff will be fixed as a natural consequence of the OS X port. The weird perfmon stuff I need to talk to Joe about, but yeah, maybe it should be in a new issue. |
@mlucy -- what's the state of affairs here? As far as I understand, we should close this and create a new perfmon-related issue (though I'm not sure what we can do about that if we don't have permissions, other than perhaps giving a better warning message and referring to gsecurity). |
I think we should close this and make a new issue. On Mon, Nov 19, 2012 at 2:20 PM, coffeemug notifications@github.com wrote:
|
No objections to closing and reopening. The perfmon problem is the:
stuff @neumino was talking about, which seems to happen for me even when we can read from /proc. |
Ok! Could you close this one and open a new one? |
@mlucy could you reference the commit that fixes this? Or a commit in which this is definitely fixed if no single commit exists? |
On a fresh ubuntu 12.04 install (not on a vm). I got a crash
I got tons of warnings before
rethinkdb --version returns "rethinkdb"...
I was built from ppa this morning, not from source.
The text was updated successfully, but these errors were encountered: