Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with include config file in config file? #76

Closed
rafalsc opened this issue Dec 6, 2016 · 2 comments
Closed

Problem with include config file in config file? #76

rafalsc opened this issue Dec 6, 2016 · 2 comments

Comments

@rafalsc
Copy link

rafalsc commented Dec 6, 2016

Hi all,

I have started to use this cookbook and I can generate all my configs but when Chef tries to restart ISC-DHCP-Server on Debian I see this error:

Dec 06 10:03:07 isc-dhcp-server[26717]: /etc/dhcp/dhcpd.conf line 33: /etc/dhcp/shared_networks.d/vlan20_stack4.conf: bad parse.
Dec 06 10:03:07 isc-dhcp-server[26717]: include /etc/dhcp/shared_networks.d/vlan20_stack4.conf"

In dhcp.conf I have:
include "/etc/dhcp/shared_networks.d/vlan20_stack4.conf";

and in this file I have normal config like:

shared-network vlan20_stack4 { subnet 10.11.1.0 netmask 255.255.254.0 { pool { range 10.11.1.100 10.11.2.254; } option subnet-mask 255.255.254.0; option default-lease-time 86400; option deny unknown-clients; option max-lease-time 604800; option ntp-servers 10.10.0.1; option routers 10.11.98.1; } }

I use Jessie and last stable version of DHCP Server. I'm not using data_bags for networks etc. I have everything in my cookbook/recipes/default.rb

Thank you for any suggestions why is like that.

Best,
Rafal

@damacus
Copy link
Member

damacus commented May 9, 2019

Closing due to inactivity.

If this is still an issue please reopen or open another issue. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help!

Thanks,
Sous-Chefs

@damacus damacus closed this as completed May 9, 2019
@lock
Copy link

lock bot commented Jun 8, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants