Download Task Failed

[Wayne Workman]

@fsu1tm In the Troubleshoot FTP article below, in the credentials section, it tells you exactly what needs to match, and exactly where it’s set.

Let us know if you need help.

[fsu1tm]

OK. Found the two sections within FOG for TFTP password and Storage Management password. I made sure that both of those were set to the same password (user was already set the same) as the local Ubuntu fog user and the password that I used when setting up MySQL. I saved both settings, closed FOG and rebooted the server. I reopened FOG and verified the password held and it did. I then went to Storage Management to verify the password held there. As soon as I clicked on Storage Management, I got a message that my database schema was out of date and that I needed to click the button to update. I clicked the button and now get a lot of MySQL errors about can’t create tables, etc. On the PLUS side, I can now log into Ubuntu FTP from another workstation. What do I do about these MySQL errors that are returned through the FOG interface?

Thanks again.

[Wayne Workman]

You changed your MySQL password?

You’ll also need to update that user/pass inside FOG Config -> Fog Settings -> Fog Storage Nodes

[fsu1tm]

No. I set the MySQL password when setting up FOG.

[fsu1tm]

I can’t even get into Fog Config -> Fog Settings -> Fog Storage Nodes. When I got to Fog management, it takes me directly to Database Schema Installer/Updater.

[Tom Elliott]

Have you checked to ensure mysql was actually running?

[fsu1tm]

I have not but I just restarted the server and made no changes to MySQL. Sorry, Newb here, but how would I check to see if it’s actually running?

[Tom Elliott]

Well,

Ubuntu has issues with mysql. Particularly anything 12 and greater seems to be hugely a problem from my experience.

The quickest way to see if things are running would be:
sudo service mysql status

If it’s dead, you’ll restart it with:
sudo service mysql restart

Also, if it’s dead, you’ll need to restart the fog services (after mysql is restarted):

sudo service FOGMulticastManager restart
sudo service FOGScheduler restart
sudo service FOGImageReplicator restart

If you’re on SVN you’ll also probably need to add:
sudo service FOGSnapinReplicator restart

To help prevent this in the future, follow these steps as needed/particularly the rc.local steps.
https://github.com/fogproject/fogproject/issues/1

[fsu1tm]

Interesting. I ran “sudo service mysql status” and it responded that mysql was running but I went ahead and did “sudo service mysql restart”. I then did the FOG restarts. Each of those replies looked like (depending on process):

*Restarting FOG Comupter Imaging Solution: FOGScheduler
start-stop-daemon: warning: failed to kill 1152: no such process

But now I can get into FOG and it’s not taking me directly to Database Schema Update/Installer so that is good.

I then tried to upload an image but the client is getting a TFTP Timeout error and rebooting. I gues that I am still stuck on the credentials.

When I log into the machine - username = fog, password = xxxxx
When I log into FOG via FireFox - username = fog, password = password
When I check, FOG_TFTP_FTP_USERNAME = fog, FOG_TFTP_FTP_PASSWORD = xxxxx
When I check, FOG_STORAGENODE_MYSQLUSER = fogstorage
When I check, FOG_STORAGENODE_MYSQLPASS = fs87054970106

xxxxx is not my real password but the others are. The TFTP password does match the machine login password.

It’s interesting that when MySQL was installed during the FOG install that I used xxxxx as the MySQL password but the
FOG_STORAGENODE_MYSQLPASS is something totally different. Does this matter?

I can FTP from my Win7 computer into the FOG machine using: username = fog, password = xxxxx

Not sure where things are going wrong now.

[Tom Elliott]

@fsu1tm I sent you a message in chat as I am sure we can help fix this issue for you. It’s relatively simple to work out.

The FOG_STORAGENODE_MYSQLUSER and FOG_STORAGENODE_MYSQLPASS are for storage nodes to link to a central fog server.

Hopefully this helps explain that. These are not what you would want to put in your main server, though I suppose it wouldn’t hurt them either.