• Fog Replicator error to storage node

    Unsolved
    7
    0 Votes
    7 Posts
    3k Views
    george1421G

    @scouseboy99 Just to be clear here, you built two complete FOG servers and then assigned one as a master node and one as a slave node? If this is the case you have a non-standard setup. There are valid reasons for setting up this configuration and it does work well with one caveat.

    The typical setup would be to setup the remote server as a FOG storage node from the installer. A fog storage node is a full fog server but without a local database. In this configuration the storage node uses the database from the master node so its aware of all images that is replicated to itself.

    In your setup you have two independant FOG databases. The replicator will still copy the images from the master node to the remote fog node just like with a remote storage node. The problem comes is that there is no (current) way for the master fog server to update the database on the remote fog server. There is a way to manage this. You can export the image definitions from the master FOG server and then manually import them into the remote fog server to synchronize the image definitions in the remote database. It sounds a bit complicated, but its not. You just have to remember if you add a new image to the master node, the image WILL be replicated to the remote fog server, you just need to manually add/import the image definition into the remote fog server’s database.

  • FTP Login Error on Upload to Fog Server

    Solved
    9
    0 Votes
    9 Posts
    3k Views
    Tom ElliottT

    A reinstall helped correct the problem with the password.

  • Database Schema Installer / Updater

    Solved
    4
    0 Votes
    4 Posts
    1k Views
    D

    I just started over with a fresh db and imported hosts from old environment. No need to look into the issue any further unless someone else has it.

  • "Snapin hash does not exist"

    Unsolved
    9
    0 Votes
    9 Posts
    3k Views
    Wayne WorkmanW

    @thopman 1.3.5 RC 3 was released today, if you wanted to try that out. Otherwise you can wait for the official 1.3.5 release.

  • New storage node - sync not working

    Solved
    5
    0 Votes
    5 Posts
    2k Views
    Jaymes DriverJ

    @Tony-Ayre

    Thank you very much, This may help someone in the future with a similar issue 😉

    I appreciate you taking the time to explain your issue and your resolution!

  • When Pushbullet plugin active wrong login to webif takes 2 minutes (timeout)

    Moved Solved
    5
    0 Votes
    5 Posts
    1k Views
    Tom ElliottT

    Moved to “FOG Problems”.

  • FOG 1.3.3 Kernel Update - Unable to contact server

    Solved
    15
    0 Votes
    15 Posts
    7k Views
    george1421G

    @Lenain I can’t understand how/why this is a fix. I’m going to update my prod instance fro 1.3.4 and see if I can duplicate it. I’m currently on 1.3.3.

  • PXE-E53: No Boot File Received

    15
    0 Votes
    15 Posts
    7k Views
    S

    @jamcdonald120 said:

    if we assume that the DHCP setting of the router are correct (they worked before) …

    I am sure I have heard phrases like this more than a hundred times and it quite often turns out …

    Asking the web to see what other things could cause this issue I see that the error message you posted is not quite the same most other people report - which is: PXE-E53: No boot Filename received (see the difference between ‘File’ and ‘Filename’?). Your positive test of trying to load the undionly.kpxe (how do you know your server is using this file and not ipxe.kpxe which we also use sometimes?) binary file makes me believe that your TFTP and the files on it are fine. This would emphasize even more that something is wrong with the DHCP! The message essentially says: “I got an answer from a DHCP server but no information on what file to load for PXE booting”.

    You need to understand that DHCP is always a bit of an issue. This is because even if neither you nor any colleague changed the “original” DHCP server you can still run into problems if someone added another DHCP server answering requests in your network.

    Please try this: Make one of your clients ready for turn on and PXE boot. Install and run tcpdump - a tool to capture network traffic - on your FOG server.

    sudo -i apt-get install tcpdump tcpdump -w /tmp/dhcp_traffic.pcap port 67 or port 68 or port 69 or port 4111

    Leave that command as is and start up the client till you see the error message on screen. Then stop the tcpdump command (Ctrl-c) and upload that packet dump file (/tmp/dhcp_traffic.pcap) from your server to the forum here.

  • Client system will not load pxe image

    Solved
    22
    0 Votes
    22 Posts
    11k Views
    Tom ElliottT

    @rbasart Well, that certainly could do it I suppose.

    As far as it “partially” working, the switch IS the IP address, and FOG had “listeners” on that IP.

    As the switch received the data, the FOG Server would perk up as well.

    Glad you figured it out for sure there. Sorry I didn’t recognize this, but hey one more thing to “look” for.

  • Error Booting Samsung Style S20

    Solved
    10
    0 Votes
    10 Posts
    4k Views
    S

    how i mark solved?

  • This topic is deleted!

    Unsolved
    0
    0 Votes
    0 Posts
    22 Views
    No one has replied
  • can't access to my Fog web interface

    Unsolved
    3
    0 Votes
    3 Posts
    5k Views
    Wayne WorkmanW

    Sounds like your hdd might be full. You can check with df -h look for partitions with 99% or 100% use.

    In addition to what Jaymes asked below, also look through your apache error logs.

  • Debian + svn = error

    Solved
    9
    0 Votes
    9 Posts
    4k Views
    Jaymes DriverJ

    @craigcoulson said in Debian + svn = error:

    nevermind all - i rebuilt the server with only minimal packages and re-ran the svn install of Fog and it worked fine - go figure.

    Glad to hear you got it working 😉

  • FOG fails to upload image after Debian was updated

    Solved
    6
    0 Votes
    6 Posts
    2k Views
    Jaymes DriverJ

    @Tom-Elliott This, this is why we love you.

  • FOG - get machine to join domain.

    5
    0 Votes
    5 Posts
    2k Views
    Wayne WorkmanW

    @dloudon96 Is 10.31.97.240 your fog server’s address? What OS is the fog server running? What version of FOG?

  • Cannot Mount /Dev/SDA3 - Sysprep & Imaging Issue

    Unsolved
    5
    0 Votes
    5 Posts
    2k Views
    Jaymes DriverJ

    @RobTitian16 Thank you for your reply.

    Did you build your Windows 10 image from scratch or are you using a modified version of the pre-installed os?

    You could try wiping the drive of all partitions, adding a blank one and imaging again. We have had trouble with partitions on the disk that were put there as a factory recovery point. (I know Dell, HP, etc are known for having a recovery partition).

  • Fresh install FOG 1.3.4 on Ubuntu Server 16.04.1 LTS Fails

    Unsolved
    5
    0 Votes
    5 Posts
    2k Views
    Wayne WorkmanW

    @psyfer9983 After changing the OS’s addressing & dns and gateway and such, the tool in here called updateIP will change all the needed spots for FOG’s files. https://github.com/FOGProject/fog-community-scripts

    It will also re-write dhcpd.conf properly if the box is configured to do dhcp - and will do so correctly even for up to 4 interfaces on one system.

  • Fresh Install FOG 1.3.4 white / blank Management Site

    Unsolved
    6
    0 Votes
    6 Posts
    3k Views
    Tom ElliottT

    @MotD If you’re trying to set a password you can do it right from the installer with:

    snmysqlpass='SomePasswordHere' ./installfog.sh -y

  • FOG Image Replication questions

    5
    0 Votes
    5 Posts
    2k Views
    FallingWaxF

    @Wayne-Workman Good point. Thanks for your help

  • TFTP service - Unit Not Found

    Unsolved
    3
    0 Votes
    3 Posts
    3k Views
    Wayne WorkmanW

    @taflad said in TFTP service - Unit Not Found:

    , I tried to restart the tftp servic.e However, I get “failed to start tftp.service: unit not found”

    The service should be called xinetd and not tftp.

    Also this might help:
    https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

84

Online

12.7k

Users

17.6k

Topics

156.5k

Posts