The files of /var/www/fog/service/ipxe are in your /var/lib/tftpboot folder and the the /tftpboot folder does not exist.

Try running the FOG installer again and hope it can fix this mess.

@Dave-Wolf If I’m not mistaken, you’re using ubuntu?

If i had to guess, mysql started before networking was ready, so you’re kind of in a “stale” state for the mysql process.

Try simply running:

sudo service mysql stop

It will most likely come back with failure to find running process…

Then run:
sudo service mysql start and all should start working from the MySQL standpoint.

RC11 solve the problem, thank you
You can close this topic

Thx Wayne, your method worked I’m now in RC11

You can close this topic

@Wayne-Workman Indeed - many thanks for your help 🙂

@mrayzies I would suggest becoming standard. You can completely separate out all of fogs pieces as you wish, but storage nodes are best as a full Linux vm and setup with the fog installer.

@Don-Winters Great you have it worked out.

Happy cloning.

@Tom-Elliott said in UEFI won boot tools via fog menu.:

hink

I see!! that’s great to know!!!

@Wayne-Workman Hell, whenever I try to upgrade Ubuntu even Ubuntu gets messed up and I need to spend time to fix it.

Already known about and fixed for RC 12.

@Tom-Elliott All nodes at RC-11, It back to assigning recently used snapin associations from recent image deployments

0_1475507131758_upload-32d5e685-9979-44a5-844e-e07b3c6cd59b

Nothing has changed here. Just going about day-to-day operation. Tried with same host name, and never before used host name, same result.

I update and it worked
0_1475505744994_fog.jpg

@Polii123 That’s what I would suspect, yes.

@Wayne-Workman said in Error 500 while trying to display Imaging Log:

@Dave-Wolf said in Error 500 while trying to display Imaging Log:

but if I try to use this name and password to access the mySQL database, it fails to login.

How are you trying to use it? Give us the command, replace the password with something else but ensure the structure of the command is the same.

@Dave-Wolf said in Error 500 while trying to display Imaging Log:

What should the FOG_STORAGE_MYSQLUSER actually be in the web config page?

It should be fogstorage

I initially thought that my report display problem was an issue with the SQL database, so I was following the “Testing MySQL” section of the “Troubleshooting MySQL” section of the wiki. I was using the following command:

mysql -u fogstorage -p****** -D fog

and I was getting an “access denied” message, though I just checked that again now and it is working fine. So I’m not sure what was wrong, maybe it was just Friday after a long week…

In any case, thank you so much again for your responses to help me resolve the imaging report issue.

Cheers,
Dave.

@george1421 said in everything installed. But management page not displaying correctly.:

the installer now uses the right php install sequences and the command line variables are not needed when the installer is called?

Correct. It just works now without anything special.

@czajne what is the exact switch you’re using? What happens when you multicast to just 2 computers ?

@george1421 The disk defrag was not fully proper. It couldn’t move portions to the proper areas. Once done a few times (just guessing) I think it started to work for him because the bits of “freespace” were then “properly cleared”

Try a different network drop and different patch cable, too.

I’d also recommend not upgrading your OS to 14 or 16, it will not go well with fog. Sit aside the old server (or swap out HDDs or something) and build a new one from scratch, if you are going to build a new server, I’d recommend going with Ubuntu 16 only because it’s the latest and will be supported the longest.

@zingaro That’s not NFS, in the command it says cifs. without heavy init modification, fog will not work with cifs. Also, you shouldn’t setup an NFS share this way, either. The share does not get mounted to the server at all, because if it were, imaging would not work. The Linux kernel will not allow you to re-export an already exported directory. You don’t even need to touch the CLI of the main server to do this. Just the NAS and the web interface of FOG.

On the NAS, create an NFS share with full read/write permissions for everyone. Create an FTP user called fog and grant it full rights to the share. In the share, make a file called .mntcheck and a folder called dev and inside of dev make another file called .mntcheck Then plug in the IP address and share name and the fog user along with it’s password, and ftp path into FOG’s web interface.