@sebastian-roth I have absolutely no problem about what you said and agree on upgrade. I only did the post to see if we may have a “bad habit situation” on updating the host informations. So, I will move onto stable (well, i dont like to risk productivity, so in production environment i will stick to stable release).

About pending macs. We dont use fog client at all but sometimes on fog pages i see we have pending macs and it wants me to decide about it. I somehow linked this to the issue in thoughts this is why i asked. ( will do upgrade as soon as possible with a junk-removed state of db then see what happens)

And the most important thing, BIG thanks for you folks who volutarily do such a huge and very very good job! We cant be grateful enough for your work!

here it comes again now, i have a log file that your script created and i think this is not the usual situation. here is what happened now:

task was deploying and DURING that task the host data was updated with new mac address (i am aware that it is not best usage it was not me)

so i have the log, where to put it? mail maybe? it has many info about our setup, maybe not best to have it on a forum ,) let me know how to share with it with you.

Final case: The debugging of this state closed. No solution found with those machines in testing. I ended up with a fully new hardware architecture, a lot newer machine. Fully reinstall again, now on Ubuntu 14.04.2 LTS, 64bit. Fun fact, issue never again happened. Maybe candid camera was removed from room… damn, it was a bit frustrating haveing such insane malfunction with a normally working software. A week passed by, no issue anymore. Strange.

Thx for replies and tries in helping!

@wayne-workman hehe, sanitize i will, well, i already started reading it but work came in the office in waves, so i postponed it to tomorrow. I will send or post it here from work. btw i kept your address from last db transaction we did together.

@pabloinza

No, not yet. We have some other issues what makes us delay it a bit, network staff has issues cos of powerfailures, things are not that happy I will make them continue tests.

Finally, done. Solution: few switch was not ok, network config was changed in a way we was not aware (other device needed different setup and was not properly separated. Now is ok! And, as for full solution multicast tables needed manual clearing. (when we had solved testing, clients seemed stuck, now they dont.)

all ok now, mass tests will come soon for performance (as now multicast speed a bit low…

Take your time, as I have learned to solve it for me is not urgent. You told me if i think it needs further investigation, let it be posted in separate thread, so i did