Just in case anyone finds this later, ended up using dnsmasq to make my configuration work using @george1421 's tutorial here: https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

Mine was a bit more complicated because I’m running an older version on ubuntu, but @george1421 's tutorial is spot once I got all the other weird things I had to do done lol.

Hello

This is a problem of config switch.
It’s a swtich Level3.

On one AC port works and not on the other.

I send you the config of its ports for info

Thank you for your help

@EricZ said in "Database connection unavailable":

I navigated to /Home/fogproject and ran the “git checkout dev-branch” and got “not a git repository” error message.

Then you are not using git source code but downloaded tar.gz/ZIP I suppose. While this isn’t wrong it’s just that you cannot switch between development and master branch as mentioned.

As well I am wondering if you are using the fogproject user to login? Don’t do that! It’s intended to be a service account and should not be used!

@Tom-Elliott Please ignore my previous post about this. I gave up on my current installation and reinstalled CentOS 8 and then tried to reinstall FOG again. I found a very useful Wiki article for CentOS7 and followed that. I posted a new issue elsewere in the forum so this particular problem no longer exists after a system re-install. I would post a new thread but I don’t know how. I don’t use forms much so I don’t know enough about them. To be honest, I wasn’t expecting folks to be so responsive on here (based on my previous experience with message boards) and I thank you for taking the time to reply.

@Tom-Elliott Thank you! I can confirm this fixed the issue. Snap-ins are deploying successfully and the tasks are clearing.

@Tom-Elliott said in Failure in Capturing an image:

@ismith-hpu But the machine, indeed, does have an OS on the disk? I can only assume the -a0 is a part of the problem. I don’t know what the argument is doing for the 0.3.12 version of partclone.

It’s to ensure compatibility with 0.2.89 images, allowing them to be deployed with 0.3.12.

0.2.89 had a broken checksum system, so we force it disabled on 0.3.12 in order to allow those images a normal deployment. It’s also faster and slightly smaller images, certainly not complaining about that part.

It is curious that 0.3.12 doesn’t seem to work in this instance, though I wonder if a non-resizable (not raw) capture has been tried?

@Daniel-Miller Thanks Daniel. They use puppet. I’ll shoot them an email.

Thanks again everyone for all the help.

@Tom-Elliott said in Backing up database Failed on install:

git checkout dev-branch

@Rogsninja As Tom said, you need to use the latest dev-branch version as there were issues due to the CentOS 8 release that came out after we had published 1.5.7 (latest official FOG version).

About install errors in general: The installer creates logs. Please take a look at /root/fogproject/bin/error_logs/fog_error_1.5.7.log and post the full content or a least the last 10 lines of that file here in the forums.

@Foglalt Yes new thread please. We like to keep one issue per thread so not to confuse future readers.

@LittleTux

How i can pass this post on Solved ?

Done. Glad it worked

okay thanks for the reply

@Sebastian-Roth the boss wants it updated…

@Baessens We there is nothing wrong with what there. What I see is a different version of undionly.kpxe for FOG 1.5.5 and 1.5.7. So the recommendation as a test take undionly.kpxe from the working FOG server and copy it over (renaming the original first) to the not working fog server then pxe boot.

If the problem goes away on the not working fog server then the problem is with undionly.kpxe if the problem stays then its with the different version of hyper-v

@Tom-Elliott This did resolve the issue.

@Keating178 The Invalid Storage Group error you were seeing should be fixed if you can upgrade to the latest within the dev-branch from GIT.

Hopefully this will fix the issue you were seeing too.

@george1421 said in issue with netcard of dock gen2 of lenovo l390:

@JJ-Fullmer The r8152.c from the torvalds github site failed to compile on 4.19.65, I’m suspecting its for a later release of linux. The version from the torvalds site was 1.10.10. The version in 4.19.65 was 1.9.9 of the realtek driver.

I was able to compile the realtek driver from the wget github site. This version is 2.12. Here is a link to that kernel with the 2.12 driver built in. I also enabled the usb-c code in the kernel that appears to have not been set. I don’t know if its relevant, but it should be on for other applications. https://drive.google.com/open?id=1wZwwOwbEr0nR3mnPLKg7AsulwJaGhO0A

Download this as bzImageRT (watch your case) and copy it to the ipxe directory with the other kernel images. Manually register the host and then in the host definition add in bzImageRT as the kernel for that host. Then pxe boot into FOS Linux debug mode to see if the network adapter inits correctly with this updated driver.

@John-L-Clark I realize that this is a few months old, but this problem sounds similar. Give this solution a try, download the kernel @george1421 made and set it on that host. It worked for me with the lenovo usb-c ethernet adapter, I imagine you’re using that or a similar adapter, this kernel fixed the issues we were having with the L390 and X390

Thanks everyone for the support.

@Daniel-Miller and @Sebastian-Roth I opted for the approach you suggested of making TFTPD ‘correct’ the filenames. The affected PC now goes to the FOG menu. I missed Sebastian’s map file and ended up writing my own which is:

# Workaround for PXE clients that misinterpret the DHCP options # because they expect a null-terminated string # match the extensions followed by any characters and replace it with # just the extensions r \.pxe.* \.pxe r \.ipxe.* \.ipxe r \.kpxe.* \.kpxe r \.kkpxe.* \.kkpxe

@george1421 I wouldn’t even have guessed that proxy DHCP was a thing. I’ve decided not to go for it this time but I’ll keep it in mind for future.

@george1421 said in issue with netcard of dock gen2 of lenovo l390:

@JJ-Fullmer The r8152.c from the torvalds github site failed to compile on 4.19.65, I’m suspecting its for a later release of linux. The version from the torvalds site was 1.10.10. The version in 4.19.65 was 1.9.9 of the realtek driver.

I was able to compile the realtek driver from the wget github site. This version is 2.12. Here is a link to that kernel with the 2.12 driver built in. I also enabled the usb-c code in the kernel that appears to have not been set. I don’t know if its relevant, but it should be on for other applications. https://drive.google.com/open?id=1wZwwOwbEr0nR3mnPLKg7AsulwJaGhO0A

Download this as bzImageRT (watch your case) and copy it to the ipxe directory with the other kernel images. Manually register the host and then in the host definition add in bzImageRT as the kernel for that host. Then pxe boot into FOS Linux debug mode to see if the network adapter inits correctly with this updated driver.

@Interrupt Give this solution a try, download the kernel @george1421 made and set it on that host. It worked for me with the lenovo usb-c ethernet adapter, it stands to reason it will work for the dock too.

@rwilsonadvantage You are welcome! I just marked it as solved (Topic Tools -> Mark as solved, not sure if you have access to this).

@Baessens In this special case I’d suggest you use basic Linux commands to export/import image definitions and sync the image files to your other node.

Optional: Create a sync user account on your main master node - otherwise you’d use the root account to do that but don’t use the fogproject account! Setup SSH keys to be able to login using the sync (or root) account from node B to node A Setup a cron job on your node B to do the DB and file sync Make sure rsync is installed on both nodes.

Here is just a quick outline of how you might do this (untested!):

#!/bin/bash ssh syncuser@nodeA mysqldump -u root -pPassw0rd fog images >/tmp/images.sql mysql -u root -pPassw0rd </tmp/images.sql rsync -ave ssh syncuser@nodeA:/images /images >>/var/log/fog/myimagesync.log 2>&1

This will wipe the images table on your node B and import all the definitions you have on node A.