Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1179199

Summary: rhcert server to listener connection gets broken abruptly
Product: Red Hat Certification Program Reporter: Anshul Behl <abehl>
Component: redhat-certificationAssignee: Greg Nichols <gnichols>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Anshul Behl <abehl>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0CC: abehl, brose
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-09 13:14:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anshul Behl 2015-01-06 12:30:32 UTC 
Version-Release number of selected component (if applicable):
rhcert version 1.0, release 20141124

How reproducible:
Occasionally

Steps to Reproduce:
Many times the connection to the listener machine stops and Hosts tab in the machine shows "timed out" message.

I checked that the server and listener were both running at the time and below is the stdout from listener.

opened task in file
Finished test run 1 for 10
10.65.213.161 - - [30/Dec/2014 04:35:16] "POST /RPC2 HTTP/1.1" 200 -
10.65.213.161 - - [30/Dec/2014 04:35:16] "POST /RPC2 HTTP/1.1" 200 -
10.65.213.161 - - [30/Dec/2014 04:35:16] "POST /RPC2 HTTP/1.1" 200 -
10.65.213.161 - - [30/Dec/2014 04:35:16] "POST /RPC2 HTTP/1.1" 200 -
10.65.213.161 - - [30/Dec/2014 04:35:16] "POST /RPC2 HTTP/1.1" 200 -
10.65.213.161 - - [30/Dec/2014 04:35:16] "POST /RPC2 HTTP/1.1" 200 -
10.65.213.161 - - [30/Dec/2014 04:35:16] "POST /RPC2 HTTP/1.1" 200 -
in ServerMessage.run
calling addJob

Expected results:
Connection should not time out
Comment 1 Greg Nichols 2015-01-06 14:35:45 UTC 
From the logging, it looks like a request came in, which the listener handled by adding a job to the queue.   It was probably hung here because the daemon process failed (crashed or hung).   What is the state of the daemon process when this happens?
Comment 2 Greg Nichols 2015-01-06 14:45:39 UTC 
Also, note that you can run both processes in forground by using "rhcert-backend server listener" on one shell, and "rhcert-backend server daemon" in another, so you'll see console logging on both processes.
Comment 3 Red Hat Bugzilla 2023-09-14 02:52:59 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days