Skip to content
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

Volumes error on Rethinkdb 2.3.5 @macOS #37

Open
yicone opened this issue May 2, 2017 · 3 comments
Open

Volumes error on Rethinkdb 2.3.5 @macOS #37

yicone opened this issue May 2, 2017 · 3 comments

Comments

@yicone
Copy link

yicone commented May 2, 2017

Rethinkdb Service can't start when Container restarted.

docker-compose.yml

  rethinkdb:
    restart: always
    image: rethinkdb:latest
    ports:
      - 28015:28015
    volumes:
      - ./data:/data

LOGS:

Running rethinkdb 2.3.5~0jessie (GCC 4.9.2)...
Running on Linux 4.9.13-moby x86_64
Loading data from directory /data/rethinkdb_data
Listening for intracluster connections on port 29015
error: Failed I/O: we tried to read from behind the end of the file. Either the file got truncated, or there is a bug in RethinkDB.
error: Failed I/O: we tried to read from behind the end of the file. Either the file got truncated, or there is a bug in RethinkDB.
error: Failed I/O: we tried to read from behind the end of the file. Either the file got truncated, or there is a bug in RethinkDB.
Version: rethinkdb 2.3.5~0jessie (GCC 4.9.2)
error: Error in src/arch/types.cc at line 35:
error: I/O operation failed. (Invalid argument) (offset = 8388608, count = 1536)
error: Backtrace:
error: Tue May  2 10:05:46 2017

        1 [0xae7500]: backtrace_t::backtrace_t() at 0xae7500 (rethinkdb)
        2 [0xae7879]: format_backtrace(bool) at 0xae7879 (rethinkdb)
        3 [0xd9f6c3]: report_fatal_error(char const*, int, char const*, ...) at 0xd9f6c3 (rethinkdb)
        4 [0x9f688c]: linux_iocallback_t::on_io_failure(int, long, long) at 0x9f688c (rethinkdb)
        5 [0x9e6815]: thread_doer_t<std::_Bind<std::_Mem_fn<void (linux_iocallback_t::*)(int, long, long)> (linux_iocallback_t*, int, long, long)> >::on_thread_switch() at 0x9e6815 (rethinkdb)
        6 [0x9f61e8]: linux_message_hub_t::on_event(int) at 0x9f61e8 (rethinkdb)
        7 [0x9f3186]: epoll_event_queue_t::run() at 0x9f3186 (rethinkdb)
        8 [0x9f122d]: linux_thread_pool_t::start_thread(void*) at 0x9f122d (rethinkdb)
        9 [0x7f9490201064]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8064) [0x7f9490201064] at 0x7f9490201064 (/lib/x86_64-linux-gnu/libpthread.so.0)
        10 [0x7f948ff3662d]: clone+0x6d at 0x7f948ff3662d (/lib/x86_64-linux-gnu/libc.so.6)
 error: Exiting.

Docker version:

  • Docker version 17.03.1-ce, build c6d412e
  • docker-compose version 1.11.2, build dfed245

macOS version:

  • Sierra 10.12.3 (16D32)
@yicone
Copy link
Author

yicone commented May 11, 2017

There has been a very similar in the past,
rethinkdb/rethinkdb#6284

@doug-numetric
Copy link

doug-numetric commented Jun 27, 2017

I had the same issue. It was a corrupted table file. I had to rename each of the table files one at a time from (guid) to (guid).old until I could get rethink to start up again to find which file was corrupted. It would be nice to have the guid of the corrupted file in the error log - even better, the name of the table the file corresponds to.

@roppa
Copy link

roppa commented Sep 20, 2017

I had the same error. Fortunately there wasn't much data so I just deleted the mounted drive and started again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants