Two "new fog client" settings?

[Wayne Workman]

Maybe it’s just me, but I just saw two “use new fog client” thingies in the latest revision.

[Tom Elliott]

What? Where?

[Wayne Workman]

@Tom-Elliott FOG Configuration -> FOG Settings -> FOG Service

There were two of them. I was helping @lessndro on Ubuntu 14.04 and put the latest trunk as of a few minutes ago on… he has two of those settings in there.

[Joe Schmitt]

I’m not seeing it:

And I’m on 3654.

[Wayne Workman]

@Jbob Promise you he has two lol… get in touch with him and look.

[lessndro]

Hello,
i think i have a lot of duplicate options… this is a image i posted on the other topic
https://forums.fogproject.org/uploads/files/1435136067281-fog1.png

[Wolfbane8653]

I HAD this exact issue. Its an issue from the mysql schema updater. I believe Tom has fixed this in a few latest update (since sourceforge is down) but those of you with the issue now will keep these duplicated entries… This is for experts only!

This process will be purging all your settings. I know that sucks but it beats going line by line and deleting all these duplicate rows.

• Create a duplicate database or backup to be easily referenced

mysql -u root -p
Create DATABASE fogbck;
exit;

• dump fog database completely into fogbck (you may need to add password)

mysqldump -u root fog | mysql -u root fogbck

• Double check the fogbck database to see if everything indeed copy over…

• And here comes the scary part…

mysql -u root fog
drop table globalSettings;

• now reinstall fog

./installfog.sh

• schema update yada yada yada

• and re-tweak your settings(passwords and such). FYI your AD password is stored in fogbck so you can go and look it up there.

[cml]

What about something like this?

• Showing I have duplicate values.

mysql> select * from globalSettings where settingKey="FOG_TFTP_PXE_KERNEL";
+-----------+---------------------+------------------------------------------------------------------------------------+--------------+-----------------+
| settingID | settingKey          | settingDesc                                                                        | settingValue | settingCategory |
+-----------+---------------------+------------------------------------------------------------------------------------+--------------+-----------------+
|         6 | FOG_TFTP_PXE_KERNEL | Location of kernel file on the PXE server, this should point to the kernel itself. | bzImage      | TFTP Server     |
|       147 | FOG_TFTP_PXE_KERNEL | Location of kernel file on the PXE server, this should point to the kernel itself. | bzImage      | TFTP Server     |
+-----------+---------------------+------------------------------------------------------------------------------------+--------------+-----------------+
2 rows in set (0.00 sec)

• Dropping duplicates.

mysql> ALTER IGNORE TABLE globalSettings ADD UNIQUE INDEX (settingKey);
Query OK, 133 rows affected (0.01 sec)
Records: 133  Duplicates: 2  Warnings: 0

mysql> ALTER TABLE globalSettings DROP INDEX SettingKey;
Query OK, 131 rows affected (0.00 sec)
Records: 131  Duplicates: 0  Warnings: 0

• Showing the duplicate is now gone.

mysql> select * from globalSettings where settingKey="FOG_TFTP_PXE_KERNEL";
+-----------+---------------------+------------------------------------------------------------------------------------+--------------+-----------------+
| settingID | settingKey          | settingDesc                                                                        | settingValue | settingCategory |
+-----------+---------------------+------------------------------------------------------------------------------------+--------------+-----------------+
|         6 | FOG_TFTP_PXE_KERNEL | Location of kernel file on the PXE server, this should point to the kernel itself. | bzImage      | TFTP Server     |
+-----------+---------------------+------------------------------------------------------------------------------------+--------------+-----------------+
1 row in set (0.00 sec)

[Wolfbane8653]

excellent!

…but double check your settings afterward.

[Tom Elliott]

I’m solving this. I added the very code to remove duplicates to the schema. So it is still possible, in the future, to have this same issue. However, for the time being this should be fixed.