• No Network Boot Option in BIOS

    Unsolved
    10
    0 Votes
    10 Posts
    4k Views
    S

    I think Quazz is right. I was trying “sudo dnsmasq” to troubleshoot. Sorry - am very new to Linux. I think this issue is resolved, though PXE is not working, but I’ll ask about that in a new thread. For anyone reading about this issue, the steps in here will help set up dnsmasq, and answered my question.

  • Directories under /var/www/html not showing after upgrade to 1.4

    Solved
    7
    0 Votes
    7 Posts
    2k Views
    Tom ElliottT

    @Thiago I think that’s what I needed to know.

    If you need the directory listing, you might be better creating an index.php file that will generate the list of files for you.

    You can even make them links so you could test downloads.

    The idea is we use an API now and if the index file doesn’t exist (which it’s attempting to locate) it will attempt to redirect through the API. I just needed clarity on whether there was an actual issue of which you just let us know there wasn’t. It was just your “testing” that was failing (which is helpful, but not requried).

  • Problem with Fog 1.3.5 install-- Setting up and Starting MySql...........FAILED! :(

    Solved
    22
    0 Votes
    22 Posts
    9k Views
    Tom ElliottT

    @safari2010 On screen where it’s giving the long warning, please say yes.

  • Problems with fog homepage

    Solved
    21
    0 Votes
    21 Posts
    9k Views
    KnightRavenK

    @zln1996
    That’s awesome! Glad to hear you got it working. I figured that directory under run would have been created automatically when starting the process. How interesting. Good job and glad all is intact. Glad we were able to get you in the right direction.

    Jason

  • problem to join domain active directory

    Solved
    3
    0 Votes
    3 Posts
    2k Views
    A

    Hello,

    I’d like to close the topic. It was the solution.

    Where is the button “solved” ?

    Thanks.

  • problems Loading Windows iso in advanced menu.

    Solved
    32
    0 Votes
    32 Posts
    23k Views
    R

    Hello guys.

    Finally, with wimboot systems work fine in all computer.

    This was the code:

    #!ipxe cpuid --ext 29 && set arch amd64 || set arch x86 kernel http://${fog-ip}/iso/asus/133/wimboot initrd http://${fog-ip}/iso/asus/133/BOOT/BCD BCD initrd http://${fog-ip}/iso/asus/133/BOOT/BOOT.SDI boot.sdi initrd -n boot.wim http://${fog-ip}/iso/asus/133/SOURCES/BOOT.WIM boot.wim boot

    Thank all, a lot.

  • Fog Image Import Issue

    Solved
    5
    0 Votes
    5 Posts
    2k Views
    Wayne WorkmanW

    Sticking this link here for future readers:
    https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

  • snapin and batch script

    Unsolved
    54
    0 Votes
    54 Posts
    32k Views
    Wayne WorkmanW

    @plegrand psexec already has the ability to send commands to remote machines, I’m not sure why you would try to make psexec commands into fog snapins.

    This whole thread seems really over-complicated.

    Why not just bake-in some run-once functionality into your image? Windows already does this natively via the registry. Doing it for Linux images is trivial because SystemD is amazing.

  • General Errors - Seeking Guidance after a Migration

    Unsolved
    3
    0 Votes
    3 Posts
    2k Views
    KnightRavenK

    @ttrammell
    It looks like something similar when I had changed the IP and didn’t finish configuring everything. I had left out checking and configuring the Storage group/nodes.
    If you have changed your IP(or maybe even Server name) try following these instructions:
    https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
    The key part I missed(becasue I didn’t really use storage nodes) was:

    Update the IP address for the storage node on the FOG system where you changed the IP address - Web Interface -> Storage Management
    Make sure you actually click the node and check the IP setting.

    that line in the bandwith.php file points to a location in /sys/class/net/<net_adapter_name>/operstate

    I’m not sure if CentOS is diferent but my adapter name is eth0 so look for that in place of adapter name.
    Im not sure if you can simply recreate it it if it doesn’t exist. It simply appears to display whether or not your adapter is up or not.

    I also found this article but refers more to the fog client install.
    https://forums.fogproject.org/topic/5926/change-fog-server-name

    Hope that helps,
    Jason

  • User cannot join Multicast Session - Invalid Login

    Solved
    8
    0 Votes
    8 Posts
    3k Views
    sudburrS

    < facepalm >

    Oh geez … okay, ignore everything. There is no problem other than that the switch servicing that bench had been reprogrammed. The ports used had been set to the wrong vlan; a vlan serviced by a FOG server that didn’t have the intended accounts.

    … oy

  • IPXE Issues

    15
    0 Votes
    15 Posts
    4k Views
    Wayne WorkmanW

    @jaoyer said in IPXE Issues:

    As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?

    Yes.

  • Pending MAC addresses

    4
    0 Votes
    4 Posts
    1k Views
    PsycholiquidP

    @Tom-Elliott Changed teh memory_Limit in PHP made all the difference. Thanks man.

  • Mounting /images/dev Permission Denied

    Unsolved
    67
    0 Votes
    67 Posts
    40k Views
    Tom ElliottT

    @vkenny The second element. (Single data store/server, 5 different nodes pointing essentially at the exact same spot.)

  • Installation issue after upgrade 1.4.0RC9.3 to 1.4.0 Release

    Unsolved
    3
    0 Votes
    3 Posts
    1k Views
    A

    No updates of the system have been performed, and FOG is the only software in use on this system. I’ve had zero issues upgrading all along from 1.3 through various RC releases as they come out and onward to this final 1.4.0 release. This is the first time I’ve seen a failed message during an upgrade.

    Specifically the error log shows:
    “update-rc.d: error: cannot find a LSB script for FOGMulticastManager”

    I was able to bypass the issue by grabbing the init.d scripts out of the packages folder, and manually placing them into /etc/init.d following with a chmod +x. Once those scripts were copied into init.d the foginstaller script moved along nicely.

  • Compatibility optiplex 7050 test Network Fail

    3
    0 Votes
    3 Posts
    1k Views
    george1421G

    You’ll also want to update if that 7050 was purchased with an NVMe drive. FOG 1.2.0 doesn’t support NVMe drives or Win10 very well.

  • Authentication Error

    Unsolved
    16
    0 Votes
    16 Posts
    5k Views
    Wayne WorkmanW

    @Joe-Gill look in the .fogsettings file and see if there is a password set for the mysql one.

  • Backing up database failed!

    Solved
    7
    0 Votes
    7 Posts
    3k Views
    Raymond BellR

    ISSUE RESOLVED By following this

    TLDR; Rerun the fog installer if you have lost “Database Connectivity” to your fog server, or run the ALTER USER syntax shown below.

    So Ubuntu 16, among others I suppose, enable a “security updates” to be applied automatically as a “default” to things. Why, well it makes it simpler to ensure your Ubuntu systems are in compliance and patched for any potential exploits. This causes unknown and unexpected issues.

    I figured it’d be a safe thing to express that there could be problems (as many of you have already experienced) that when these updates go up (with or without your knowledge) it can break functionality in unexpected and inopportune ways.

    The quickest fix is to simply rerun the fog installer which should correct the problem.

    As a note, it seems this problem is specific only when the mysql account is the ‘root’ user AND the password is blank.

    The “fix” if you must do it manually is to open a terminal and obtain root:
    Super (Windows Key) + T then sudo -i (in most cases).

    From there, open mysql with mysql -u root

    NOTE: MySQL MUST be run with ROOT.

    Run:

    ALTER USER ‘root’@‘127.0.0.1’ IDENTIFIED WITH mysql_native_password BY ‘’; AND
    ALTER USER ‘root’@‘localhost’ IDENTIFIED WITH mysql_native_password BY ‘’;

    It’s okay if one of them fails. This is going to fix Most people’s issues.

    I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.

    To prevent this problem from happening in the future you could run:

    apt-get -y remove unattended-upgrades (AS Root again).

  • Updated To FOG 1.4.0 - Getting Blank White Page

    12
    0 Votes
    12 Posts
    4k Views
    W

    @noelpd Thanks!!!

  • FogReplicator and Storage Nodes.

    Solved
    64
    0 Votes
    64 Posts
    37k Views
    Wayne WorkmanW

    @george1421 I didn’t know this was a multi-master setup, if that’s what you meant. I was referring to a video on just configuring a second node into an existing fog setup. With the new access control plugin and site plugin, multi-master setups are just that less a good idea.

    As it stands now with the access control plugin, location plugin, and site plugin - the only benifit one stands to gain in a multi-master setup is some level of fault tolerance against the upstream box failing - and fault tolerance against the link failing - and for those two things you loose a comprehensive database/control center in a central location - a major drawback.

  • PXE boot under Fortigate 40C

    Solved
    10
    0 Votes
    10 Posts
    6k Views
    K

    @george1421

    Hey george1421 some update: 🙂
    all PC getting IP and seeing the Fog menu for deployment and registration much appreciated again, for direction.

    might be its for new post but wondering I notice one thing that after Deploy image when PC rebooting he is looking for pxe instead load OS, so I need change the BIOS manually to UEFI enabled.
    before the change it was done automatically enable/disable UEFI on BIOS

    thanks ,
    Kpax

161

Online

12.4k

Users

17.4k

Topics

155.9k

Posts