https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-10-02T14:52:42ZPulpPulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=64432015-10-02T14:52:42Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=64492015-10-02T15:12:14Zbmbouterbmbouter@redhat.com
<ul></ul><p>I suspect this is only a problem for the init scripts (EL6) and not for EL7 (systemd). The init script daemonizes the pulp_resource_manager process, and the init script can't know if the spawned process has "connected correctly to the db" or not because the pulp_resource_manager process has a wait-and-continue behavior when connecting to the database. As such the spawned process will always be in the running state if it daemonized correctly and didn't experience a fatal exception.</p>
<p>Given that, I propose the init script returns exit code 0 immediately if the spawned process daemonizes correctly and is running, and 1 otherwise. The init script should return at some point in both cases.</p> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=64912015-10-05T18:02:48Zmhrivnakmhrivnak@redhat.com
<ul><li><strong>OS</strong> set to <i>RHEL 6</i></li></ul> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=75322015-12-21T19:08:27Zmhrivnakmhrivnak@redhat.com
<ul></ul><p>To reproduce with pulp, you should be able to</p>
<pre><code>service mongod stop
service pulp_resource_manager start
</code></pre> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=75502015-12-22T17:05:15Zpcreechpcreech@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>MODIFIED</i></li></ul><p>[root@localhost pulp_packaging]# service mongod stop<br>
Stopping mongod: [ OK ]<br>
[root@localhost pulp_packaging]# service pulp_resource_manager start<br>
celery init v10.0.<br>
Using config script: /etc/default/pulp_resource_manager<br>
celery multi v3.1.11 (Cipater)</p>
<blockquote>
<p>Starting nodes...</p>
</blockquote>
<p>> <a href="mailto:resource_manager@localhost.localdomain" class="email">resource_manager@localhost.localdomain</a>: OK<br>
[root@localhost pulp_packaging]#</p>
<p>Was not able to reproduce with latest build of pulp 2.8. It appears the work done in <a href="https://pulp.plan.io/issues/988" class="external">https://pulp.plan.io/issues/988</a> fixes the issue</p> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=75802015-12-23T16:22:07Zamacdona@redhat.comaustin@redhat.com
<ul><li><strong>Assignee</strong> set to <i>pcreech</i></li></ul> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=92232016-02-23T20:55:42Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li></ul> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=99752016-03-23T18:12:56Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Issue #1290: missing DB during boot causes resource manager to hanghttps://pulp.plan.io/issues/1290?journal_id=395332019-04-15T20:42:46Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>