• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. techlover28
    T
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 33
    • Best 1
    • Controversial 0
    • Groups 0

    techlover28

    @techlover28

    1
    Reputation
    682
    Profile views
    33
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    techlover28 Unfollow Follow

    Best posts made by techlover28

    • RE: FOG Compatibility Test 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
      
      posted in Hardware Compatibility
      T
      techlover28

    Latest posts made by techlover28

    • RE: FOG Compatibility Test Failed

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

      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

      @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";
          }
      }
      
      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

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

      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

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

      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

      @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;
      
      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

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

      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

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

      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

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

      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

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

      posted in Hardware Compatibility
      T
      techlover28
    • RE: FOG Compatibility Test Failed

      @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: 
      
      posted in Hardware Compatibility
      T
      techlover28