FOG Clients Stop Working



  • CentOS Linux 7.5.1804
    FOG 1.5.6

    I have a lot of clients with FOG.logs like this. Is there any way to fix this other than uninstall reinstall? If not could we get some powershell people together to write a script to uninstall reinstall if it finds log files like this?

     11/20/2019 4:39 PM Service Starting service
     11/20/2019 4:39 PM Log Unhandled exception caught
     11/20/2019 4:39 PM Log     Terminating: True
     11/20/2019 4:39 PM Log     Hash code: 63835064
     11/20/2019 7:44 PM Main Overriding exception handling
     11/20/2019 7:44 PM Main Bootstrapping Zazzles
     11/20/2019 7:44 PM Controller Initialize
     11/20/2019 7:44 PM Controller Start
    
     11/20/2019 7:44 PM Service Starting service
     11/20/2019 7:44 PM Log Unhandled exception caught
     11/20/2019 7:44 PM Log     Terminating: True
     11/20/2019 7:44 PM Log     Hash code: 63835064
     11/20/2019 7:45 PM Main Overriding exception handling
     11/20/2019 7:45 PM Main Bootstrapping Zazzles
     11/20/2019 7:45 PM Controller Initialize
     11/20/2019 7:45 PM Controller Start
    
     11/20/2019 7:45 PM Service Starting service
     11/20/2019 7:45 PM Log Unhandled exception caught
     11/20/2019 7:45 PM Log     Terminating: True
     11/20/2019 7:45 PM Log     Hash code: 63835064
     11/20/2019 7:46 PM Main Overriding exception handling
     11/20/2019 7:46 PM Main Bootstrapping Zazzles
     11/20/2019 7:46 PM Controller Initialize
     11/20/2019 7:46 PM Controller Start
    
     11/20/2019 7:46 PM Service Starting service
     11/20/2019 7:46 PM Log Unhandled exception caught
     11/20/2019 7:46 PM Log     Terminating: True
     11/20/2019 7:46 PM Log     Hash code: 63835064
     11/24/2019 5:13 PM Main Overriding exception handling
     11/24/2019 5:13 PM Main Bootstrapping Zazzles
     11/24/2019 5:13 PM Controller Initialize
     11/24/2019 5:13 PM Controller Start
    
     11/24/2019 5:13 PM Service Starting service
     11/24/2019 5:13 PM Log Unhandled exception caught
     11/24/2019 5:13 PM Log     Terminating: True
     11/24/2019 5:13 PM Log     Hash code: 63835064
     11/25/2019 8:47 AM Main Overriding exception handling
     11/25/2019 8:47 AM Main Bootstrapping Zazzles
     11/25/2019 8:47 AM Controller Initialize
     11/25/2019 8:47 AM Controller Start
    
     11/25/2019 8:47 AM Service Starting service
     11/25/2019 8:47 AM Log Unhandled exception caught
     11/25/2019 8:47 AM Log     Terminating: True
     11/25/2019 8:47 AM Log     Hash code: 63835064
     11/25/2019 8:48 AM Main Overriding exception handling
     11/25/2019 8:48 AM Main Bootstrapping Zazzles
     11/25/2019 8:48 AM Controller Initialize
     11/25/2019 8:48 AM Controller Start
    
     11/25/2019 8:48 AM Service Starting service
     11/25/2019 8:48 AM Log Unhandled exception caught
     11/25/2019 8:48 AM Log     Terminating: True
     11/25/2019 8:48 AM Log     Hash code: 63835064
     11/25/2019 9:14 AM Main Overriding exception handling
     11/25/2019 9:14 AM Main Bootstrapping Zazzles
     11/25/2019 9:14 AM Controller Initialize
     11/25/2019 9:14 AM Controller Start
    
     11/25/2019 9:14 AM Service Starting service
     11/25/2019 9:14 AM Log Unhandled exception caught
     11/25/2019 9:14 AM Log     Terminating: True
     11/25/2019 9:14 AM Log     Hash code: 63835064
    

  • Moderator

    @UWPVIOLATOR My colleague and I have a PS script that at least checks if the service is running. It exports the results into .csv file. It can at least give you an idea of how many and which ones need fixed. (I sanitized this a bit, so put in your own stuff where needed)

    ForEach ($Computer in (Get-ADComputer -Filter * -SearchBase "OU=XXXXXXXXXXX,DC=MYDOMAIN,DC=COM")) {
    $ComputerName = $Computer.Name
    If (Test-Connection $ComputerName -Count 1 -Quiet) {
        $FogService = Get-Service -Name FogService -ComputerName $ComputerName -ErrorAction SilentlyContinue
            If ($FogService) { Write-Output "FOG is running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append}
            Else {Write-Output "FOG is not running on $ComputerName" | Out-File C:\Scripts\FOG.csv -Append }}
    Else {Write-Output "$ComputerName is Offline" | Out-File C:\Scripts\FOG.csv -Append}
    }
    

    From there, I am pretty sure you can just add affected PC’s to a group in Active Directory and map a GPO to run the following batch script (Note I sanitized a bit, so insert your own stuff where needed):

    msiexec /q /x "PATH TO FOG CLIENT MSI"
    msiexec /i "PATH TO FOG CLIENT MSI" /quiet USETRAY="0" HTTPS="0" WEBADDRESS="FOGSERVERIP" WEBROOT="/fog" ROOTLOG="1"
    
    net start FOGService
    


  • @Sebastian-Roth I have no way of knowing any of that hence the powershell script. What I want is to get a script that does all that FOG users need. Check to see if service is installed, if not Install. Check to see if FOG is broken, I currently look at the FOG.log date. If the date is over 14 days old then its broken, uninstall reinstall. Now I want to read the FOG.log file and key in on something to tell me its broke “Unhandled exception caught” or “Log Hash code” seem like good options. If we get this script to just record info then I can start narrowing down the info your are asking for. We usually dont deploy many snapins post imaging.

    My skills in powershell are not amazing so was thinking of colaborating with the FOG community and r/Powershell to get us a good script that others can deploy to their networks to maintain FOG. I plan to add this script to a daily maintence script.


  • Developer

    @UWPVIOLATOR said in FOG Clients Stop Working:

    11/20/2019 7:44 PM Service Starting service
    11/20/2019 7:44 PM Log Unhandled exception caught
    11/20/2019 7:44 PM Log Terminating: True
    11/20/2019 7:44 PM Log Hash code: 63835064

    I don’t think we’ve ever seen this before. Unfortunately the fog-client code does only print out the hash but no real error message and I can’t seem to find a way to translate the hash to a readable hint on what’s going wrong.

    Let’s start by asking a few questions:

    • How many clients do have the error?
    • When did it start first?
    • Did they all start with that issue on the same day or same week? (windows update?)
    • Which version of Windows (exact build version)?
    • Can you please grab a full fog.log from a client so we see what happened last before the error arises?
    • Is the issue reproducible - meaning, can you reinstall the fog-client and have it run into the same error within a few hours/days?

Log in to reply
 

355
Online

6.4k
Users

13.8k
Topics

130.3k
Posts