Pascal,
We've seen similar behavior in testing and have always failed to track down
the cause. Nothing is actually running in Riak, but the process still just
hangs around. I filed an issue for this
https://github.com/basho/riak/issues/330. Coincidentally on the
erlang-bugs mailing list someone just reported a similar problem with
shutdown. I am going to try the suggestion provided on erlang-bugs and get
the change into our upcoming 1.4 release.
Thanks for the message and sorry no one got back to you sooner.
-Jared
On Tue, May 7, 2013 at 2:09 AM, Pascal Schmiel <
pascal.schm...@bluelionmobile.com> wrote:
> Hi List,
>
> sometimes the riak init script hangs on the "stop" command. After several
> hours the init script and the riak process itself is still running (but
> unreachable). I have to use SIGTERM to stop the process.
>
> The lines from my console.log after invoking "/etc/init.d/riak stop" are:
>
>
> 2013-05-07 01:08:54.624 [info] <0.1307.0>@riak_kv_app:prep_**stop:165
> Stopping application riak_kv - marked service down.
> 2013-05-07 01:08:54.624 [info] <0.1307.0>@riak_kv_app:prep_**stop:169
> Unregistered pb services
> 2013-05-07 01:08:54.625 [info] <0.1307.0>@riak_kv_app:prep_**stop:174
> unregistered webmachine routes
> 2013-05-07 01:08:54.625 [info] <0.1307.0>@riak_kv_app:prep_**stop:176 all
> active put FSMs completed
> 2013-05-07 01:08:54.634 [info] <0.1346.0>@riak_kv_js_vm:**terminate:240
> Spidermonkey VM (pool: riak_kv_js_hook) host stopping (<0.1346.0>)
> 2013-05-07 01:08:54.635 [info] <0.1307.0>@riak_kv_app:stop:**187 Stopped
> application riak_kv.
> 2013-05-07 01:08:54.651 [info] <0.129.0>@riak_core_app:prep_**stop:101
> Stopping application riak_core - disabling web services.
> 2013-05-07 01:08:54.733 [error] <0.23337.1>@riak_kv_stat:**update:85
> error:badarg updating stat {vnode_index_delete,0}.
> 2013-05-07 01:08:54.748 [error] <0.12920.2>@riak_kv_stat:**update:85
> error:badarg updating stat {vnode_index_delete,0}.
> 2013-05-07 01:08:54.769 [error] <0.27391.2>@riak_kv_stat:**update:85
> error:badarg updating stat {vnode_index_delete,0}.
> 2013-05-07 01:08:54.777 [error] <0.24922.3>@riak_kv_stat:**update:85
> error:badarg updating stat {vnode_index_delete,0}.
> 2013-05-07 01:08:54.780 [error] <0.27478.3>@riak_kv_stat:**update:85
> error:badarg updating stat {vnode_index_delete,0}.
> 2013-05-07 01:08:54.784 [error] <0.23385.2>@riak_kv_stat:**update:85
> error:badarg updating stat {vnode_index_delete,0}.
> 2013-05-07 01:08:57.294 [info] <0.129.0>@riak_core_app:stop:**110 Stopped
> application riak_core.
> 2013-05-07 01:08:57.459 [info] <0.55.0> alarm_handler:
> {clear,system_memory_high_**watermark}
>
> The problem appeared suddenly without any config or system changes.
>
> We're using Riak 1.3 installed from RPM on CentOS 6.3 x64 with eleveldb
> backend.
>
> - Pascal
>
>
> --
> Pascal Schmiel
> Head of System Operations
> Blue Lion mobile GmbH (QEEP)
> Gottfried-Hagen-Str. 20
> 51105 Köln
>
> Tel. +49 (0) 221 788 797 17
> Fax. +49 (0) 221 788 797 19
>
> pascal.schmiel@bluelionmobile.**com <pascal.schm...@bluelionmobile.com>
> www.bluelionmobile.com
> www.qeep.net
>
> Sitz Köln, HRB 58203, Amtsgericht Köln
> Geschäftsführung: Cornelius Rost, Christian R. Schulte
>
> ______________________________**_________________
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/**mailman/listinfo/riak-users_**lists.basho.com<http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com>
>
_______________________________________________
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
