-
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
Specify that encryptfs doesn't work in the error message #18
Comments
Hmm I think we're going to probably need to get a core dump here to do On Saturday, November 10, 2012, Justin wrote:
|
It's on ext3. |
I think A backtrace + core file from that unstripped binary would make debugging much easier. You can run |
Could one cause of this be if the user's home directory is ecryptfs (which is available as a default option on Ubuntu)? I got a similar error on Ubuntu 11.10 (it printed different output - below - so not sure if it's actually the same error, but it had the same ultimate symptom that the initial The error I got:
|
Yep, rethink doesn't work on encrypted volumes (there isn't anything we can do about it -- you can't run with direct io on encrypt fs). We'd still appreciate a core file for the original bug so we can exit with a meaningful error message. |
I tried installing
|
Sorry about that. The unstripped binaries in Debian dbg packages are not exectutable. (We do not know why.) If you run the main binary in gdb, you ought to get a meaningful backtrace if symbols are installed. |
So, the file at /usr/lib/debug/usr/bin/rethinkdb is a symbol file, not an executable. You can specify it in gdb using It's pretty important that this symbol file is the result of the same build of rethinkdb, or none of the symbols will make sense. I don't think we have a symbol file for the version that the original stack trace in this issue came from, so if you could produce one with the latest released version, that would help. |
Here's a core dump: http://dl.dropbox.com/u/12108749/core.28866 I have no idea if the symbols match, I just used the provided symbol file above. |
So, the symbols I'm getting back in the backtrace don't make much sense, but the one at the top of the stack could very well have segfaulted:
where int addr_res = getifaddrs(&if_addrs);
guarantee_err(addr_res == 0, "getifaddrs failed, could not determine local ip addresses");
for (ifaddrs *p = if_addrs; p != NULL; p = p->ifa_next) {
>>> if (p->ifa_addr->sa_family == AF_INET) {
if (!(p->ifa_flags & IFF_LOOPBACK)) { We were assuming that I fixed this in commit f872a0b, and it should be published soon. |
Ok, version 1.2.5 is up, and should have the fix I just mentioned. Let me know if this is still reproducible. |
Ok, the only thing that remains to be done here is to clarify the error message to include encrypted file systems. If other bugs pop up, we'll open a new issue. Assigning to self. |
Um...not sure why the title of this issue was changed? I never said I was using an encrypted file system. I am seeing a different problem now, so I guess this is fixed. |
Sorry, I may have confused the issue by posting mine here (which was caused by ecryptfs). |
Yes, I think multiple posts confused it a little bit. @presidentbeef -- the issue you've been experiencing has been fixed. Try running sudo apt-get update, sudo apt-get upgrade rethinkdb. If you encounter it again, please open another issue. |
As for making the error message mentioning encrypted file systems, we are waiting on @wmrowan to finish a code review. |
This is fixed in next. |
Installed per directions, and ran
rethinkdb
:This is on Ubuntu 12.04 LTS (GNU/Linux 2.6.32-316-ec2 x86_64)
The text was updated successfully, but these errors were encountered: