Posts made by Sebastian Roth

@mardonis200 Where exactly do you see this error? Which Linux OS and version do you use? Also post the full content of the configuration file used.

@jfenner Obviously something went wrong when installing. What output did you get from the installer? I doubt it finished fine.

Please post the full content of the installer error log - found in the sub directory named error_log of where you initially ran the installer script from.

@danboid You can set a specific disk for each host individually in its host settings. Have you tried that yet? This way you can make FOG capture and deploy only from/to a certain disk. Depending on the FOG version used you can select a disk via Linux device file name (e.g. /dev/sda) which works ever since I know FOG or in the latest version you can also use disk size or disk serial number…

@Kureebow Which kernel version and FOG version do you use? Does the same happen on different computer models?

@chambie said in Fog Configuration Kernel Update not working:

I have this file in two directories, one that is updated and one that is not.

You seem to have a duplicated FOG docroot, one in /var/www/html/fog/ and another one in /var/www/fog/. In certain cases this happens - I think I have only seen this when the FOG installer runs for the first time but does not finish properly. Though I never had the time to look into this properly.

Now that you know the correct docroot path on your system I suggest you rename or move the wrong one. But instead create a symbolic link pointing to the correct one named just like the old wrong docroot directory.

@lostitguy Do you have any USB devices connected. If yes, then I suggest you disconnect all if possible or use different USB ports and try again.

@kapelar-pablo said in image problem not seen by FOG:

to add them manually how should I proceed?

Well, just create the image defintions in the web UI and make sure the settings are the same as they were on the old server.

@Ax_Hades Please open a new topic in the forums and give us some more information on your own setup (FOG version, DHCP server, make and model of client machine, picture of errors on screen, …).

@kapelar-pablo said in image problem not seen by FOG:

knowing that the images that we see are the one that I tried to add manually.

FOG does not automatically add images it finds in the image store. You need to manually add those.

Before re-installation you could have used the “Exporter les images” link to get all the image definitions and be able to import those again on the new server.

@dyacishyn Looks like I was wrong. The partition on the new disk does not have a filesystem on it as we see by the output of the file command. Do you remember if you missed the mkfs.ext4 /dev/sdb1 command?? I suggest you issue that command (again).

I won’t be liable for any loss of data. Formating a disk with a new filesystem will overwite whatever is on there now.

mv /images/.mntcheck /root
mkfs.ext4 /dev/sdb1
mount /dev/sdb1 /images
mv /root/.mntcheck /images

If this is all fine (no errors) you might just do another server reboot to make sure it’s all fine.

@Fog_Newb Can we mark this solved then?

@youzersef Hello and welcome to the forums.

As far as I know the fog-client managing printers for you cannot enforce access rights on the printers. If you are keen you can work on implementing this feature yourself. FOG is open source and we can help you on the general aspects.

The other way would be to enforce access rights by using a printing server/spooler like Windows I suppose.

@dyacishyn Thanks for uploading the pictures elsewhere.

Looks like the new disk / partition is kind of prepared but we still don’t know if this is formated. Please run the following commands. Copy&paste the output here or take pictures again:

file -s /dev/sdb1
mount /dev/sdb1 /images
ls -al /images

PS: Uploading pictures is working again. The issue was client_max_body_size in nginx config was too small (default was 1 MB - made it 5 MB now). So you should be able to upload larger size pictures now. Anyhow it’s still wise to downsize pictures before uploading.

@hummela Sounds like a bug on first sight. Will need to investigate.

Though you might help us checking the apache error log (see my signature) if there is any hint on an error.

@WT_101 said in Kernel Argument host vs global:

Question: how can i only use host args if it is provided else will use the global setting arg

Probably by modifying FOG’s PHP code I think. As far as I know there is no other way as of now.

@buddyaderholt I don’t see how this is directly related. Please remove the link you posted or we will do so unless you can explain the context of how this fits into the picture.

@Fog_Newb said in What do I rename the T2 bzimage file to for reliable mac OS capture and restores?:

It worked great and could capture and deploy no problem but…

Are you sure this is because of the new 6.x FOS kernel???

@Baden-Skates said in Isolated Fog Server Removing M.2 From UEFI Bios:

Long story short I’m losing my onboard drive and can not boot the device without being connected to the fog server.

You don’t actually loose the drive as you would not be able to boot form it when it’s connected to the FOG server network… Makes sense?

What I am saying is that FOG does not create EFI boot entries for you and that some UEFI firmware is not behaving “favorable” when cloning systems (instead of doing a plain OS install).

While the topic posted is about dual booting it might still help in your situation because it explains how to let FOG create EFI boot entries for you: https://forums.fogproject.org/post/151757

@Martin-IT-Systems said in Where do I find the file undionly.kpxe and default.ipxe:

Now to my question: on Github FOG Project / Backet someone has set under tftp a lot of ipxe so also the undionly.kpxe file. Can I use this or where do I get this so I can copy this into /tftpboot?

Sure you can manually download the files. BUT the files not being in /tftpboot might be a hint that the FOG installer never finished all the way to the end. I suggest you re-run the installer, carefully read what you see on screen, follow it’s instructions and it should take care of everything for you.

And where do I get the default.ipxe file or should I do it myself according to the instructions in FOG Wiki?

Same answer. The installer will create it when it runs all the way to the end.

Would there also have to be a dnamasq integrated into the network?

You can manually setup dnsmasq in your network if you think you need a DHCP Proxy. The FOG installer does not so this for you.