Re: ceph was didn't stop.

[Tommi Virtanen <tv@inktank.com>]

On Wed, Jun 27, 2012 at 10:05 PM, ramu <ramu.freesystems@gmail.com> wrote:
> + ssh gamma cd /etc/ceph ; ulimit -c unlimited ; while [ 1 ]; do
>        [ -e /var/run/ceph/osd.1.pid ] || break
>        pid=`cat /var/run/ceph/osd.1.pid`
>        while [ -e /proc/$pid ] && grep -q ceph-osd /proc/$pid/cmdline ; do
>            cmd="kill  $pid"
>            echo -n $cmd...
>            $cmd
>            sleep 1
>            continue
>        done
>        break
>    done

Well, if that didn't do it (and I don't see the "echo -n $cmd..."
output anywhere, so if was most likely false), then it's highly likely
the PID file has gone missing or is corrupt. This is a classic failure
mode of sysvinit style self-daemonizing and PID file handling. Kill
the process manually for now, and let us know of this keeps happening;
right now "somebody rm -rf /var/run/ceph" is as good a guess as any.

This is one of the reasons why I advocate upstart/runit/etc, and why
the "new style" of deployment uses upstart.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html