FOG Compatibility Test Failed

[techlover28]

@Tom-Elliott I have done the “svn up”, below is the output:

# svn up
   A    .gitignore
   U    lib/common/functions.sh
   .
   .
   U    packages/web/lib/fog/group.class.php
   Updated to revision 4752.

But the install.sh script failed again at the same place (Setting up and starting DHCP Server…Failed!).

[Wayne Workman]

@techlover28 Ok so, you have many interfaces.

What network do you want FOG to serve DHCP to? The 192.168.1.0 network or the 10.201.0.0 network?

[techlover28]

@Wayne-Workman I am using interface em2 (192.168.1.0) for FOG/DHCP management.

[Wayne Workman]

@techlover28 So are you specifying the correct interface during the FOG installation? the em2 interface?

[techlover28]

@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: 

[Wayne Workman]

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.

[techlover28]

@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?

[Wayne Workman]

@techlover28 It’s not pointing to 1.2.0.

[Wayne Workman]

@techlover28 Please update and try again, the changes I’ve made have been merged. Maybe it’s fixed now?

[techlover28]

@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.

[techlover28]

I am trying to make an understanding with GIT and going to try again installing version 6181 after setting GIT up.

[Sebastian Roth]

@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.

[techlover28]

@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!

[Sebastian Roth]

Sorry! Should be (remove $

            [[ -z $submask ]] && submask=$( cidr2mask $(getCidr $interface))

@george1421 You are absolutely right about people need to get enough sleep!

[techlover28]

@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;

[Sebastian Roth]

I have that option in my config too. Does not cause an issue?! I can’t see what’s wrong with it.

[techlover28]

@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?

[Sebastian Roth]

@techlover28 Please take a look at your syslog while having the option in place and restarting dhcpd. Do tail -f /var/log/messages on one console and restart the service on another. See what error message comes up.

[Quazz]

@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.

[Sebastian Roth]

@Quazz Thought about that too, but tested with and without space and it’s fine either way.