Bug 699247

Summary:	up-imapproxy does not fork to the background
Product:	[Fedora] Fedora EPEL	Reporter:	Jeroen van Meeuwen <vanmeeuwen+fedora>
Component:	up-imapproxy	Assignee:	Tim Jackson <rpm>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	el5	CC:	jeff, manuel.wolfshant, rpandit, rpm
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-09 19:41:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jeroen van Meeuwen 2011-04-24 15:59:14 UTC

Description of problem:

Upon starting the imapproxy service, up-imapproxy's init script does not fork imapproxy to the background

Version-Release number of selected component (if applicable):

up-imapproxy-1.2.6-1.el5

How reproducible:

Every time

Steps to Reproduce:
1. Install up-imapproxy
2. Configure if necessary
3. # /sbin/service imapproxy start
  
Actual results:

Does not return to the command-line and "hangs" indefinitely.

Expected results:

Return to cli

Additional info:

Comment 1 Tim Jackson 2011-07-31 18:45:06 UTC

I strongly suspect there is something about your environment or configuration that is causing it to hang, rather than a fault in the init script (since it's pretty straightforward). Have you discussed the problem on the imapproxy mailing list?

Comment 2 Jeroen van Meeuwen 2011-08-01 00:53:10 UTC

Could you elaborate on what kind of environment / system setting would / could be of influence on what I consider to be a clean install?

I have contacted the original author, Dave McMurtrie, as he's somewhat closeby given that I'm the release engineer for Cyrus IMAP and Cyrus SASL.

Thanks.

Comment 3 Tim Jackson 2011-08-01 17:17:28 UTC

I can't suggest anything specific assuming that you've eliminated things such as any firewalls that could be blocking the proxy startup when it tries to connect out. It's just that the package has been around for a while and there's nothing unusual in the init script (all it does is "daemon /usr/sbin/in.imapproxyd"), and it isn't reproducible for me on a clean install. Is there anything special you need to do to reproduce it?

Comment 4 Tim Jackson 2011-10-09 19:41:34 UTC

Works for me. If you still have this problem, please consider seeking help on
the upstream mailing list, and if it turns out to be a problem with the
packaging then please re-open this bug.