@Sebastian-Roth

Interesting, and good questions. I definitely didn’t install anything, but curl, and openssh.

The Ubuntu install was a stock “Quick Create” on Hyper-V; the first thing I did with all 5 VM’s was to download and install Fog.

My exact steps were this:

sudo apt-get install net-tools sudo apt-get install openssh-server sudo apt-get update sudo apt-get install curl curl https://codeload.github.com/FOGProject/fogproject/tar.gz/1.5.6 --output 1.5.6.fog.tar.gz tar -xzvf 1.5.6.fog.tar.gz cd fogproject-1.5.6/bin sudo ./installfog.sh

This was based on this page: https://fogproject.org/download

Side note: Ah ha! sudo -i works on a Raspberry Pi. Su does not; root is disabled, so I got in the habit of doing “sudo” for everything. So it never occured to me the sudo ./installfog.sh was a problem. I get you on the path issues; I ran into this with Debian, so much so I just ran “su” there and did everything as root 🙂

The root user is disabled on Raspbian (I do a lot of work on embedded systems), so I got out of the habbit of su.

I had hoped to run Fog on a PineH64, but couldn’t get it to boot with Armbian, and the supporters of Armbian said “I was wasting their time” trying to debug why it wouldn’t boot without a $20K payment to them. I won’t be doing Fog with Armbian! I may try it on the Pi 4, it’s got a Gigabit network, and USB3, so might get some OK speeds. If I get it in time, I’ll let everyone know.

For now, I’ll use the Debian VM, but for completeness will check the above commands.

The proposed fix here again more or less hung stuff up.

sig@sig-fog-3:~$ sudo fuser -vki /var/lib/dpkg/lock [sudo] password for sig: sig@sig-fog-3:~$ sudo apt purge snapd E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. sig@sig-fog-3:~$ sudo dpkg --configure -a Setting up libgstreamer-plugins-base1.0-0:amd64 (1.14.4-1ubuntu1.1~ubuntu18.04.1) ... Setting up libpython3.6-stdlib:amd64 (3.6.8-1~18.04.1) ... Setting up gstreamer1.0-plugins-base:amd64 (1.14.4-1ubuntu1.1~ubuntu18.04.1) ... Setting up gir1.2-gtk-3.0:amd64 (3.22.30-1ubuntu3) ... Setting up libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1) ... Setting up libedataserver-1.2-23:amd64 (3.28.5-0ubuntu0.18.04.2) ... Setting up cups-browsed (1.20.2-0ubuntu3.1) ... Setting up plymouth-label (0.9.3-1ubuntu7.18.04.2) ... Setting up usb-creator-gtk (0.3.5ubuntu18.04.1) ... Setting up gstreamer1.0-pulseaudio:amd64 (1.14.4-1ubuntu1~ubuntu18.04.1) ... Setting up plymouth-theme-ubuntu-text (0.9.3-1ubuntu7.18.04.2) ... update-initramfs: deferring update (trigger activated) Setting up gvfs-fuse (1.36.1-0ubuntu1.3.3) ... Setting up libgnome-bluetooth13:amd64 (3.28.0-2ubuntu0.2) ... Setting up libgbm1:amd64 (19.0.2-1ubuntu1.1~18.04.1) ... Setting up libevdocument3-4:amd64 (3.28.4-0ubuntu1.2) ... Setting up python3.6-minimal (3.6.8-1~18.04.1) ... Setting up cups-ppdc (2.2.7-1ubuntu2.6) ... Setting up libebackend-1.2-10:amd64 (3.28.5-0ubuntu0.18.04.2) ... Processing triggers for initramfs-tools (0.130ubuntu3.8) ... update-initramfs: Generating /boot/initrd.img-4.15.0-47-generic Setting up libqmi-glib5:amd64 (1.22.0-1.2~ubuntu18.04.1) ... Setting up libqmi-proxy (1.22.0-1.2~ubuntu18.04.1) ... Setting up libebook-contacts-1.2-2:amd64 (3.28.5-0ubuntu0.18.04.2) ... Setting up snapd (2.39.2+18.04) ... md5sum: /etc/apparmor.d/usr.lib.snapd.snap-confine: No such file or directory snapd.failure.service is a disabled or a static unit, not starting it. snapd.snap-repair.service is a disabled or a static unit, not starting it.

Just in case I messed something up … I’ll create a sixth Ubuntu “quick start” 18.0.4 LTS image for Hyper-V and immediately check the snapd stuff.

== John ==

Yes I’m aware of this behavior, I’m working on that from my side…

@u1401149 See George’s answer.

I created a new disk.

I have to change the repertory of the picture.

It is on wich file ?

Only /opt/fog/.fogsettings ?

I create a new topic : https://forums.fogproject.org/topic/13366/tftp-error-on-server/2

@Sebastian-Roth I did it and it’s work ! thanks a lot for your reply ans the time you spent for me 🙂

OK I have a working solution at least for centos uefi. I don’t know if it will break others… YMMV

scanfor internal,external,optical,manual dont_scan_files shim.efi,MokManager.efi,shimx64-centos.efi,shimx64.efi,mmx64.efi

I didn’t need to change anything else from default. I didn’t see any other settings I fiddled with over time either.

@montesd What target OS are you capturing?

What mode are you using to capture the image (single disk resizable, single disk non-resiziable)?
In the partclone screen, is it capturing the image as raw (as if you have bitlocker enabled)?

I’m initially suspecting something wrong with the source disk itself. The error reporting out of partclone is not very good, so FOG makes the assumption that the server is out of disk space.

One way to debug this is to start another capture, but before you hit the submit button tick the debug check box, then submit the capture task.

PXE boot the target computer and then after a few screens of text (where you must press enter to pass) you will be dropped to a FOS Linux command prompt. At the FOS command prompt key in fog and press enter. This mode will allow you to single step through the image capture hopefully you will be able to capture the exact error message displayed in partclone. Also if you reach the error but partclone hasn’t told us what we need, we can look at the partclone error log. But lets start with the single stepping through the capture to see what the true error is.

Ok, solved that. Seemed like another one of those spanning tree issues… 🙂

@Junkhacker and @Sebastian-Roth

Junk was right. Fresh install taking almost all defaults fixed it for me.

Thanks!

@Sebastian-Roth Well it looks like I need to pay better attention to the wiki articles. I reinstalled mono, complete this time, and I was able to push a task to the host. The Host still doesn’t show up as online within the host list on fog, but I can live with that.

Thanks again! Now I can replace a fleet of windows signage machines!

@docorange6 Sorry for the late answer.

Looking at the information you posted we see that it handles sda2 (SWAP as we see from type=82) as fixed partition. And because of that I am fairly sure it will resize the boot partition (sda1) back to it’s original size as well.

I can understand that you would prefer it to not touch sda1 at all and I think we have fixed this in the latest scripts already. Please download the latest init files (32 bit and 64 bit) and put those into /var/www/html/fog/service/ipxe/ (best to rename the original ones instead of directly overwriting those.

@daguilar if you no longer have the option of exporting from the old server, you’re probably best off just creating each one manually though the interface. just make sure the “Image Path” field and format info matches the info that goes to the files.

@Sebastian-Roth Yes of course. The networking team will let me know.

@airsine Thanks for posting the issue. We don’t seem to have many Mint users and didn’t notice that obviously they have moved to default to PHP 7.2 being pre installed. At least that is my interpretation of the error without actually having looked into it.

If you are not bound to use Mint then see George’s and Wayne’s answers.

If you want to stick to it, try running the installer as php_ver=7.2 ./installfog.sh (note this is just from the top of my head, no promise this is working)

It started working after i disabled selinux…

Wait… Maybe I’ve been going at this wrong.

Am I supposed to manually register each computer I image? I assumed the client would register the computer in the FOG server. My bad if so, I’ve looked at the quick register settings, enabled it but that isnt bringing new clients on to the server

@fhrivers That did it. I assumed that since I could browse this site, I didn’t need to add it to the web filter. I’m up and running! Thanks!

@Sebastian-Roth that fixed it. I just tested it by booting a laptop off PXE and it works great. I am now capturing an image. I really appreciate you taking the time to help me out.

@mig39 I am wondering which version of FOG are you trying to install? I remember we had this issue long time ago and the current installer should install those packages for you - see here!

The line numbers we see in the error messages above don’t match those in the current scripts. So I am fairly sure you are not using the latest FOG version 1.5.5!?