Snapins removed from Previously registered hosts
Since the snapin hash issue of last week. I noticed that all the hosts we have registered, have lost the assigned snapins they used to have. Is there a way to get those settings back from a backup? or do we need to reassigned snapins to 3000 hosts?
@Wayne-Workman I was able to get it rolled back. It is looking like the snapins are back now. thanks for the help
@Wayne-Workman OK, I will give that shot.
@adukes40 Well, I’d say make a new backup first so that you can go back if needed. Like this:
mysqldump fog > /root/fogDB.sql
Or via the web interface. But CLI is more reliable.
Then I’d try to restore the one called
fog_sql_35first. If that isn’t good I’d go to the
33next, which appears to have a little more data in it.
@Wayne-Workman Tom was working on my system on the 16th, which has two entries, but I just noticed them missing, so not sure when it went missing. The one for the 13th is 0 in size, so not sure how far to go.
@adukes40 Those files have date/time stamps and versions. When were things correct last?
The nomenclature for the backups is:
Don’t go further back than you need.
You can restore the files via CLI like this:
mysql < file
If a user/pass is needed just include those before the
@Tom-Elliott Which would I choose
@adukes40 no. There is no code that removes associations unless the associations are invalid or somebody goes and removes the associations. There should be a backup db on the fog server. If you can get it on your machine you can upload it straight through the GUI.
adukes40 last edited by adukes40
@Tom-Elliott Correct, all the associations have been blown out. How would I restore them from the backup?
Also I did not get around to updating the nodes until the weekend, so the nodes are on version 39, but master on 33. Would that cause it?
What do you mean not assigned? Snapin tasks were cleaned up, but we didn’t touch associations at all. You can recover from backup or you can reassign via groups.