Seg fault when using a ppp connection about rethinkdb HOT 7 CLOSED

I figured out the cause. I was on a ppp connection (mobile boradband). Once I switch back to wi-fi it started fine.

from rethinkdb.

Interesting, we'll see if we can reproduce this and find out where the crash came from.

from rethinkdb.

@gkamal -- thanks for the bug report. We'll still look at this, because the server should never ever crash, even under unusual conditions.

from rethinkdb.

I had a similar thing -- though the traceback looks different.

error: Error in http/http.cc at line 37:
error: Guarantee failed: [size > 0 && _val[0] == resource_parts_sep_char[0]] resource path must start with a '/'
error: Backtrace:
error: Sat Nov 10 03:41:16 2012

   1: rethinkdb() [0x76ed71]
   2: rethinkdb() [0x76f951]
   3: rethinkdb() [0x8916d8]
   4: rethinkdb() [0x89567a]
   5: rethinkdb() [0x89697a]
   6: rethinkdb() [0x897112]
   7: rethinkdb() [0x79b232]
   8: rethinkdb() [0x79064e]

error: Exiting.
Crashing while already crashed. Printing error message to stderr.
Segmentation fault from reading the address (nil).[1814] worker: Couldn't read job function: end-of-file received
[1814] worker: Failed to accept job, quitting.
[1804] worker: Couldn't read job function: end-of-file received
[1803] worker: Couldn't read job function: end-of-file received
[1804] worker: Failed to accept job, quitting.
[1810] worker: Couldn't read job function: end-of-file received
[1818] worker: Couldn't read job function: end-of-file received
[1803] worker: Failed to accept job, quitting.
[1810] worker: Failed to accept job, quitting.
[1813] worker: Couldn't read job function: end-of-file received
[1818] worker: Failed to accept job, quitting.
[1813] worker: Failed to accept job, quitting.
[1805] worker: Couldn't read job function: end-of-file received
[1805] worker: Failed to accept job, quitting.
[1819] worker: Couldn't read job function: end-of-file received
[1815] worker: Couldn't read job function: end-of-file received
[1808] worker: Couldn't read job function: end-of-file received
[1815] worker: Failed to accept job, quitting.
[1819] worker: Failed to accept job, quitting.
[1808] worker: Failed to accept job, quitting.
[1809] worker: Couldn't read job function: end-of-file received
[1806] worker: Couldn't read job function: end-of-file received
[1809] worker: Failed to accept job, quitting.
[1816] worker: Couldn't read job function: end-of-file received
[1807] worker: Couldn't read job function: end-of-file received
[1816] worker: Failed to accept job, quitting.
[1807] worker: Failed to accept job, quitting.
[1817] worker: Couldn't read job function: end-of-file received
[1820] worker: Couldn't read job function: end-of-file received
[1817] worker: Failed to accept job, quitting.
[1820] worker: Failed to accept job, quitting.
[1811] worker: Couldn't read job function: end-of-file received
[1812] worker: Couldn't read job function: end-of-file received
[1806] worker: Failed to accept job, quitting.
[1811] worker: Failed to accept job, quitting.
[1812] worker: Failed to accept job, quitting.
Trace/breakpoint trap

I'm running on ubuntu the python client is pumping data into rethinkdb.
On the same machine, no networking involved.

Can provide more details if needed.

from rethinkdb.

@vikram -- thanks for the bug report. This looks like a very different issue, could you move your report into a new one, and we'll discuss it there? Also, have you been pointing the web browser at the http connection of the server, or you just got the error with only a server and a client?

from rethinkdb.

This could very well be the same issue as #18, so I'd like to know if it's still reproducible with the latest version (1.2.5).

from rethinkdb.

I tested after upgrading to 1.2.5 the problem doesn't occur any more.

from rethinkdb.