search

tmont / puppet-rethinkdb

Puppet module for rethinkdb
4 stars 5 forks source link

service rethinkdb restart doesn't work #2

Open timjrobinson opened 10 years ago

timjrobinson commented 10 years ago

I like the module but doing 'service rethinkdb restart' never works for me. Giving the following:

root@db-6:/var/lib/rethinkdb/instances.d/db-6# service rethinkdb restart
rethinkdb: db-6: The instance is not running (there is no pid file)
rethinkdb: db-6: Starting instance. (logging to `/var/lib/rethinkdb/instances.d/db-6/log_file')
Directory '/var/lib/rethinkdb/instances.d/db-6' is already in use, perhaps another instance of rethinkdb is using it.
root@db-6:/var/lib/rethinkdb/instances.d/db-6# ps ax | grep rethink
  524 ?        S      0:00 /usr/bin/rethinkdb --daemon --config-file /etc/rethinkdb/instances.d/db-6.conf --pid-file /var/run/rethinkdb/instances.d/db-6.pid
14047 pts/1    S+     0:00 grep --color=auto rethink
16973 ?        S      0:00 /usr/bin/rethinkdb --daemon --config-file /etc/rethinkdb/instances.d/db-6.conf --pid-file /var/run/rethinkdb/instances.d/db-6.pid
16974 ?        S      0:46 /usr/bin/rethinkdb --daemon --config-file /etc/rethinkdb/instances.d/db-6.conf --pid-file /var/run/rethinkdb/instances.d/db-6.pid
root@db-6:/var/lib/rethinkdb/instances.d/db-6#
tmont commented 10 years ago

Not really sure what would cause that. It looks like you have an instance running independent of the init.d service. You could try killing all of those processes and restarting it.

I don't really do anything with this module anymore, but I cracked it open again after seeing your ticket. I did some updates on it, so you could also try reinstalling the module (v0.1.0 on puppet forge: https://forge.puppetlabs.com/tmont/rethinkdb).

Apparently RethinkDB had deprecated their PPA at some point, and now you have to manually specify their repo. So that was really the only change I made.

timjrobinson commented 10 years ago

I could restart it after running 'pkill -9 rethinkdb' just thought I'd let you know as I was using default install and this happened. It could be because it's a 4 core machine and it's spawning an instance for each core but then not shutting them down when doing 'service rethinkdb stop'.

Thanks, I'll try updating to the newest version.

On Sun, Sep 21, 2014 at 9:57 AM, Tommy Montgomery notifications@github.com wrote:

Not really sure what would cause that. It looks like you have an instance running independent of the init.d service. You could try killing all of those processes and restarting it.

I don't really do anything with this module anymore, but I cracked it open again after seeing your ticket. I did some updates on it, so you could also try reinstalling the module (v0.1.0 on puppet forge: https://forge.puppetlabs.com/tmont/rethinkdb).

Apparently RethinkDB had deprecated their PPA at some point, and now you have to manually specify their repo. So that was really the only change I made.

— Reply to this email directly or view it on GitHub https://github.com/tmont/puppet-rethinkdb/issues/2#issuecomment-56284124 .

tmont commented 10 years ago

Hm, weird. Let me know if that problem persists. Unless rethinkdb is doing something super strange, it shouldn't be spawning more than one instance.