• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Tasks do not start after upgrade to 1.0.1

Scheduled Pinned Locked Moved
FOG Problems
3
4
1.1k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K
    Koen
    last edited by Jun 5, 2014, 12:22 PM

    Hi

    I upgraded our Fog server to version 1.0.1. PXE boot did not work, I noticed that the tftpboot directory seemed to be missing files. The upgrade process seemed to have created a backup tftpboot.prev directory. So I restored the tftpboot to the prvious state. Now PXE-boot works fine, but tasks are not started. Tested on several computers. I have reverted to version 0.32 until I find a solution. Anyone has an idea?

    Thanks,

    Koen

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Jun 5, 2014, 12:27 PM

      DID YOU READ THE OUTPUT ON THE SCREEN?

      It tells you you need to change the Option 67 from pxelinux.0 to undionly.kpxe

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • K
        Koen
        last edited by Jun 10, 2014, 2:14 PM

        Hi Tom

        Sorry, I overlooked completely that option 67 had to get a different value, my fault.
        May be the install script can emphasize that this has to be changed in case of an update?

        All the best and thanks,

        Koen

        1 Reply Last reply Reply Quote 0
        • J
          Jaymes Driver Developer
          last edited by Jun 10, 2014, 2:50 PM

          [quote=“Koen, post: 29688, member: 4127”]Hi Tom

          Sorry, I overlooked completely that option 67 had to get a different value, my fault.
          May be the install script can emphasize that this has to be changed in case of an update?

          All the best and thanks,

          Koen[/quote]

          It um… it does.

          [code]
          echo " DHCP will NOT be setup but you must setup your";
          echo " current DHCP server to use FOG for PXE services.“;
          echo ;
          echo " On a Linux DHCP server you must set:”;
          echo " next-server";
          echo ;
          echo " On a Windows DHCP server you must set:“;
          echo " option 066 & 067”;
          echo;
          echo " Option 066 is the IP of the FOG Server: (e.g. ${ipaddres}“;
          echo " Option 067 is the undionly.kpxe file: (e.g. undionly.kpxe)”;
          [/code]

          This is a blatant rip from the installfog.sh script that you run to install FOG, for some reason many members fail to read the instructions presented to them.

          WARNING TO USERS: My comments are written completely devoid of emotion, do not mistake my concise to the point manner as a personal insult or attack.

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          1 / 1
          • First post
            3/4
            Last post

          224

          Online

          12.0k

          Users

          17.3k

          Topics

          155.2k

          Posts
          Copyright © 2012-2024 FOG Project