Database Schema Installer / Updater

[Thiago]

login to your mysql and set root password.

mysql -u root -p
use mysql;
UPDATE user SET password=PASSWORD(‘Your-pass-for-mysql-here’) WHERE User=‘root’;
exit;

the password must be the same as configured during installation by foginstall script

and then try update your schema again.

works for me.

[Tom]

@Thiago Thank for the advice, Unfortunately, it did not help. I’m a bit frustrated.
Since it’s VM, I’m ready to revert back and try this upgrade again.

[Wayne Workman]

@Tom look at this article, thiere is a section on db issues that is specific to Ubuntu. https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

[Tom]

@Wayne-Workman Thank you, I went through the troubleshooting steps and could not figure out what’s wrong.
I’m going to revert back and start over.
Does anyone have instructions on how to do it and what to look for?
Is there anything I should do pre and post upgrade?

Thanks,

Tom

[Wayne Workman]

@Tom said:

anything I should do pre and post upgrade?

I’d recommend going through 0.32 first, and then to 1.2.0.

[george1421]

I guess I have to be captain obvious here (well may be not so much).

What would you loose if you spun up a new instance of the FOG server using the current trunk image?

Would it be just the registrations, the images, what would be the real impact of starting over?

The reason why I asked is: Will it take more time to upgrade from 0.30 to 1.20 and work out all of the kinks or just recreate the new environment?

Unless I’m off here, you can not deploy images created with 0.30 with the trunk build of fog 1.2.0. The image format has changed. Your best bet would be to deploy an image with fog 0.30 and then right away recapture it with the trunk build of 1.2.0. That way you get the image in the correct format. If its the registrations there may be a way to export the hosts and then re-import them into fog. But again will it take less time to just reenter them into the latest release of FOG.

[Wayne Workman]

@george1421 said:

Unless I’m off here, you can not deploy images created with 0.30 with the trunk build of fog 1.2.0.

You can, you’d just change settings from partclone to partimage.

But I agree, if there is not much to loose, just rebuild everything using fog trunk. The new client auto-registers computers anyways.

[Tom]

@george1421 Thank you for the advice. My knowledge about Ubuntu and FOG is very basic. Can you provide more info (step by step would be great) how to accomplish this?

Thank you very much,

Tom

[Wayne Workman]

@Tom https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

[Tom]

@Wayne-Workman So, I have decided to start fresh, I installed Ubuntu 14.04.3 and fog 1.2.0 ( It was my understanding that the trunk is beta version).
My issue now is that the host is not booting to PXE.
Set correctly opt 66 and 67 (undionly.kpxe) and tried to work with dnsmasq, but I cannot figure this out.
I can get to the management console via IE over the network.
Should I start a new thread?

Thanks,

Tom

[JJ Fullmer]

@Tom
Trunk isn’t beta in the traditional sense. I would strongly recommend upgrading to it. If there are problems you post it on the forum and often the issue is fixed in a manner of hours.

[Tom Elliott]

@Arrowhead-IT Sometimes even minutes.

[Wayne Workman]

@Tom said:

My issue now is that the host is not booting to PXE.

Make sure UFW is off. Check this out: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP