Bug 190379

Summary: dnsmasq doesn't start
Product: [Fedora] Fedora Reporter: JM <igeorgex>
Component: dnsmasqAssignee: Jima <jima>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: extras-qa
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 2.30-4.2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-01 23:29:01 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 JM 2006-05-01 20:16:46 UTC
The version

dnsmasq-2.30-3.fc5.x86_64.rpm

is broken. I can't start it, I get always the message:

May  1 22:18:38 neo dnsmasq: ISC dhcpd integration not available: set
HAVE_ISC_READER in src/config.h
May  1 22:18:38 neo dnsmasq: FAILED to start up

Comment 1 Werner Hoelzl 2006-05-01 21:38:19 UTC
(In reply to comment #0)
> The version
> 
> dnsmasq-2.30-3.fc5.x86_64.rpm
> 
> is broken. I can't start it, I get always the message:
> 
> May  1 22:18:38 neo dnsmasq: ISC dhcpd integration not available: set
> HAVE_ISC_READER in src/config.h
> May  1 22:18:38 neo dnsmasq: FAILED to start up

The same problem occurs with FC4.

Comment 2 Jima 2006-05-01 23:29:01 UTC
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=189775#c5 ; that
message refers to a deprecated feature.  You need to configure dhcp-range and
dhcp-leasefile in /etc/dnsmasq.conf.

Upstream has been notified of this.

Marking as duplicate (otherwise NOTABUG).

*** This bug has been marked as a duplicate of 189775 ***

Comment 3 JM 2006-05-02 00:24:21 UTC
I don't use DHCPD from dnsmasq but I have to configure a dhcp-range and a
dhcp-leasefile? Btw. the default /etc/dnsmasq.conf has no dhcp-range and a
dhcp-leasefile as default in the config file.

Comment 4 Jima 2006-05-02 16:49:42 UTC
The problem was found to be the init script from upstream.  I've patched around
the issue and am releasing dnsmasq-2.30-4.2 to resolve this bug.