Remoted in. Issue possibly appeared from an Ubuntu update.

Essentially, however, the services were not able to start because PHP was missing the mysqli extension. I suspect it was removed (or at least unlinked) during one of these OS updates.

Cleaned up/fixed this by editing the /opt/fog/.fogsettings file and removing the php_ver, php_verAdds, and packages lines. Reran the installer and everything needed installed properly and the services all appear to be working properly too now.

Possibly. I’m not getting the 500 error, but everything else looks the same.

Retesting on another machine now. I will update to 1.3.4 and see if the problem goes away!

Yes. It’s not the simplest methodology and is highly dependent on your DHCP configuration layout, but it can be done. For the most part, however, if you’re using the ipxe named files, you should really use ipxe.pxe. I only recommend undionly.kpxe as it maintains the undi stack to all nics. undionly.kkpxe is meant for those with buggy bios’ (anything that undionly.kpxe works on will work with undionly.kkpxe as well) but I can’t say the same about ipxe.pxe, though it should work for most systems.

@jeremy-kou I still think installing the latest will help fix this for you.

Per our chat, it seems you are not running the FOG Version 1.2.0 as the error messages you’re seeing were not present in the 1.2.0 release to begin with.

I don’t know if it will install nicely on Redhat 5.3 or not because I’ve been working with CentOS 6 ever since I started working with FOG. That said, I already am aware you have PHP 5.6 which leads me to think your server is pretty much capable.

To me this sounds like a partition layout issue.

The messages from the kernel appear to me to be informative, not show stopping. These messages were always present in 1.2.0 kernels iirc. What exactly is happening when you try to capture?

Instructions can also be found here: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

To add on, if your fogserver cannot access the internet, the page will be blank because it has no way to access the kernels.

@xx23piracy Good catch!

I reviewed them and yes, they are laptops. I tracked one down and yes, it is adding MAC addresses that it previously didn’t have a record for. It just worried me because the hosts already existed and have been there for a while then it all the sudden started adding all these extra addresses.

So…resolved it looks like. Thanks!

@Tom-Elliott The register and image setup is confirmed to be working in the latest release 🙂 Thanks!

For all to see and understand what’s happening.

1.3.0 had some strangeness I was unaware of. This things were:

It had no error reporting on schema updates. Because of no error reporting, even a bad schema (bad sql) would appear as if all ran ok.

1.3.1 corrected these issues. Apparently at schema version point 136 and 140 there was an issue in creating the primary fields. These two schema versions handled the creation of imageGroupAssoc and snapinGroupAssoc.

These issues have been corrected for in 1.3.1 (and are of course present in 1.3.2). If you’re running into these issues, please open mysql and run:

ALTER TABLE `fog`.`imageGroupAssoc` ADD COLUMN `igaPrimary` ENUM('0','1') NOT NULL; ALTER TABLE `fog`.`snapinGroupAssoc` ADD COLUMN `sgaPrimary` ENUM('0','1') NOT NULL;

This would only pose a problem for those that were running on trunk builds that had a schema after these points. If either of them error on the command line (or in phpMyAdmin if that’s what you’re using) please just let me know. If you’re getting the Database ID 236 issue though, I’m pretty sure at the least the alter table of the igaPrimary above will work without any errors.

@Quazz

Thanks. I’ve try your proposition but it seems to boot always on my first dhcp erver who had fog 0.32 as next-server. No dhcp on my fog.

After the choice of your new “ipxe boot”, ipxe search : tftp://ipoffog0.32/default.ipxe

I’m sure it wiil be better with :
tftp://ipoffog1.3.0/default.ipxe

Thanks for your help

Mickael
ch
Sorry if my english is not very good, I’m french

@TomBagley It’s good to hear the tool worked for you and that your issues are solved.

@cerebron said in problem with running basic snapins:

but when i run them throgh snapins, it creates the shortcut, but after clicking on it, nothing happens. I just cannot enter that folder.

Right click on it, go to the security tab, click advanced. There should be a place to take ownership of the file. Do this and see if it lets you into the shortcut or not. If it does, you’ll also have to have the script set permissions on the files it places.

@LibraryMark Please follow the instructions in Tom’s first post in this thread.

@RoweAdmin Thanks for the feedback, I’ll get those items changed. I have no idea why I wrote ‘copy’ or wrote the mounting command backwards. Guess I was pretty tired. Never-the-less, thank you for your feedback. It’s very appreciated.

@Tom-Elliott said in Transferring all images & all host info from (1.2.0) to (1.2.0):

The older export system (1.2.0 and earlier back to 1.0.0 when it was introduced) didn’t take into account the tables existing.

@Moderators important tid-bit of info there.

For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

For future readers: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG