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 ?
Posts made by lebrun78
-
RE: updating database very long
-
RE: updating database very long
The task is finished, so I suppose the database update is successful.
-
updating database very long
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
-
RE: Win10 slow after imaging
How could I do it in the script preparing my master ?
-
Win10 slow after imaging
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
-
RE: Deploy associed image on boot menu
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
-
Deploy associed image on boot menu
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
-
RE: FOG 1.6 Testing Needed - Help would be greatly appreciated as needed
[root@cosinus fogproject]# git pull Already up-to-date.
But when I execute installfog.sh I have Version: 1.5.4.562 Installer/Updater
-
RE: FOG 1.6 Testing Needed - Help would be greatly appreciated as needed
Hello,
I try to upgrade my test server to 1.6 version.
But I have a problem with git:
When I try tu update the directory I get : “fatal: ‘working-1.6’ does not appear to be a git repository”[root@cosinus fogproject]# git checkout working-1.6 Already on 'working-1.6' [root@cosinus fogproject]# git pull working-1.6 fatal: 'working-1.6' does not appear to be a git repository fatal: The remote end hung up unexpectedly [root@cosinus fogproject]# git reset --hard HEAD is now at d1ea5e5 Fix api for slack return information [root@cosinus fogproject]# git pull working-1.6 fatal: 'working-1.6' does not appear to be a git repository fatal: The remote end hung up unexpectedly
Arnaud
-
RE: white screen trying to view schedulled tasks
Here are the log when I try to list scheluded tasks
in /var/log/httpd/ssl_error_log[Mon Jun 04 08:24:48 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:27:09 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:36:00 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 95, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 08:47:45 2018] [error] [client 192.168.1.10] PHP Warning: trim() expects parameter 1 to be string, array given in /var/www/html/fog/lib/fog/fogbase.class.php on line 1316, referer: https://fogus.univ-rennes1.fr/fog/management/?node=task&sub=active [Mon Jun 04 14:10:47 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 54, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 14:11:18 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 14:29:39 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active [Mon Jun 04 15:18:51 2018] [error] [client 192.168.1.10] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/fog/lib/fog/fogcron.class.php on line 86, referer: https://fogus.univ-rennes1.fr/fog/management/index.php?node=task&sub=active
Arnaud
-
RE: white screen trying to view schedulled tasks
Yes I’m still on 1.4.4 with my server on production.
Is PHP-FPM available only on newer version ? -
white screen trying to view schedulled tasks
Hello,
When I want to check schedulled tasks, I get a white screen.
In same time, httpd process go to 100%cpu on the server…memory_limit is set at 1024M in php.ini
Could you help me ?
Arnaud
-
view delayed tasks
Hello,
How could I servey delayed task with fog 1.4.4 ?
Thank
Arnaud
-
RE: Problem during upgrade from 1.5.0 to 1.5.2
@george1421
Hello,
This problem reapair updating to 1.5.3 on my test server running with centos 6.9.
The solution you proposed is always available.Thank you for you work