FOG Compatibility Test Failed
-
@Wayne-Workman I am using interface em2 (192.168.1.0) for FOG/DHCP management.
-
@techlover28 So are you specifying the correct interface during the FOG installation? the
em2interface? -
@Wayne-Workman Yes, I am.
* Here are the settings FOG will use: * Base Linux: Redhat * Detected Linux Distribution: CentOS * Server IP Address: 192.168.1.1 * Interface: em2 * Installation Type: Normal Server * Donate: 0 * Internationalization: 0 * Image Storage Location: /images * Using FOG DHCP: Yes * DHCP router Address: * DHCP DNS Address: -
I’ve forked the fogproject and added auxiliary code in case the IP or Subnet mask is missing - to hopefully solve your issue.
If you know how to use git, the project is here: https://github.com/wayneworkman/fogproject
Report back with your findings please, if it works we need to merge it to the main repo.
-
@Wayne-Workman I had installed FOG 1.2.0 earlier. It worked fine with DHCP. I observed the issue during upgrade to Trunk (I attempted to upgrade because I was facing issue with the RAID disk and Trunk has RAID drivers included).
If you know how to use git, the project is here: https://github.com/wayneworkman/fogproject
This link appears to be pointing to the download of Fog 1.2.0. Is it the updated version including RAID drivers?
-
@techlover28 It’s not pointing to 1.2.0.
-
@techlover28 Please update and try again, the changes I’ve made have been merged. Maybe it’s fixed now?
-
@Wayne-Workman Sorry I should have downloaded and installed it instead of just looking at the text. I have downloaded it and trying to install it now.
I am getting an error:
Setting up and starting DHCP Server…/lib/common/functions.sh: line 1705: 255.255.255.0: command not found
Failed!I think it should be something to do with GIT.
-
I am trying to make an understanding with GIT and going to try again installing version 6181 after setting GIT up.
-
@techlover28 No I think there is a fix needed that @Wayne-Workman can shoot up pretty soon!
In line 1705 instead of:
[[ -z $submask ]] && $( cidr2mask $(getCidr $interface))should be (I reckon):
[[ -z $submask ]] && $submask=$( cidr2mask $(getCidr $interface))You can edit this in your local files and test till you hear from Wayne.
-
@Sebastian-Roth I have edited functions.sh file - replaced 1705 line.
I am facing the same issue again.
Setting up and starting DHCP Server…/lib/common/functions.sh: line 1705: =255.255.255.0: command not found
Failed! -
Sorry! Should be (remove
$
[[ -z $submask ]] && submask=$( cidr2mask $(getCidr $interface))@george1421 You are absolutely right about people need to get enough sleep!
-
@Sebastian-Roth Thank you for the instant response.
I have edited it and removed the “$” symbol.
It has failed again.
Setting up and starting DHCP Server…Failed!
It seems that “dhcpd.conf” has the “option subnet-mask 255.255.255.0;” line in it. When I remove it, I am able to start the DHCPd service.
subnet 192.168.1.0 netmask 255.255.255.0{ option subnet-mask 255.255.255.0; range dynamic-bootp 192.168.1.253 192.168.1.254; default-lease-time 21600; max-lease-time 43200; -
I have that option in my config too. Does not cause an issue?! I can’t see what’s wrong with it.
-
@Sebastian-Roth I am not sure why it is causing the issue. When I remove it, DHCP service works, when I keep it, DHCP service does not come up.
May be because we are configuring mask (255.255.255.0) two times?
-
@techlover28 Please take a look at your syslog while having the option in place and restarting dhcpd. Do
tail -f /var/log/messageson one console and restart the service on another. See what error message comes up. -
@techlover28 That should not cause an issue, but I do note that in my dhcp configs there’s a space between netmask 255.255.255.0 and {
Might be irrelevant, but I’ve yet to see a valid config without that space.
-
@Quazz Thought about that too, but tested with and without space and it’s fine either way.
-
@Sebastian-Roth Ah! sorry. Behavior has changed from the previous versions. In previous version, it used to say “unrecognized command” or something (not sure about the exact errors) in messages.
But in the current version (6181), install.sh does fail on DHCP but not because of “options” thing. Should be something else. It doesn’t give the same error under messages which it used to in old version.
In fog_error_6181.log, we see this:
Shutting down dhcpd: ESC[60G[ESC[0;32m OK ESC[0;39m] Starting dhcpd: ESC[60G[ESC[0;32m OK ESC[0;39m] status: unrecognized serviceIn messages, we see this:
Feb 4 15:30:18 Phoenix dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file Feb 4 15:30:18 Phoenix dhcpd: Wrote 0 class decls to leases file. Feb 4 15:30:18 Phoenix dhcpd: Wrote 0 leases to leases file. Feb 4 15:30:18 Phoenix dhcpd: Listening on LPF/em2/f8:bc:12:3b:48:3d/192.168.1.0/24 Feb 4 15:30:18 Phoenix dhcpd: Sending on LPF/em2/f8:bc:12:3b:48:3d/192.168.1.0/24 Feb 4 15:30:18 Phoenix dhcpd: Feb 4 15:30:18 Phoenix dhcpd: No subnet declaration for em1 (10.201.6.176). Feb 4 15:30:18 Phoenix dhcpd: ** Ignoring requests on em1. If this is not what Feb 4 15:30:18 Phoenix dhcpd: you want, please write a subnet declaration Feb 4 15:30:18 Phoenix dhcpd: in your dhcpd.conf file for the network segment Feb 4 15:30:18 Phoenix dhcpd: to which interface em1 is attached. ** Feb 4 15:30:18 Phoenix dhcpd: Feb 4 15:30:18 Phoenix dhcpd: Sending on Socket/fallback/fallback-net Feb 4 15:35:50 Phoenix dhcpd: Internet Systems Consortium DHCP Server 4.1.1-P1 Feb 4 15:35:50 Phoenix dhcpd: Copyright 2004-2010 Internet Systems Consortium. Feb 4 15:35:50 Phoenix dhcpd: All rights reserved. Feb 4 15:35:50 Phoenix dhcpd: For info, please visit https://www.isc.org/software/dhcp/It appears to be a system specific issue. I should be able to get rid of it soon.
-
Is this with “option subnet-mask”?? Looks ok from the logs I reckon:
Feb 4 15:30:18 Phoenix dhcpd: Listening on LPF/em2/f8:bc:12:3b:48:3d/192.168.1.0/24 Feb 4 15:30:18 Phoenix dhcpd: Sending on LPF/em2/f8:bc:12:3b:48:3d/192.168.1.0/24
