<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Slight correction: (in the middle of my email):<br>
<br>
I did grep <i class="moz-txt-slash"><strike><span
class="moz-txt-tag">/</span></strike><strike>var/log/httpd/ssl_access_log</strike>
<b>for my ta</b><b>sk</b><b>-id (</b></i><i class="moz-txt-slash"><b>f3a4a828-1a98-4d30-989f-a8f62acc29f9)</b>
in <i class="moz-txt-slash"><span class="moz-txt-tag">/</span>var/log<span
class="moz-txt-tag">/</span></i>* and /var/log<span
class="moz-txt-tag">/</span></i>*/*, but it only found it in
/var/log/httpd/ssl_access_log and /var/log/httpd/ssl_request_log
(lines like:
<br>
/var/log/httpd/ssl_access_log:135.1.215.52 - - [12/Apr/2016:15:04:17
-0500] "GET /pulp/api/v2/tasks/f3a4a828-1a98-4d30-989f-a8f62acc29f9/
HTTP/1.1" 200 579
<br>
<br>
regards,<br>
Paul<br>
<div class="moz-cite-prefix">On 04/12/2016 03:09 PM, EXT Paul Jochum
wrote:<br>
</div>
<blockquote cite="mid:570D55E4.9080706@nokia.com" type="cite">Hi
Brian:
<br>
<br>
I am running into the same problem of "waiting", so here are
my outputs (let me know if you need anything else):
<br>
<br>
-sh-4.1# pulp-admin -vv tasks details --task-id
f3a4a828-1a98-4d30-989f-a8f62acc29f9
<br>
+----------------------------------------------------------------------+
<br>
Task Details
<br>
+----------------------------------------------------------------------+
<br>
<br>
2016-04-12 14:59:46,539 - DEBUG - sending GET request to
/pulp/api/v2/tasks/f3a4a828-1a98-4d30-989f-a8f62acc29f9/
<br>
2016-04-12 14:59:46,602 - INFO - GET request to
/pulp/api/v2/tasks/f3a4a828-1a98-4d30-989f-a8f62acc29f9/ with
parameters None
<br>
2016-04-12 14:59:46,602 - INFO - Response status : 200
<br>
<br>
2016-04-12 14:59:46,602 - INFO - Response body :
<br>
{
<br>
"exception": null,
<br>
"task_type": "pulp.server.managers.repo.sync.sync",
<br>
"_href":
"/pulp/api/v2/tasks/f3a4a828-1a98-4d30-989f-a8f62acc29f9/",
<br>
"task_id": "f3a4a828-1a98-4d30-989f-a8f62acc29f9",
<br>
"tags": [
<br>
"pulp:repository:rhel-i386-server-optional-6.5.z-debuginfo",
<br>
"pulp:action:sync"
<br>
],
<br>
"finish_time": null,
<br>
"_ns": "task_status",
<br>
"start_time": null,
<br>
"traceback": null,
<br>
"spawned_tasks": [],
<br>
"progress_report": {},
<br>
"queue": "None.dq",
<br>
"state": "waiting",
<br>
"worker_name": null,
<br>
"result": null,
<br>
"error": null,
<br>
"_id": {
<br>
"$oid": "570d1727e75b4adec6bd0d58"
<br>
},
<br>
"id": "570d1727e75b4adec6bd0d58"
<br>
}
<br>
<br>
Operations: sync
<br>
Resources: rhel-i386-server-optional-6.5.z-debuginfo
(repository)
<br>
State: Waiting
<br>
Start Time: Unstarted
<br>
Finish Time: Incomplete
<br>
Result: Incomplete
<br>
Task Id: f3a4a828-1a98-4d30-989f-a8f62acc29f9
<br>
Progress Report:
<br>
<br>
<br>
-sh-4.1# ps -awfux | grep celery
<br>
Warning: bad syntax, perhaps a bogus '-'? See
/usr/share/doc/procps-3.2.8/FAQ
<br>
root 16147 0.0 0.0 6444 704 pts/2 S+ 15:01 0:00 \_
grep celery
<br>
apache 977 0.1 0.1 561608 25908 ? Sl Apr09 6:15
/usr/bin/python /usr/bin/celery beat
--app=pulp.server.async.celery_instance.celery
--scheduler=pulp.server.async.scheduler.Scheduler
--workdir=/var/run/pulp/ -f /var/log/pulp/celerybeat.log -l INFO
--detach --pidfile=/var/run/pulp/celerybeat.pid
<br>
apache 9558 0.0 0.4 553760 58972 ? Sl 10:40 0:05
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:resource_manager@lss-pulp01.ih.lucent.com">resource_manager@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO -Q resource_manager
--logfile=/var/log/pulp/resource_manager.log
--pidfile=/var/run/pulp/resource_manager.pid
<br>
apache 9602 0.4 0.3 472928 50512 ? Sl 10:40 1:16
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:resource_manager@lss-pulp01.ih.lucent.com">resource_manager@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO -Q resource_manager
--logfile=/var/log/pulp/resource_manager.log
--pidfile=/var/run/pulp/resource_manager.pid
<br>
apache 9792 0.0 0.4 553976 58924 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-0@lss-pulp01.ih.lucent.com">reserved_resource_worker-0@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-0.log
--pidfile=/var/run/pulp/reserved_resource_worker-0.pid
<br>
apache 9865 0.0 0.3 472916 49692 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-0@lss-pulp01.ih.lucent.com">reserved_resource_worker-0@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-0.log
--pidfile=/var/run/pulp/reserved_resource_worker-0.pid
<br>
apache 9807 0.0 0.4 553976 58920 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-1@lss-pulp01.ih.lucent.com">reserved_resource_worker-1@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-1.log
--pidfile=/var/run/pulp/reserved_resource_worker-1.pid
<br>
apache 9887 0.0 0.3 472916 49688 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-1@lss-pulp01.ih.lucent.com">reserved_resource_worker-1@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-1.log
--pidfile=/var/run/pulp/reserved_resource_worker-1.pid
<br>
apache 9826 0.0 0.4 553564 58896 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-2@lss-pulp01.ih.lucent.com">reserved_resource_worker-2@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-2.log
--pidfile=/var/run/pulp/reserved_resource_worker-2.pid
<br>
apache 9893 0.0 0.3 472924 49684 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-2@lss-pulp01.ih.lucent.com">reserved_resource_worker-2@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-2.log
--pidfile=/var/run/pulp/reserved_resource_worker-2.pid
<br>
apache 9847 0.0 0.4 553976 58912 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-3@lss-pulp01.ih.lucent.com">reserved_resource_worker-3@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-3.log
--pidfile=/var/run/pulp/reserved_resource_worker-3.pid
<br>
apache 9917 0.0 0.3 472916 49692 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-3@lss-pulp01.ih.lucent.com">reserved_resource_worker-3@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-3.log
--pidfile=/var/run/pulp/reserved_resource_worker-3.pid
<br>
apache 9871 0.0 0.4 553752 58896 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-4@lss-pulp01.ih.lucent.com">reserved_resource_worker-4@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-4.log
--pidfile=/var/run/pulp/reserved_resource_worker-4.pid
<br>
apache 9945 0.0 0.3 472920 49684 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-4@lss-pulp01.ih.lucent.com">reserved_resource_worker-4@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-4.log
--pidfile=/var/run/pulp/reserved_resource_worker-4.pid
<br>
apache 9896 0.0 0.4 553988 58932 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-5@lss-pulp01.ih.lucent.com">reserved_resource_worker-5@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-5.log
--pidfile=/var/run/pulp/reserved_resource_worker-5.pid
<br>
apache 9982 0.0 0.3 472924 49700 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-5@lss-pulp01.ih.lucent.com">reserved_resource_worker-5@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-5.log
--pidfile=/var/run/pulp/reserved_resource_worker-5.pid
<br>
apache 9918 0.0 0.4 553972 58916 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-6@lss-pulp01.ih.lucent.com">reserved_resource_worker-6@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-6.log
--pidfile=/var/run/pulp/reserved_resource_worker-6.pid
<br>
apache 9990 0.0 0.3 472912 49680 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-6@lss-pulp01.ih.lucent.com">reserved_resource_worker-6@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-6.log
--pidfile=/var/run/pulp/reserved_resource_worker-6.pid
<br>
apache 9940 0.0 0.4 553756 58892 ? Sl 10:41 0:06
/usr/bin/python -m celery.__main__ worker --heartbeat-interval=30
-c 1 -n <a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-7@lss-pulp01.ih.lucent.com">reserved_resource_worker-7@lss-pulp01.ih.lucent.com</a>
--events --app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-7.log
--pidfile=/var/run/pulp/reserved_resource_worker-7.pid
<br>
apache 10013 0.0 0.3 472920 49684 ? S 10:41 0:00
\_ /usr/bin/python -m celery.__main__ worker
--heartbeat-interval=30 -c 1 -n
<a class="moz-txt-link-abbreviated" href="mailto:reserved_resource_worker-7@lss-pulp01.ih.lucent.com">reserved_resource_worker-7@lss-pulp01.ih.lucent.com</a> --events
--app=pulp.server.async.app --loglevel=INFO
--logfile=/var/log/pulp/reserved_resource_worker-7.log
--pidfile=/var/run/pulp/reserved_resource_worker-7.pid
<br>
-sh-4.1#
<br>
<br>
<br>
I did grep /var/log/httpd/ssl_access_log in /var/log/* and
/var/log/*/*, but it only found it in
/var/log/httpd/ssl_access_log and /var/log/httpd/ssl_request_log
(lines like:
<br>
/var/log/httpd/ssl_access_log:135.1.215.52 - -
[12/Apr/2016:15:04:17 -0500] "GET
/pulp/api/v2/tasks/f3a4a828-1a98-4d30-989f-a8f62acc29f9/ HTTP/1.1"
200 579
<br>
<br>
<br>
-sh-4.1# rpm -q -a | grep -i pulp | sort
<br>
mod_wsgi-3.4-2.pulp.el6.x86_64
<br>
pulp-admin-client-2.8.1-1.el6.noarch
<br>
pulp-puppet-admin-extensions-2.8.1-1.el6.noarch
<br>
pulp-puppet-plugins-2.8.1-1.el6.noarch
<br>
pulp-rpm-admin-extensions-2.8.1-1.el6.noarch
<br>
pulp-rpm-plugins-2.8.1-1.el6.noarch
<br>
pulp-selinux-2.8.1-1.el6.noarch
<br>
pulp-server-2.8.1-1.el6.noarch
<br>
python-isodate-0.5.0-4.pulp.el6.noarch
<br>
python-kombu-3.0.33-4.pulp.el6.noarch
<br>
python-pulp-bindings-2.8.1-1.el6.noarch
<br>
python-pulp-client-lib-2.8.1-1.el6.noarch
<br>
python-pulp-common-2.8.1-1.el6.noarch
<br>
python-pulp-oid_validation-2.8.1-1.el6.noarch
<br>
python-pulp-puppet-common-2.8.1-1.el6.noarch
<br>
python-pulp-repoauth-2.8.1-1.el6.noarch
<br>
python-pulp-rpm-common-2.8.1-1.el6.noarch
<br>
<br>
<br>
-sh-4.1# uname -a
<br>
Linux lss-pulp01.ih.lucent.com 2.6.32-042stab113.21 #1 SMP Wed Mar
23 11:05:25 MSK 2016 x86_64 x86_64 x86_64 GNU/Linux
<br>
<br>
<br>
-sh-4.1# more /etc/*release*
<br>
::::::::::::::
<br>
/etc/redhat-release
<br>
::::::::::::::
<br>
Scientific Linux release 6.7 (Carbon)
<br>
::::::::::::::
<br>
/etc/system-release
<br>
::::::::::::::
<br>
Scientific Linux release 6.7 (Carbon)
<br>
::::::::::::::
<br>
/etc/system-release-cpe
<br>
::::::::::::::
<br>
cpe:/o:redhat:enterprise_linux:6.7:ga
<br>
-sh-4.1#
<br>
<br>
On 04/11/2016 03:32 PM, Brian Bouterse wrote:
<br>
<blockquote type="cite">To anyone who has a stuck task running
Pulp 2.6 or newer, can you open a
<br>
bug or e-mail the list with the following. The full output from:
<br>
<br>
pulp-admin -vv tasks details --task-id
<the_stuck_task_UUID>
<br>
<br>
Post the full output, but observe the value of "worker_name"
similar to
<br>
what was suggested here[0].
<br>
<br>
Can you also include the `sudo ps -awfux | grep celery` output
to show
<br>
your running process?
<br>
<br>
Also can you grep the logs for that UUID and include any lines
that you
<br>
see as output too.
<br>
<br>
[0]:
<a class="moz-txt-link-freetext" href="https://www.redhat.com/archives/pulp-list/2016-April/msg00026.html">https://www.redhat.com/archives/pulp-list/2016-April/msg00026.html</a>
<br>
<br>
Thanks,
<br>
Brian
<br>
<br>
<br>
On 04/11/2016 01:32 PM, Mihai Ibanescu wrote:
<br>
<blockquote type="cite">I have a similar problem on 2.7.1 with
rabbitmq.
<br>
<br>
Occasionally a task will get "lost":
<br>
<br>
pulp-admin tasks details --task-id
622041ac-e9e4-4a15-bd7c-7c98a17782e0
<br>
+----------------------------------------------------------------------+
<br>
Task Details
<br>
+----------------------------------------------------------------------+
<br>
<br>
Operations: publish
<br>
Resources: thirdparty-snapshot-rpm-latest (repository)
<br>
State: Waiting
<br>
Start Time: Unstarted
<br>
Finish Time: Incomplete
<br>
Result: Incomplete
<br>
Task Id: 622041ac-e9e4-4a15-bd7c-7c98a17782e0
<br>
Progress Report:
<br>
<br>
<br>
I have seen more than one getting in this state.
<br>
<br>
I can cancel the task, but I'd like to find out if I can
tickle
<br>
something to re-process the queue. Other tasks do get
correctly processed.
<br>
<br>
If there's something you would like me to do in order to debug
this
<br>
further, please let me know.
<br>
<br>
Thank you!
<br>
Mihai
<br>
<br>
On Fri, Apr 8, 2016 at 9:27 AM, Brian Bouterse
<<a class="moz-txt-link-abbreviated" href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:bbouters@redhat.com"><mailto:bbouters@redhat.com></a>> wrote:
<br>
<br>
There is a known issue [0] introduced in 2.8.0 which will
cause your
<br>
tasks to become stuck at waiting. This occurs after Pulp
runs normally
<br>
for hours or days.
<br>
<br>
A fix is completed but won't be released until Pulp 2.8.3
is released.
<br>
The good news is, you can resolve that issue now by
upgrading
<br>
python-kombu on your existing 2.8.0, 2.8.1, or 2.8.2
system. Manually
<br>
install python-kombu-3.0.33-5.pulp for your distro on
your system,
<br>
restart Pulp services and you'll be all set. All of the
links below come
<br>
out of the Pulp build system[1]
<br>
<br>
EL6: <a class="moz-txt-link-freetext" href="http://tinyurl.com/j5sy5zh">http://tinyurl.com/j5sy5zh</a>
<br>
EL7: <a class="moz-txt-link-freetext" href="http://tinyurl.com/jppwcdv">http://tinyurl.com/jppwcdv</a>
<br>
F22: <a class="moz-txt-link-freetext" href="http://tinyurl.com/hp7z4sq">http://tinyurl.com/hp7z4sq</a>
<br>
F23: <a class="moz-txt-link-freetext" href="http://tinyurl.com/zplzua3">http://tinyurl.com/zplzua3</a>
<br>
F24: update is in -testing repo [2]
<br>
rawhide: already available in stable
<br>
<br>
These are the same versions of python-kombu that you'll
receive when
<br>
2.8.3 comes out so upgrading this package will keep your
packages on the
<br>
normal upgrade path. These newer python-kombu versions
are compatible
<br>
with 2.8.0, 2.8.1, and 2.8.2 versions of Pulp.
<br>
<br>
[0]: <a class="moz-txt-link-freetext" href="https://pulp.plan.io/issues/1801">https://pulp.plan.io/issues/1801</a>
<br>
[1]:
<a class="moz-txt-link-freetext" href="http://koji.katello.org/koji/packageinfo?packageID=665">http://koji.katello.org/koji/packageinfo?packageID=665</a>
<br>
[2]:
<a class="moz-txt-link-freetext" href="https://bodhi.fedoraproject.org/updates/FEDORA-2016-ec038bbf19">https://bodhi.fedoraproject.org/updates/FEDORA-2016-ec038bbf19</a>
<br>
<br>
-Brian
<br>
<br>
_______________________________________________
<br>
Pulp-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a> <a class="moz-txt-link-rfc2396E" href="mailto:Pulp-list@redhat.com"><mailto:Pulp-list@redhat.com></a>
<br>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-list">https://www.redhat.com/mailman/listinfo/pulp-list</a>
<br>
<br>
<br>
</blockquote>
_______________________________________________
<br>
Pulp-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-list">https://www.redhat.com/mailman/listinfo/pulp-list</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
Pulp-list mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Pulp-list@redhat.com">Pulp-list@redhat.com</a>
<br>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/pulp-list">https://www.redhat.com/mailman/listinfo/pulp-list</a>
<br>
</blockquote>
<br>
</body>
</html>