Bug 1012907 - handle_reply_fetch: Unable to find stored AMQP message
Summary: handle_reply_fetch: Unable to find stored AMQP message
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: condor-low-latency
Version: 2.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: grid-maint-list
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 11:07 UTC by Martin Kudlej
Modified: 2016-05-26 19:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-26 19:33:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Kudlej 2013-09-27 11:07:37 UTC
Description of problem:

Sometime there is error in CaroLog:
ERROR: handle_reply_fetch: Unable to find stored AMQP message with AMQPID "X"

and job is not processed as usually.

Version-Release number of selected component (if applicable):
condor-7.8.9-0.5
condor-aviary-7.8.9-0.5
condor-classads-7.8.9-0.5
condor-debuginfo-7.8.9-0.5
condor-job-hooks-1.5-6
condor-kbdd-7.8.9-0.5
condor-low-latency-1.2-3
condor-qmf-7.8.9-0.5
condor-vm-gahp-7.8.9-0.5
condor-wallaby-base-db-1.25-1
condor-wallaby-tools-5.0.5-2
python-condorutils-1.5-6
python-qpid-0.18-5
python-qpid-qmf-0.18-18
qpid-cpp-client-0.18-17
qpid-cpp-client-devel-0.18-17
qpid-cpp-client-devel-docs-0.18-17
qpid-cpp-client-rdma-0.18-17
qpid-cpp-client-ssl-0.18-17
qpid-cpp-server-0.18-17
qpid-cpp-server-cluster-0.18-17
qpid-cpp-server-devel-0.18-17
qpid-cpp-server-rdma-0.18-17
qpid-cpp-server-ssl-0.18-17
qpid-cpp-server-store-0.18-17
qpid-cpp-server-xml-0.18-17
qpid-java-client-0.18-8
qpid-java-common-0.18-8
qpid-java-example-0.18-8
qpid-jca-0.18-8
qpid-jca-xarecovery-0.18-8
qpid-qmf-0.18-18
qpid-qmf-devel-0.18-18
qpid-tests-0.18-2
qpid-tools-0.18-10
ruby-condor-wallaby-5.0.5-2
ruby-qpid-0.7.946106-2
ruby-qpid-qmf-0.18-18

How reproducible:
~5%

Steps to Reproduce:
1. install messaging, condor pool + low latency
2. run simple low latency jobs

Actual results:
There is error in CaroLog and jobs are not processed as they should
be.

Expected results:
There is no error in CaroLog and jobs are processed as they should
be.

Comment 3 Anne-Louise Tangring 2016-05-26 19:33:04 UTC
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.


Note You need to log in before you can comment on or make changes to this bug.