[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Pulp-list] gofer hogging CPU



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/14/2011 11:45 AM, Jeff Ortel wrote:
> All,
> 
> Looks like gofer is pegging the CPU after it's been running for while. 
> I'm profiling now but in the meantime, restart the goferd service as a
> workaround.
> 
> -jeff

Not sure if it's related, but I just ran into the WSGI process crashing
after the server was running for about an hour. I typed before I thought
and I restarted httpd before dumping the threads. But my pulp.log was
spammed with the following, so keep an eye out for that as well:

      2011-03-14 10:09:08,062 [INFO][MainThread] connect() @
broker.py:74 - connecting:
      {localhost:5672}:
      transport=TCP
      host=localhost
      port=5672
      cacert=/etc/pki/qpid/ca/ca.crt
      clientcert=/etc/pki/qpid/client/client.pem



- -- 
Jay Dobies
RHCE# 805008743336126
Freenode: jdob
http://pulpproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNfjhZAAoJEOMmcTqOSQHCtLoIAKPdJVJUxaQZ/HKaTp9p43Ww
IgIpikRs58p5g0v8LWUNa+GFk95aJWz2tDEAlflFnTjlcGODvJvr7GhSR/x260PW
ooJ0amWIt8tGtzs5TWPEgjOQn5QxnGwFxK6dpXVZB+g5vJ6UsN87oL07gpTjzKow
bIlSJtve9PAQPHRISyl9wacJFaFhatYzJ4j4tKletCMi4ATaC2DxPUwDHUCLJKnP
4zkV/cYVcxecLr8fGlaoVQDjtQA0hzgzASKkgx0jUHs/HhAS3BRFCpQ2crNF5Z80
7Jto1qvS7SrPfxG72Bw+VW1hx5KKZZng0oA/AjGbyahyIWIqZ3Igvjb6Dv67t7s=
=8T0e
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]