Bug 849130

Summary:	cntlm started too early
Product:	[Fedora] Fedora	Reporter:	Jens- Birger Schlie <external.jens-birger.schlie>
Component:	cntlm	Assignee:	Matt Domsch <matt_domsch>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	17	CC:	egon.rath, external.jens-birger.schlie, matt_domsch, paniraja_km
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	650079	Environment:
Last Closed:	2013-08-01 03:38:02 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jens- Birger Schlie 2012-08-17 11:54:41 UTC

+++ This bug was initially created as a clone of Bug #650079 +++

Description of problem:

cntlm is started too early so it's not able to resolve the configured proxy and dies. This problem only occurs when the given proxy is resolved using DNS.

When started after the system has come up using "service cntlmd start" it works flawless.

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

cntlm 0.92


How reproducible:

Install cntlm package and configure a proxy (using DNS name, no IP or /etc/hosts resolved name)
 
Actual results:

service failed to start up at boot time

Expected results:

service starts successfully

Additional info:

Same symptoms, similar log as in 650079 orig. Will provide more details; there is the same problem with network manager and cntlm and upstart start order on ubuntu 12.

Comment 1 Jens- Birger Schlie 2012-10-01 11:44:31 UTC

Issue is solved @debian / ubuntu. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686368

There is an upstream fix for this and other errors as cntlm version 0.92.3 available. 

See: http://www.awk.cz/svn/revision.php?repname=Cntlm&rev=280

Can s.o. pack 0.92.3 as rpm package?

Yours, 

Jens

Comment 2 Fedora End Of Life 2013-07-04 00:11:15 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2013-08-01 03:38:05 UTC

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.