Hello,
After we restart a pulp server, it receives hundreds of sync tasks. I
presume that they are kept in qpid, but I don't know how to check.
Even is we cancel all, after the next restart, we have the same problem:
hunderds of sync tasks and the pulp server useless for a few hours until
they fi
I have observed something like this, and reported it previously. I didn't
think about the tasks being stored in qpid.
I found that this spotted when I removed all my sync schedules.
Ben.
On 16 November 2015 8:39:03 pm Cristian Falcas wrote:
Hello,
After we restart a pulp server, it recei
Hello,
When trying to download modules from our local forge with puppet 3.8, the
returned code from pulp is 401:
# puppet module install --module_repository
http://$(hostname)/pulp_puppet/forge/repository/optymyze_puppet_forge
--config /dev/null --target-dir /tmp/qqw puppetlabs-stdlib --verbose -
- Original Message -
> Hello,
>
> When trying to download modules from our local forge with puppet 3.8, the
> returned code from pulp is 401:
I believe you can only use the latest client with Pulp 2.7.0. Which version of
pulp-server and pulp-puppet do you have installed?
-Dennis
>
> #
All sync jobs are now failing after upgrading from 2.6.4-1.
Nov 13 18:43:11 Updated: python-pulp-common-2.7.0-1.el6.noarch
Nov 13 18:43:12 Updated: python-pulp-puppet-common-2.7.0-1.el6.noarch
Nov 13 18:43:12 Updated: python-pulp-rpm-common-2.7.0-1.el6.noarch
Nov 13 18:43:12 Updated: python-gofer-
I forgot to mention that we have upgraded to 2.7
On Mon, Nov 16, 2015 at 5:11 PM, Dennis Kliban wrote:
> - Original Message -
> > Hello,
> >
> > When trying to download modules from our local forge with puppet 3.8, the
> > returned code from pulp is 401:
>
> I believe you can only use t
Hi Joel,
I too have been experiencing symptoms like this on my development
system. At the moment, we suspect an issue with either qpidd or the
python-qpid library. Unfortunately, we do not have any updates. In the
meantime you can try these two workaround:
0) Try restarting pulp_workers, pulp_res
Randy Barlow wrote:
> 0) Try restarting pulp_workers, pulp_resource_manager, and pulp_celerybeat.
I should mention that this is only a temporary fix, so if you go this
route you may find yourself needing to do this frequently.
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature
Hi Randy,
Here's what I've tried thus far.
1) for i in httpd qpidd pulp_celerybeat pulp_resource_manager pulp_workers;
do service $i restart; done
2) Downgrading to 2.6.4-1.el6
3) Reboot... what? This isn't Windows.
4) Turned up all logging to debug and can't see what's killing or making
pulp th
