Posts made by Huecuva

@Sebastian-Roth I have changed nothing on the FOG server. It’s a pretty fresh install. In fact, I installed it fresh about 4 times yesterday trying to get things to work. The only things I have changed, before even installing FOG, was to edit the fstab file to mount the 1TB drive at /images and to edit the yaml file at /etc/netplan/ so that the machine could even resolve DNS, otherwise I couldn’t even download FOG. The mining rigs still don’t have DNS, but I’m pretty sure that is not a FOG related issue.

As for what version of FOG I am using, I am using 1.5.7 because the OS I am using is Ubuntu 18.04. I had tried using 1.5.9 but it was causing all sorts of failures during boot. I can’t recall exactly what was failing, but I believe it was DHCP related and the OS would only boot into emergency mode. I guess I could try installing Ubuntu 20.04 instead.

Hey guys. I finally got a confirmation email after waiting days for it. I’m having a strange issue on a FOG server.

After fiddle-farting around and finally getting my crypto-mining rigs to boot from PXE and register in FOG, I am having issues capturing an image. Upon finishing the capture, FOG attempts to update the database but fails because the credentials are wrong. During installation, I used the default (ie: blank) MySQL password. When it fails to update the database it cites some user account called “fogproject” and I’m not sure where that came from, as the linux account generated by the FOG installer is just called fog, as far as I’m aware. I have a separate 1TB HDD mounted to /images where I intend for FOG to store the images it captures. It is able to inventory and register hosts just fine, but it cannot update the database when it finishes capturing and ends up rebooting the machine and running the capture all over again until it’s canceled.

Now, it just occurred to me that the issue could involve user ownership of the 1TB drive mounted at /images but if that were the case, would it not also have problems inventorying and registering hosts?

I have not had this problem running FOG on my home network on a VM but I have not tried using a separately mounted drive for /images as that particular setup would be difficult for me to test on my own network. Could the ownership of /images actually be the problem or is there something else going on here?

Thanks in advance.