I have reboot the server yesterday,
Now updating database is very fast.
And I receive mails for task results…

I think the problem appeared when I set “FOG_EMAIL_ACTION”.

Thanks for your answers

@Sebastian-Roth
Thank you,
I tried the procedure you proposed but , with a log for request over 2 seconds, I don’t obtain anything in my /var/lib/mysql/fogus-slow.log .

Precisely, it is following a purge of the deployment reports that the problem appeared.
How could I evaluate access time off a base log request ?

The task is finished, so I suppose the database update is successful.

Hello,
Our fog server is working very well for several years.
Its configuration has not changed for 1 year.
But for 2 mounth, when deploying image, the sequence “updating database” is very long, about 2 minutes.
Everythings else seems to be working nice.

Arnaud

Thank you
I try it now

How could I do it in the script preparing my master ?

Hello,
Windows 10, with a large image, about 120Go, is very slow after imaging.
I suppose that windows is indexing files so hard drive is very sought for several minutes.
I have mechanical hard drives, and it’ better with SSD drives.

How could I avoid this problem

Arnaud

We have made a special setting in deploy.image menu for the computers of the room. Then login and password are not requested to access to deploy menu.

#login
params
param mac0 ${net0/mac}
param arch ${arch}
param hostname ${hostname}
goto host_${hostname} || goto autres
:host_bug
:host_win10-3
:host_i207m01
:host_i207m02
:host_i207m03
:host_i207m04
:host_i207m05
:host_i207m06
:host_i207m07
:host_i207m08
:host_i207m09
:host_i207m10
set username userlogin
set password userpassword
params
param username userlogin
param password userpassword
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
goto fin
:autres
login
params
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:fin

Hello,

On boot menu, actually, users can deploy every images on a host .
I work in a IT school, so student may reset host after test, like a sandbox.
Could it be possible to limit deploy the associated image to the host ?
Or/and could it be possible to limit a user to access to only one image ?

Lebrun