Categories

  • 13k Topics
    115k Posts
    Tom ElliottT

    @kratkale What you see in the text field are place holders, just example views, if you were to hit update/save, those things aren’t what will be set.

    THe reason you see “(varies)” is because the hosts in the group have some things where their host Primary Disk is set, but not all hosts have the same values.

    As for your odd snapin issues please try these commands on the Database:

    delete from snapinAssoc where saSnapinID <= 0; delete from snapinTasks where stSnapinID <= 0;

    As for the domain join issue:

    The “captured” host should not be joined to the domain until after the image has been captured.

    The error you were seeing was joining domain “Code = 87”

    That is not FOG writing an erroneous error, but rather the error from the Domain controller directly.

    This may mean your environment is expecting to be set to a specific OU within the domain?

    https://forums.fogproject.org/topic/11971/unable-to-join-domain-error-87

    This is an old (albeit similar) topic with the same type of error you had seen so maybe it’s fix may help your fog client as well?

    This, of course, isn’t strictly necessary, since your snapin method appears to be working anyway.

    As always, please update to the latest and greatest as it should help with the prevention of odd jobs just getting created as well. After you clean up things of course.

    Thank you!

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    V

    Hello everyone,

    I am facing an issue with image capturing after performing an upgrade on my FOG server from 1.5.10 to 1.5.10.1886. Before the update, everything worked fine for me. The images were stored directly on the Synology NAS.

    My Setup:

    FOG Server: IP 192.168.10.220 (Debian 13) Storage: External Synology NAS with multiple virtual IPs (192.168.109.220 and 192.168.110.220). Storage Configuration: The Synology NAS is configured in FOG web UI as the Master Node for its storage group. The local Default storage node is NOT the master. Clients: Multiple clients on different subnets (e.g., 192.168.109.23 and 192.168.110.23).

    The Problem:
    The Partclone phase finishes successfully on the client machine. The image files are correctly uploaded via NFS directly to the Synology NAS into the /images/dev/[MAC_ADDRESS] folder.

    However, right after Partclone reaches 100%, the task gets stuck in the FOG Web UI (at around 70%), and the client screen shows the following PHP FTP error:

    Error returned: Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 709, Message: ftp_put(/images/dev/[MAC]): Failed to open stream: No such file or directory, Host: 192.168.110.220, Username: foguser

    What I have verified:

    I tested the FTP connection manually via CMD/PowerShell from a PC using the same foguser credentials. I am able to log in, mkdir, rename, and rmdir inside the /images and /images/dev directories on the NAS without any permission errors. If I move and rename the MAC folder manually inside Synology File Station from /images/dev/[MAC] to /images/[Image_Name], the image works fine. This setup worked flawlessly before the FOG server upgrade. The /images directory is NOT mounted locally on the FOG server itself (and never had to be). Verified FTP username and password on NAS and FOG. It's same.

    It seems that fogftp.class.php is incorrectly triggering ftp_put (trying to read a local file from the FOG server) instead of doing a remote ftp_rename directly on the NAS storage node.

    Has anyone encountered this bug after a recent upgrade, or is there a specific setting in the new version that I missed?

    Thank you for any help.

    Storage Node for NAS
    Storage Node for NAS.png

    Error on PC
    U10-PC13.jpg

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    K

    @Valer Hi Valer,

    You can see my tutorial on using Secure boot with Shim, and my thoughts on what 2.0 means for Secure Boot with FOG here: http://forums.fogproject.org/post/158170

90

Online

12.7k

Users

17.6k

Topics

156.7k

Posts