14500 computers in the database are a lot of. I had troubles in the past when I tried to list my 8000 computers, this was solved with the php-fpm module but maybe in you case the problem is other (timeouts in the database or used memory)
Any error in the apache logs?
Is a random situation, I have tried to replicate the issue but was unsuccess. The problem is with the first time that the FOGservice runs, if you reboot the computer, in the second time the service runs well. But is necesary do it manually :(
Hi @JB2019 ,
If you want to install the last version of FOG please follow the instructions of the next link:
You can see it in:
Host Image History bug?
https://forums.fogproject.org/topic/12934/host-image-history-bug
If you want to not update the server to this release you can do a little change of code, you can see it in:
https://github.com/FOGProject/fogproject/commit/501e2e947abe55f61fec434751e51e517dcba4d4
Hi @Florent ,
Which version og FOg are you using? I think that in the last release this problem is solved
@Sebastian-Roth Yes, we do sysprep to deploy the image but we setup the FOG client to start the service as the post says.
@george1421 In the FOG client log:
10/05/2019 11:24 Main Overriding exception handling
10/05/2019 13:46 Main Overriding exception handling
10/05/2019 13:46 Main Bootstrapping Zazzles
10/05/2019 13:46 Controller Initialize
10/05/2019 13:46 Controller Start
10/05/2019 13:46 Service Starting service
10/05/2019 13:46 Bus Became bus server
10/05/2019 13:46 Bus Emmiting message on channel: Status
10/05/2019 13:46 Service Invoking early JIT compilation on needed binaries
------------------------------------------------------------------------------
--------------------------------Authentication--------------------------------
------------------------------------------------------------------------------
10/05/2019 13:46 Client-Info Version: 0.11.16
10/05/2019 13:46 Client-Info OS: Windows
10/05/2019 13:46 Middleware::Authentication Waiting for authentication timeout to pass
We can see that the service trid to start at 11:24, then two hour later after reboot the computer the service start well.
In the windows event log we can see more information:
At 11:20 the system starts and at 11:24 an error:
This error launchs a 7000 event, in this page we can see more info about it:
A service does not start, and events 7000 and 7011 are logged in the Windows event log
The service control manager waits for the time that is specified by the ServicesPipeTimeout entry before logging event 7000 or 7011.
Services that depend on the Windows Trace Session Manager service may require more than 60 seconds to start.
Therefore, increase the ServicesPipeTimeout value appropriately to give all the dependent services enough time to start.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
839803 The Windows Trace Session Manager service does not start and Event ID 7000 occurs
Hi,
With the 1.5.6 release version is available one new plugin: Host Status.
This plugin say you the state of the computer in the host edit page:
This plugin detects the OS that is running in the computer:
The state is detected on fly and only in the host edit page.
NOTE: when you search one host or hosts, in the result list appears the state of the computers too, but this state is read from the database and this entry in the database is updated by FOGHostPing daemon. The daemon need time to iterate with all computers and update his state. If you have a lot of PC in your FOG server, the daemon takes one second per PC to update his state, there may be discrepancies between the two states (host status plugin and FOGHostPing daemon)
Yes, all computers are setup as service delayed. Is possible increase the delayed time?
Hi,
Sometimes when we deploy an image in one IT room and Windows boots, the FOGService doesn´t start. I saw the properties of the FOGService service in the console and this one start delayed. Does´t happen always, but if we deploy 40 computers, maybe 10 don´t start the service.
Normaly the problem happen in computers with SSD disks, we think that the problem is that the system boots so quickly that one or more dependecies don´t start.
Any idea?
Hi @Sebastian-Roth and @EduardoTSeoane ,
I tested the changes in my dev environment and the suggestions work fine. I think we can push the changes in the repository.
I don´t use the location plugin but Ithink that the problem is the same. Maybe, @Tom-Elliott can say us want think about them XD and the reason it does not wok correctly