SOLVED Too much traffic on the server FOG
I use FOG 1.3.3, FOG Service 0.11.8 and i think i have a problem between the server and the client.
The CPU on server Fog is 100% and kill apache and mysql with “Out of memory: Kill process or sacrifice child”.
I suppose that the process is “ksoftirqd” and I assumed a problem with the network card.
For test, i have just change IP adress and i restart this server. After the restart, the server it’s OK, for sure, i change again with normal IP and the server crash again.
I suppose that is the FOG Client communicate with this IP adress, but why ?
I have 2000 Client.
Thank you for help.
The Fog Client and Fog Server are up to date and database is fixed.
Now the Fog Server working properly now.
Thank You for your help.
@Sebastian-Roth I do not think it’s the update that damaged it. I think that de database was damaged before and and that’s why I had problems on the server. It’s a suposition, I did not think to check before.
I will try your solution.
@sapeurorca I have not seen a FOG update damaging the database. Not saying that it cannot happen but I have never heard of it.
Maybe try manually fixing it? Try the
myisamchkcommands suggested here: https://stackoverflow.com/questions/8843776/mysql-table-is-marked-as-crashed-and-last-automatic-repair-failed (don’t forget to shut down the DB at first as mentioned)
Hello, I started by updating the FOG Server.
Now FOG Server it’s in 1.5.4 but the client it’s not update.
I noticed an error in the database, in the base “usertracking” and very much traffic :
Traffic => 8Go in 30minutes on the database
These values are normal?
Okay thanks, I’ll try this solution and I’ll come back.
@sapeurorca we are up to version 1.5.4 now and with the release of 1.4.0 I believe the client communication method changed to use a single poll request during this (though that may have been with 1.3.5).
I would highly recommend updating your instance of fog to gain the benefits and features.
If upgrading doesn’t fix the client communication then you can adjust the client check-in time from the fog settings page.