@Wayne-Workman I believe that would be a right thing to do.

@Sebastian-Roth @Sebastian-Roth Yes it is with “option subnet-mask”. But install.sh is still failing.

A quick question, do “ldap” errors won’t affect the working of DHCP? I can ignore it then.

@Quazz Please find the output below:

 # dhcpd -t -cf /etc/dhcp/dhcpd.conf
Internet Systems Consortium DHCP Server 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file

@Wayne-Workman Please find the complete DHCPd.conf below:

# DHCP Server Configuration file\n#see /usr/share/doc/dhcp*/dhcpd.conf.sample
# This file was created by FOG
#Definition of PXE-specific options
# Code 1: Multicast IP Address of bootfile
# Code 2: UDP Port that client should monitor for MTFTP Responses
# Code 3: UDP Port that MTFTP servers are using to listen for MTFTP requests
# Code 4: Number of seconds a client must listen for activity before trying
#         to start a new MTFTP transfer
# Code 5: Number of seconds a client must listen before trying to restart
#         a MTFTP transfer
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16;
use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 192.168.1.1;
# Specify subnet of ether device you do NOT want service.
# For systems with two or more ethernet devices.
# subnet 136.165.0.0 netmask 255.255.0.0 {}
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;
    class "UEFI-32-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
        filename "i386-efi/ipxe.efi";
    }
    class "UEFI-32-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
        filename "i386-efi/ipxe.efi";
    }
    class "UEFI-64-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
        filename "ipxe.efi";
    }
    class "UEFI-64-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
        filename "ipxe.efi";
    }
    class "UEFI-64-3" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
        filename "ipxe.efi";
    }
    class "Legacy" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
        filename "undionly.kkpxe";
    }
}

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

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

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

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

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

@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 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 am using interface em2 (192.168.1.0) for FOG/DHCP management.

@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 Thank you for your response.

I am using version 6134 (as written on a cloud on FOG management page). Please let me know where I can download latest Trunk.

Please find the output of said command below (I am using interface em2 for FOG/DHCP management):

  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
    valid_lft forever preferred_lft forever
 2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether f8:bc:12:3b:48:3c brd ff:ff:ff:ff:ff:ff
    inet 10.201.6.176/16 brd 10.201.255.255 scope global em1
    inet6 2001:ac9:101:3e9:fabc:12ff:fe3b:483c/64 scope global dynamic 
    valid_lft 2591952sec preferred_lft 604752sec
    inet6 fe80::fabc:12ff:fe3b:483c/64 scope link 
    valid_lft forever preferred_lft forever
3: em2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether f8:bc:12:3b:48:3d brd ff:ff:ff:ff:ff:ff
   ** inet 192.168.1.1/24 brd 192.168.1.255 scope global em2**
    inet6 fe80::fabc:12ff:fe3b:483d/64 scope link 
    valid_lft forever preferred_lft forever
4: em3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether f8:bc:12:3b:48:3e brd ff:ff:ff:ff:ff:ff
5: em4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether f8:bc:12:3b:48:3f brd ff:ff:ff:ff:ff:ff

@Tom-Elliott I re-tried installing Trunk from scratch after removing-reinstalling DHCP and VSFTPD RPMs.

It got stuck at same place again (Setting up and starting DHCP Server…Failed!).

Attaching logs for reference. 1_1454387019861_foginstall.log 0_1454387019861_fog_error_6134.log

It is not able to start the DHCP service, therefore I manually configured it and re-executed the installfog.sh script. Script overwrites the configuration and fails.

My manual configuration which let DHCP service to start:

   subnet 192.168.1.0 netmask 255.255.255.0 {
   # option subnet-mask ;
    range dynamic-bootp 192.168.1.10 192.168.1.100;
    default-lease-time 21600;
    max-lease-time 43200;
    #       option domain-name-servers      x.x.x.x; 
    #       option routers      x.x.x.x;
    filename "undionly.kpxe";
    }

Script configuration which does NOT let DHCP service to start:

    subnet 0.0.0.0 netmask  {
    option subnet-mask ;
    range dynamic-bootp 0.0.0.253 192.168.1.254;
    default-lease-time 21600;
    max-lease-time 43200;
    #       option domain-name-servers      x.x.x.x; 
    #       option routers      x.x.x.x;
    filename "undionly.kpxe";
    }

@Tom-Elliott said:

@techlover28 please use the file provided as is. I don’t know what is or isn’t included in all the comments and what not. The only guess I have is from the before commenting part in which I’m guessing you want fog to be the dhcp server?

Yes, I want fog to be dhcp.

I have attached the commented installfog.sh file (trunk). As the upgrade failed at the point where it was setting up DHCP, so just thought if commenting some part of script could avoid complete re-installation.

0_1454379388299_installfog.sh

@Tom-Elliott said:

@techlover28 you commented the lines in installfog.sh that sources the config.sh files as well.

No, sorry forgot to tell. I started commenting the file after two source files (config.sh and functions.sh) lines.

hi,

I rebuild the FOG server today and was able to move further on upgrade. This time it got stuck here:

====================================================================================
Downloading inits, kernels, and the fog client…OK
Comparing checksums of kernels and inits…Done
Enabling apache and fpm services on boot…OK
Creating SSL CA…OK
Creating SSL Private Key…OK
Creating SSL Certificate…OK
Creating auth pub key and cert…OK
Resetting SSL Permissions…OK
Setting up SSL FOG Server…OK
Restarting Apache2 for fog vhost…OK
Changing permissions on apache log files…OK
Backing up database…OK

You still need to install/update your database schema.
This can be done by opening a web browser and going to:

http://192.168.1.1/fog/management

Press [Enter] key when database is updated/installed.

Setting up storage…OK
Setting up and starting DHCP Server…Failed!

So I reconfigured the DHCP server and restarted its service manually with success.

Then I commented entire “installfog.sh” script for Trunk except last few lines where it executes all the functions like “configureDHCP” etc.

I executed “installfog.sh” again and it shows me below (everytime below is shown now with the commented “installfog.sh” script):

====================================================================================

• Setting up storage…OK
• Setting up and starting DHCP Server…Skipped
• Setting up and starting TFTP and PXE Servers…/lib/common/functions.sh: line 432: : No such file or directory
  OK
• Setting up and starting VSFTP Server…/lib/common/functions.sh: line 373: : No such file or directory
  OK
• Setting up FOG Snapins…OK
• Setting up UDPCast…OK
• Configuring UDPCast…OK
• Building UDPCast…OK
• Installing UDPCast…OK
• Installing FOG System Scripts…Failed!
  ====================================================================================

@Sebastian-Roth said:

Well wget and curl do kind of the same thing but they are still different tools. Have you tried using the command I posted? Because curl is used in the installer script. And I thought it would be a good idea to test exactly what is going on when you run the installer (which failed when downloading kernel/init/fog client).

Yes, I tried the command. It successfully downloaded a bzImage file under /tmp directory with size 6883968 bytes.
The download kernel part failed on the 2nd attempt, first attempt was successful which later got stuck at “Backing up database”.

Adding RAID drivers which are not included in the official kernel source is kind of a huge effort. We would need to keep those updated and tested. How are we going to do this not having that hardware at home.
On the other hand you can just try following the kernel compile wiki articles to build your own custom kernel. We are more than happy to help if you run into a problem with this.

I will surely give it a try, starting Monday.

The NIC is a bit of a mystery to me. Should be I350-AM4 (quad port) if I got this correct from the mainboard manual. Those should be supported by driver ‘igb’ in old and new kernels! http://cateee.net/lkddb/web-lkddb/IGB.html

Yes, you are correct. Please find more information below:

– ethtool -i eth0

driver: igb
version: 3.2.10-k
firmware-version: 1.4-8
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes

[[modules:composer.user_said_in, @george1421, FOG Compatibility Test Failed]]

@techlover28 Yes that is the same. That is sad the newer kernels work not good.

Ah! yes, that is sad.

Maybe if you make a nice donation to the @Developers they would add your network driver and raid card to the FOG boot kernels

I earn $12000 (minus income tax) an year, not ashamed to tell it . Giving the fact that developers are so much helping and friendly, I was already thinking about giving a donation (not a nice amount but good percentage of my monthly income). Not that I am generous, but thankful for the help and support I have been getting instantly.

It looks like you may have to build your own kernel to get these specific drivers to work

I will try it and hope it goes well. If it doesn’t work, I may have to move to some other solution as I am under pressure to finish this task soon.

@george1421 said:

Actually this is what I was going to have the OP do to update the kernel without having to upgrade to the trunk (even though the trunk is a good choice)

@Sebastian-Roth said:

Well then try (test-)downloading the kernel by hand and see what happens: curl -ko "/tmp/bzImage" https://fogproject.org/kernels/bzImage

Does above mean similar to below post?

@george1421 said:

@techlover28 OK then, If you navigate to your web servers base directory (usually /var/www/html or /var/html) and then go to <www_base_dir>/fog/service/ipxe/ and rename bzImage and bzImage32 to bzImage.old and bzImage32.old

Then run the following commands to download the latest kernels
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32

From there reboot your target device to load in the newest kernels. If something breaks with this target or any other ones, just roll back the changes you made to load the old kernels.

If yes, then it didn’t work last time when I tried. I can try again though.

@techlover28 said:

I have tried it (newer version of kernel) today. It says “Network - Fail” along with “Disk - Fail”. Older version of bzImage works with Network therefore as you mentioned, I did the rollback.