Version 1.2.0 released!

[Tom Elliott]

All are having problems with the database schema problem check your fog settings file in/opt/fog/.fogsettings and make sure snmysqlpass is correct for the db password

[andyroo54]

This post is deleted!

[Tom Elliott]

If it installed properly, you should have the /opt/fog/.fogsettings

My guess, unless somebody else removed it, is something wasn’t completely installed properly.

I’d recommend a reinstall.

[andyroo54]

Wow I am stupid… I forgot to check hidden files CTRL+H (ls -a)then I found the file. Updated password and done! Thanks Tom and thanks to the Fog team we are now on 1.2 can’t wait to test windows 8…!

The upgrade was super easy just don’t mind my stupidity!

Thanks again!

[Sivasubramaniam.T]

Congrats Fog Team. Thanks for your great effort.

[Daniel Anderson]

I just signed up to say thanks. I’ve been using FOG for the deployment of our training lab since 2012ish and I really wouldn’t want to use anything else!

[chclark]

Thanks for the advise updated my fog server today

[BigDawg986]

Please clarify, when this says now supports multiboot re-sizable imaging, do you mean multi-partition resizable?

I am still on version .31 and have been hesitant to upgrade because I am the only tech in a 1,500 PC 3,000 user school and can’t risk the downtime.

[Jaymes Driver]

[quote=“BigDawg986, post: 33945, member: 75”]Please clarify, when this says now supports multiboot re-sizable imaging, do you mean multi-partition resizable?

I am still on version .31 and have been hesitant to upgrade because I am the only tech in a 1,500 PC 3,000 user school and can’t risk the downtime.[/quote]

No when it says Multiboot I means Multiple Operating Systems on the hard drive, such as Windows and Linux on one machine but being able to choose the OS to boot to at each reboot.

[BigDawg986]

[quote=“Jaymes Driver, post: 33964, member: 3582”]No when it says Multiboot I means Multiple Operating Systems on the hard drive, such as Windows and Linux on one machine but being able to choose the OS to boot to at each reboot.[/quote]

Thanks, I should have figured as much but whenever I set up multiboots I always put each OS in a separate partition so that’s why I asked.

[Tom Elliott]

That should still work for you.

Resizable was never “partition” dependent, just when it was initially implemented it was for XP which only had one partition on a default install.

[Josh Scoville]

Hello all,

What database is the new version of FOG using? I just set up a new server as I need to migrate off some old hardware. I did a fresh install and exported/imported my hosts. I copied over my image files and want to be able to export/import the image database info, but there is no option for this. So I thought I’d mysqldump the images table and import it into the 1.2 database on the new server.

I may be totally going about this the wrong way and if so, please let me know, but my question is: how do I find the database name that 1.2 is using? When I go to mysql and do a “show databases”, I see no “fog” database like on the old server.

Please advise as my old server was having problems saying it could not find the entire image file, so I thought I’d go ahead and migrate to the new one. We use FOG heavily for our school system.

Thanks!

[Tom Elliott]

[quote=“Josh Scoville, post: 34427, member: 25343”]Hello all,

What database is the new version of FOG using? I just set up a new server as I need to migrate off some old hardware. I did a fresh install and exported/imported my hosts. I copied over my image files and want to be able to export/import the image database info, but there is no option for this. So I thought I’d mysqldump the images table and import it into the 1.2 database on the new server.

I may be totally going about this the wrong way and if so, please let me know, but my question is: how do I find the database name that 1.2 is using? When I go to mysql and do a “show databases”, I see no “fog” database like on the old server.

Please advise as my old server was having problems saying it could not find the entire image file, so I thought I’d go ahead and migrate to the new one. We use FOG heavily for our school system.

Thanks![/quote]

It sounds to me like the FOG database never got created on your system. Did you not run through the Schema installer/updater?

[Josh Scoville]

I did run the schema update and I can log into the new server web gui and was even able to import hosts from a csv file, which did import and show up.

[Tom Elliott]

In /var/www/fog/lib/fog/Config.class.php under the db_settings method, there should be a line like:
[code]define(‘DATABASE_NAME’, ‘fog’);[/code]

This should be the name of the database per default. If you edited the file or this isn’t set correctly, it should, at the least tell what the new database name is being referenced.

[Josh Scoville]

That’s weird. It says fog in the name setting in the php file, but when I gype mysql > show databases; fog is not listed. I try a “use database” command, but it says access denied. Could it be hidden or something? It has to be there, obviously since the web interface is running?

Am I even on the right track trying to import this image table? Or should I just recreate the names?

[Tom Elliott]

I’d recommend recreate the names. I don’t know why the db is reporting that it’s access is denied, but maybe the user you’re logged into mysql with isn’t allowed?

[Josh Scoville]

OK, this is weird. I thought I’d try creating a new image and see if I can get it to work. This time when I click the button to add the image, I get a schema update message, so I click the button to update.

I get a tone of errors back inclucing the following:

[CODE]Update/Install Failed!
The following errors occured

Update ID: 1 - 0

Database Error:

Database SQL:

CREATE DATABASE fog

Update ID: 1 - 1

Database Error:

Database SQL:

CREATE TABLE fog.groupMembers (
gmID int(11) NOT NULL auto_increment,
gmHostID int(11) NOT NULL,
gmGroupID int(11) NOT NULL,
PRIMARY KEY (gmID),
KEY new_index (gmHostID),
KEY new_index1 (gmGroupID)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1 ROW_FORMAT=DYNAMIC

Update ID: 1 - 2

Database Error:

Database SQL:

CREATE TABLE fog.groups (
groupID int(11) NOT NULL auto_increment,
groupName varchar(50) NOT NULL,
groupDesc longtext NOT NULL,
groupDateTime datetime NOT NULL,
groupCreateBy varchar(50) NOT NULL,
groupBuilding int(11) NOT NULL,
PRIMARY KEY (groupID),
KEY new_index (groupName)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1

Update ID: 1 - 3

Database Error:

Database SQL:

CREATE TABLE fog.history (
hID int(11) NOT NULL auto_increment,
hText longtext NOT NULL,
hUser varchar(200) NOT NULL,
hTime datetime NOT NULL,
hIP varchar(50) NOT NULL,
PRIMARY KEY (hID)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1

Update ID: 1 - 4

Database Error:

Database SQL:

CREATE TABLE fog.hosts (
hostID int(11) NOT NULL auto_increment,
hostName varchar(16) NOT NULL,
hostDesc longtext NOT NULL,
hostIP varchar(25) NOT NULL,
hostImage int(11) NOT NULL,
hostBuilding int(11) NOT NULL,
hostCreateDate datetime NOT NULL,
hostCreateBy varchar(50) NOT NULL,
hostMAC varchar(20) NOT NULL,
hostOS int(10) unsigned NOT NULL,
PRIMARY KEY (hostID),
KEY new_index (hostName),
KEY new_index1 (hostIP),
KEY new_index2 (hostMAC),
KEY new_index3 (hostOS)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1

Update ID: 1 - 5

Database Error:

Database SQL:

CREATE TABLE fog.images (
imageID int(11) NOT NULL auto_increment,
imageName varchar(40) NOT NULL,
imageDesc longtext NOT NULL,
imagePath longtext NOT NULL,
imageDateTime datetime NOT NULL,
imageCreateBy varchar(50) NOT NULL,
imageBuilding int(11) NOT NULL,
imageSize varchar(200) NOT NULL,
PRIMARY KEY (imageID),
KEY new_index (imageName),
KEY new_index1 (imageBuilding)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1

Update ID: 1 - 6

Database Error:

Database SQL:

CREATE TABLE fog.schemaVersion (
vID int(11) NOT NULL auto_increment,
vValue int(11) NOT NULL,
PRIMARY KEY (vID)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1 ROW_FORMAT=DYNAMIC

Update ID: 1 - 7

Database Error:

Database SQL:

CREATE TABLE fog.supportedOS (
osID int(10) unsigned NOT NULL auto_increment,
osName varchar(150) NOT NULL,
osValue int(10) unsigned NOT NULL,
PRIMARY KEY (osID),
KEY new_index (osValue)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1

Update ID: 1 - 8

Database Error:

Database SQL:

CREATE TABLE fog.tasks (
taskID int(11) NOT NULL auto_increment,
taskName varchar(250) NOT NULL,
taskCreateTime datetime NOT NULL,
taskCheckIn datetime NOT NULL,
taskHostID int(11) NOT NULL,
taskState int(11) NOT NULL,
taskCreateBy varchar(200) NOT NULL,
taskForce varchar(1) NOT NULL,
taskScheduledStartTime datetime NOT NULL,
taskType varchar(1) NOT NULL,
taskPCT int(10) unsigned zerofill NOT NULL,
PRIMARY KEY (taskID),
KEY new_index (taskHostID),
KEY new_index1 (taskCheckIn),
KEY new_index2 (taskState),
KEY new_index3 (taskForce),
KEY new_index4 (taskType)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1

Update ID: 1 - 9

Database Error:

Database SQL:

CREATE TABLE fog.users (
uId int(11) NOT NULL auto_increment,
uName varchar(40) NOT NULL,
uPass varchar(50) NOT NULL,
uCreateDate datetime NOT NULL,
uCreateBy varchar(40) NOT NULL,
PRIMARY KEY (uId),
KEY new_index (uName),
KEY new_index1 (uPass)
) ENGINE=MyISAM AUTO_INCREMENT=1 DEFAULT CHARSET=latin1

Update ID: 1 - 10

Database Error:

Database SQL:

INSERT INTO fog.users VALUES (‘’,‘fog’, MD5(‘password’),‘0000-00-00 00:00:00’,‘’)

Update ID: 1 - 11

Database Error:

Database SQL:

INSERT INTO fog.supportedOS VALUES (‘’,‘Windows XP’, ‘1’)

Update ID: 1 - 12

Database Error:

Database SQL:

INSERT INTO fog.schemaVersion VALUES (‘’,‘1’)

Update ID: 2 - 0

Database Error:

Database SQL:

INSERT INTO fog.supportedOS VALUES (‘’,‘Windows Vista’, ‘2’)[/CODE]

[Jose Antonio Sanchez]

I keep getting the “Database Schema Installer / Updater” message this all the time now with clean installs of FOG 1.2.0 (three different FOG Servers).

The server works, then I can create images at first, deploy them, then after a while, boom! nothing. All I get is the “Database Schema Installer / Updater” page.

Is there a fix for this? I left the MySQL password blank and tried the fixes other’s used as indicated on this thread. How can I avoid this? I can’t deploy images now…

Any help appreciated.

Thank you.

[Tom Elliott]

Grrr, Read the forums.

Anyway,

Check the /opt/fog/.fogsettings specifically the snmysqlpass variable setting and make it B"" in the case of blank, or set it to that of the mysql root password you need.