Issue #1202 ยป Issue #5923 - 2015-08-27T14_51_22Z.eml

rbarlow, 08/27/2015 04:51 PM

Return-Path: <>
Received: from ([]) by running ExIM with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1ZUyWJ-0000JY-1l; Thu, 27 Aug 2015 16:51:15 +0200
Received: from ([]) by ( with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) id 1ZUyWI-0007B1-4s for; Thu, 27 Aug 2015 16:51:14 +0200
Received: from ( []) by (Postfix) with ESMTPS id 314CCC15CA8A for <>; Thu, 27 Aug 2015 14:51:11 +0000
Received: from ( []) by (8.14.4/8.14.4) with ESMTP id t7REpAF9016975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <>; Thu, 27 Aug 2015 10:51:10 -0400
Date: Thu, 27 Aug 2015 10:51:10 -0400
From: Randy Barlow <>
To: Pulp <>
Message-ID: <>
In-Reply-To: <>
References: <>
Subject: Re: [Pulp - Issue #1202] pulp_celerybeat,pulp_resource_manager fail
to start on boot
Mime-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable
Delivery-date: Thu, 27 Aug 2015 16:51:15 +0200
X-Enigmail-Draft-Status: N1110
Organization: Red Hat, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
X-Scanned-By: MIMEDefang 2.68 on
X-HE-Spam-Level: ----------
X-HE-Spam-Score: -10.0
X-HE-Spam-Report: Content analysis details: (-10.0 points) pts rule name
description ---- ----------------------
-------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL:
Sender listed at, high trust [ listed in] -5.0 PGP_MESSAGE RAW: Contains a PGP signed or encrypted

On 08/21/2015 03:53 PM, Pulp wrote:
> A newer version of Pulp (iirc 2.7.0 beta+) will keep these pids on a
> local folder and not in the /var/lib/pulp. Even still, I think it would=

> be good to have all Pulp services wait until the network is started. I
> think we should propogate the units change to all of our units files.
> =

> @rbarlow, what do you think?

For the network services I think this is a reasonable suggestion, though
I don't believe it will solve any issues that people might be
experiencing since our Celery code will keep attempting to connect to
its network dependencies until it is able. Thus, even without doing this
everything will work. I would say it's the "right thing", though I also
don't think it'll change anyone's experiences with Pulp in a noticeable w=

For the remote-fs, there's a way to add a symlink under /etc/systemd to
indicate that you want a service to start after another one. Since the
remote-fs is system-dependent (i.e., not everybody is hosting
/var/lib/pulp in NFS), I think this would be the way to go. I don't
recall the exact way to do this, but I believe you can learn about it her=

-- =

Randy Barlow