@george1421
It seems yes

I just upgraded debian an it’s now php 7.3 but the installer of fog 1.5.7 is looking for php 7.0.
Do i have to install the dev-branch ?
Actually nothing works anymore

@ckasdf said in Errors in Apache log and www-error.log:

Perhaps those are less errors, and more just warnings?

Abdolutely but it’s still imporant to get rid of those to not cause any confusion when we tell people to consult the logs when looking for an error.

Is LDAP login possible with the current build?

While I have not tested it myself in our test environment lately I am fairly sure it does work. I remember others posting questions on this in the forums and did succeed.

If so, I’ll open a new post requesting help with that.

Probably not too bad of an idea. Doesn’t cost much extra and it’s good to keep things sorted a bit so people find answers more easily themselves.

Just a quick hint: Are you able to connect to your LDAP using the same credentials in a tool like ldapbrowser?

@weidongyan CentOS installs on LVM by default. Unfortunately FOG does not support cloning LVM as of now.

Probably something we can add if you are very keen and help us working on this.

The easier way is to re-install your master without LVM…

@chunter2 You are free to ask pretty much anything here but don’t expect a full answer. 😉

Though you are using FOG this has not much to do with it and I won’t find the time to step you through this. Maybe other user will.

What I was actually trying to say is that there are forums with users way more experienced on this particular topic than we are. So even if people wanna help I am sure there are other places you get more experienced eyes on your question to help you.

To say it in a MS Windows terms (which also doesn’t support this). Lets say you have server A and you share a directory. On server B you connect Server A’s share to the W: drive. On server B you are try to share the W: drive. The share fails because you are trying to reshare a mounted share. Again this is a file level share. You may be able to do this with a block level share (as an iSCSI volume), but I haven’t tried.

@bogle

Solved it…

yum reinstall ca-certificates curl -sS https://downloads.mariadb.com/MariaDB/mariadb_repo_setup | bash

@quinniedid Sad to hear that you had a lot of work and trouble with this but sometimes it’s just good to redo the whole lot to get rid of old issues. Hope you have moved forward from Ubuntu 16.04 as well! 🙂

@george1421 thank you for the help.

@Sebastian-Roth It works!!! Thank you.

@Sebastian-Roth Hi Sebastian, I reboot the system and now when I enter the command, it prompted ‘Enter password’, I just click enter and now the error came
'ERRO 1045 (28000): Access denied for user ‘root’@‘localhost’ (using password: NO). Because last time I entered some command I found in the internet, I did not want that to influence our process so I reboot. Last time, I restarted MySQL and entered ’ sudo mysqld_safe -skip-grant-tables’

@mitnotromney said in PXE Boot "Initial menu has no LABEL entries!":

I set it up to have Fog handle DHCP.

In that case it should not habd hand out pxelinux.0 - possibly you have another device handing out IPs and PXE infos to the VM.?! The IP address we see in the picture, is this the FOG server address or a different one?!

@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.