Topics created by Dave Wolf

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

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

@Dave-Wolf The article says minutes for a 100GB+ image - this isn’t a stone-cold figure. If your system is older, running on older hardware, is under higher load, has slower RAM/Processor/Bus speed - this figure will vary quite a bit I imagine. Even more if it’s using a SAN that is less than amazing.

And, what you’ve described is exactly what’s described by Sebastian. Credentials check out, seems like a timeout, using Ext3… I am not sure you’re not affected - I’m almost positive you are. Ext3 is the issue, it’s how it operates, there’s no configuration you can do to fix it besides moving to Ext4 or better.

And - several people here have used FreeNAS with Fog, there’s a wiki writeup about it in two different spots I think, I’ll see if I can find them.

Newer note and features on the subject:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#FTP_Path

Older stuff:
https://wiki.fogproject.org/wiki/index.php?title=Use_FOG_with_FreeNAS

That’s part of why I’ve included fixparts in the init.xz/init_32.xz files. If something doesn’t seem to work properly, boot into a debug task, preferably upload, and run fixparts. It should find and fix any partition data that is supposed to be mbr but still has residue of GPT within it. This has been a common issue and I just don’t have a better means to fix this. I don’t know if you’re intending to maintain GPT or go pure MBR and if I start trying to make guesses as to what you’re attempting to do, it may cause more problems down the road.

No problem. I’ve seen this errors many times before, it’s the only reason I give the suggestions I do.

Thanks for reporting back.

That’s ok, I was just wondering if the issue was in the NIC firmware having a problem loading the png file. Is there an easy way for me to pretty up the menu to a simple white text on black background? I haven’t worked with php before, but thought I’d ask before researching the ‘colour’ and ‘cpair’ parameters of the print statements.

I figured out the issue, and I’m here to report I’m an idiot. 🙂

The original Windows Server 2012 installation had a 100GB system partition.

When I created the test VM, I used the default of 60GB for a system partition. My bad. The clues were there (Single Disk - Not resizable), I just missed them. If I could make a request: If the target partition is smaller than the source, can an error be sent to the screen, or logged to a file somewhere? It may have reported an error to the screen, but then it scrolls by very fast before rebooting. I’d like to thank both of you for your time in helping me with this issue! It looks like FOG will work very well for us in replacing Ghost.