• could not install PciConfig hanler

    8
    0 Votes
    8 Posts
    1k Views
    george1421G

    @cicero ok two things.

    The PciConfig handlers is just a spurious warning message. You can safely ignore this warning. If FOS Linux hits a critical warning it will stop booting.

    What is more interesting is what I can’t read in the picture. It looks like /images are being redirected somewhere. What is going on with that link? I think I can make out you have the virtual raid adapter md127 is mounted on /raid/fog/images and then you have a symlink mapping /images to that sub directory. NFS doesn’t follow symlinks.

    There is a few ways to fix this, but I would have to ask why the logic of /raid/fog/images? A quick way to fix is to mount /dev/md127 over /images (directly) and then rerun the fog installer to fix the reset of the bits.

  • Visual Studio activation snapin

    Solved
    4
    0 Votes
    4 Posts
    732 Views
    EruthonE

    Great, it works 🙂 sorry for the bother

  • Getting stuck at /ipxe/boot.php

    9
    0 Votes
    9 Posts
    1k Views
    V

    @Sebastian-Roth It’s works thanks you ! 🙂

    Try with ipxe.kpxe !

    With “kk” SAN boot image don’t work.

  • How to PXE boot from master node in location/storage group

    10
    0 Votes
    10 Posts
    904 Views
    S

    @dopyrory3 said in How to PXE boot from master node in location/storage group:

    so the imaging actions of other admins in other countries can be monitored for usage, issues, and consistency.

    You can do this by logging into the web UIs of the FOG master nodes at each location or even easier write a little “tool” to or manually pull that information from the location (master) nodes. From my point of view there is no point in making the overall FOG setup decision depend on the reporting you want to get from the system. This should have way less priority than actual imaging and transfer of stuff over the VPN as this will cause you and your team way more issues and headaches when the initial setup decision is not ideal.

    I’m intending to disable the storage node features of the Central Master server so it’s not assigned to any Storage group, and let storage nodes take up the responsibility of deploy/capture for their respective countries.

    As mentioned before, capture can only be done to a master node. There is no way (other than really hacking a fair bit of the code) to get a machine to capture an image to a storage node.

    using the AccessControl plugin to restrict them somewhat

    Another plugin that does not belong to the core code (as all plugins do). While they are part of the official code they don’t get as much attention as the core code does. Not because we don’t like those but because we hardly have enough people to work on the core and can’t afford to put in as much energy into the plugins as we do in the core. What that means is that most plugins have been added by vigorous FOG users and we don’t have anyone to improve those as much as we work on the FOG core. When people report a bug we try to fix though. I think you get what I mean. The access control plugin is one of the most overrated in the FOG world I reckon. People hope to get a full blown access control to restrict people from anything they want them from doing but in reality FOG was not build with layers of access in mind and this plugin won’t solve it properly.

    I want to have nodes for countries, but centralise the management aspect.

    I think it’s really good you start looking into FOG and asking in the forums because we are keen to set you on the “right way” to enjoy using FOG a way it can really make your life a lot easier. But there are tripping hazards that we can try to rule out beforehand. So again, centralizing the management in a single Central-Master will leave you with some big hurdles to cope with. Let’s re-think that design I’d offer.

  • DHCP-Server is not fog, so how..

    10
    0 Votes
    10 Posts
    1k Views
    S

    Hi, sorry for the long time without response.
    I checked a WDS and this server couldn’t serve too,
    Than I put one client in my other dhcp config and tada, it works.
    So it’s with the shared-network settings, that at least pxe won’t work. I have this config for now 2 Years an most of the time myself is in “the other net” so i don’t have seen this behavior.

    My work around is to put my cloning Pc in the “working” net, image them and than change it to the other net.

  • Kernel update to 18.04 -- image deployment now taking 4x the time

    Solved
    3
    0 Votes
    3 Posts
    278 Views
    Z

    This can be disregarded – and marked as solved - the underlying VM infrastrcture was having an issue - we didn’t catch it as we of course thought it was due to the upgrade.

  • Strange logs

    3
    0 Votes
    3 Posts
    482 Views
    S

    @plegrand Yes correct, this has been fixed already. This has nothing to do with the fog-client issues you see.

  • Stuck on pinning server

    10
    0 Votes
    10 Posts
    1k Views
    S

    @plegrand Do other clients work properly or do they all show those messages in the client logs?

  • Unable to update Kernel and Captures not going to /images

    14
    0 Votes
    14 Posts
    995 Views
    S

    @doogxela Good to hear this solved all the issues. Please keep in mind that when you re-run the installer to upgrade to the next version this might happen again. Though I am not sure. I don’t have Lubuntu to test here.

  • Compiling custom kernel / network driver missing issue

    8
    0 Votes
    8 Posts
    1k Views
    D

    Thank you, your instructions worked great. I needed to install flex and workaround a kernel specific issue (http://rglinuxtech.com/?p=2834) but otherwise things went very smoothly.

  • Total wipe and re install

    6
    0 Votes
    6 Posts
    2k Views
    S

    @Julianh Please read through the whole wiki page and you’ll find the section on exporting the DB.

  • API gives 500 error but only for a specific call

    10
    0 Votes
    10 Posts
    1k Views
    S

    @robincm Sure you can do a full database maintenance/cleanup manually: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

    Not sure if it’s wise to do this an a regular basis because others might want to keep that history for a long time. You can access all of that in the hosts (edit) view -> Image History tab.

  • Multicast - unable to find image path

    16
    0 Votes
    16 Posts
    2k Views
    S

    @Eruthon Great to hear you got multicast working. It’s way more convenient to deploy this way! Well done.

  • Can't deploy on Dell Latitude 5410

    20
    0 Votes
    20 Posts
    3k Views
    A

    @george1421 thanks dude !
    It’s works !!!

    Thanks for your help

  • Capturing image update database failed

    22
    0 Votes
    22 Posts
    7k Views
    B

    Works fine now. Thanks @Sebastian-Roth !

  • FOG Kernel update: "Preparing to move to tftp server"

    7
    0 Votes
    7 Posts
    2k Views
    george1421G

    @Pyrol said in FOG Kernel update: "Preparing to move to tftp server":

    and the final step was to go into WebGui>fog settings>tftp server
    and here changed bzImage to bzImage.64 the same with bzImage32

    I would back up to this step. Replace the existing bzImage with the .64 bit one keeping it bzImage and the 32 bit image should be named bzImage32 (watch your case because it is important). Leave everything else FOG defaults. It will save you headaches in the future. Then pxe boot the client once you are on 5.6.18 it will see the network adapter.

    Then we can look back to why the update process is not working as it should. What version of FOG are you running?

  • 0.00 iB of all images on server (not standard setup)

    3
    0 Votes
    3 Posts
    552 Views
    EruthonE

    Ok, so I found the solution: after I copied all the images on the main fog server with its new 2TB disk and making the main fog server as the master node and restarting the FOGImageSize service on the main server, the info about the images’ sizes on the server appeared in the webpage.

  • Active Tasks in Storage Group Activity shows active task

    3
    0 Votes
    3 Posts
    809 Views
    R

    Perfect all looking normal now 🙂
    One place I didn’t think to look was on the Wiki 😕

    Thanks!
    Cheers,

  • Fog will not register hosts. At all...

    12
  • Hosts reboot after any selection at FOG menu

    3
    0 Votes
    3 Posts
    526 Views
    S

    @doogxela Thanks for using the latest release and letting us know about issues.

    The initial topic on kernel problem seems weird to me because the installer script uses checksums and would re-download the kernel/init files 10 times in a row if the checksum doesn’t match and error out in the end. So I can’t really see why there could be anything wrong.

    On the other hand I see from your post that you are using a custom kernel image (bzImage_5.6.18) and I am wondering if that customization had anything to do with the boot issue??

    About the slowness you want to check out this topic: https://forums.fogproject.org/topic/14267/upgrade-from-1-5-7-to-1-5-8-issues

    Unfortunately we didn’t get enough response and didn’t have enough time to keep up this topic and figure out which part is causing the slowness.

171

Online

12.3k

Users

17.4k

Topics

155.6k

Posts