Posts made by Wayne Workman

@Sebastian-Roth said in Adding needed repository... Failed!:

@Wayne-Workman The installer test seems absolutely fine but possibly that’s because you have the package software-properties-common pre-installed? Can you check on that? I have had a look at the logs from your installer tests but the package is not mentioned and that’s why I guess you have it pre-installed…

Yes, it’s pre-installed. This is on Ubuntu 18.04 server, minimal installation.

root@ip-10-0-0-165:~# dpkg -l | grep software-properties-common
ii  software-properties-common     0.96.24.32.7                      all          manage the repositories that you install software from (common)

@jcabuco No, not realistically. Blame Microsoft for that. They charge money to sign iPXE binaries. With FOG being an incredibly low budget open source project supported by volunteers, Microsoft has pretty much all but barred FOG from playing the SecureBoot game (eyes on you, Microsoft).

You should consider more than just a remote database, you need to scale. You should probably put a few FOG servers behind HAProxy as a load balancer (And have HAProxy do SSL offloading if you use https), and turn sticky on for HAProxy. Then, each of those FOG Servers should point to another HAProxy load balancer that distributes database queries across a Galara MariaDB cluster.

^ I know how to do all that, and can guide you.

A quick google search gives some tutorials:

HAProxy http load balancing:
https://thegeeksalive.com/how-to-setup-haproxy-http-load-balancer-on-centos/
https://www.digitalocean.com/community/tutorials/how-to-use-haproxy-to-set-up-http-load-balancing-on-an-ubuntu-vps

HAProxy Galara load balancing:
http://galeracluster.com/documentation-webpages/haproxy.html#using-haproxy
https://www.cloudandheat.com/blog/tutorial-simple-mariadb-galera-cluster-with-haproxy-load-balancing/

I don’t know if the access control plugin applies to the boot menu… @Fernando-Gietz ?

@dooleyrd We need the FOG log from one of the host’s failed attempts before we can tell you anything. It’s normally at C:\fog.log Please don’t snip a tiny piece from this file, but give us a whole client iteration - or the whole file.

@fenix_team Check for Apache errors that are written during an attempt to see logs via the UI. Also check free space on your fog server.
Also, just as a general rule you can re-run the fog installer when you have issues, it’s pretty good at fixing them. As always, I recommend a snapshot/backup before making changes.

@Sebastian-Roth I don’t have access to their articles anymore - but when I did have access back at a previous job, I found if I google’d enough I could find the same stuff elsewhere.

Has a duplicate IP been looked for yet, for the fog server and for the VMs?

@lambdacalculus Typically, this error is not caused by accessing certain pages… Generally speaking, your database connection is totally busted, or is intermittently working. And when it’s intermittently working, it’s usually load related problems. I have some questions for you:

• How many hosts do you have running the fog client?
• How much ram/cpu do you have allocated to your fog server?
• What OS & version is your fog server running?
• What version of FOG are you running?
• Give us a screenshot of the output produced by the linux top command on your FOG server while the problem is occurring.
• Check for a duplicate IP address concerning your FOG server’s IP address using these instructions.

@george1421 said in Presenting On FOG at conference?:

I happen to have Raspbian installed without the gui.

We all know that’s the only way. :-)

@Almeida I thought the upload limits for 1.5.4 were 100MB. What OS & version is your fog server running? Also make sure you have the space in /opt/fog/snapins

Related article for future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

I made the changes and did a test run, dev-branch completely passed.

@MoonDancer We still don’t know your fog version.

@Reagan delete everything in /var/www except for html, and delete everything in /var/www/html and then re-run the installer.

@salted_cashews Correction. This is what I use for updating Debian based systems: apt-get update;apt-get -y dist-upgrade;apt-get -y autoclean;apt-get -y autoremove

@mstrolo Good thing we have a wiki article addressing this exact issue: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Repair_broken_database

@Sebastian-Roth I’ll add the command pacman -Sy archlinux-keyring && pacman -Syyu into the mix soon, I’m sure it’ll resolve the issue.

@Rhywden What OS and version are you running?

This is just me, but if my FOG server was in a VM (it is), I’d snapshot it, and then delete everything in /var/www/html and re-run the fog installer.