Random Hosts Added to Group

[UWPVIOLATOR]

@Tom-Elliott

No sir. Just the ones selected from the filter.

[Wayne Workman]

@UWPVIOLATOR I’d say run these maintenance/cleanup commands for good measure & try again. Bad entries in the DB can cause weird stuff. https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands

[UWPVIOLATOR]

@ablohowiak @andjjru

Can you guys try this. I am out until Monday.

[falko]

@Wayne-Workman Not having made new groups in a while I noticed last week I was having the same issue.

Followed the Database Maintenance Commands and issue resolved

[UWPVIOLATOR]

@Wayne-Workman

This worked. Thank you

[UWPVIOLATOR]

@Wayne-Workman

Its doing it again.

[Wayne Workman]

@UWPVIOLATOR can you figure out whats causing bad entries in the db? It’s a fog issue I think, but we need to narrow in on what exactly it is.

[UWPVIOLATOR]

@ablohowiak

[UWPVIOLATOR]

@Wayne-Workman @ablohowiak

Wayne we have updated to RC 7 and still it is still doing it. What should we be looking for? I do not have access to the database so that has to be done by @ablohowiak or @andjjru

[Wayne Workman]

@UWPVIOLATOR What I would do is run the maintenance commands, and then I would open up notepad and change all the maintenance commands into select statements. I’d then ask the team to start noting what they do, when they do it concerning fog. Then I’d just start running those select statements every 15 minutes to every half hour - and when the bad row pops up, I’d ask around and see what people did during that time. I’d also look into the history table for things there during the same time. I’d look in the apache error log for something during that time. Even if you find no errors in these logs, it’s worthwhile to see what IS in there during that time, those can be clues. Then - I would begin the tedious task of reproducing the problem and identifying the single thing that is causing it. Reproducing the problem is a lot of educated guesswork based on what you think is causing the problem. If at the time the issue happens for example, someone was registering and imaging a new system - You’d have to test registering by itself - then imaging - using the same image they did - and possibly even in debug mode to identify the single thing that is doing it. Just as example. What I’m expecting though is it’s being caused by something being done in the web GUI - you guys just need to figure out what that thing is - and narrow in on it by separating out variables & unknowns and testing individual things. Example - I don’t know if my application isn’t working or if my antivirus is blocking it. Well, uninstall the AV and try. You have to isolate. And to begin isolating, you have to have a general idea of what you’re isolating.