• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    FOG Clients Stop Working

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    5
    281
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • UWPVIOLATORU
      UWPVIOLATOR
      last edited by

      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
      
      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        @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?

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        UWPVIOLATORU 1 Reply Last reply Reply Quote 0
        • UWPVIOLATORU
          UWPVIOLATOR @Sebastian Roth
          last edited by

          @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.

          fry_pF 1 Reply Last reply Reply Quote 0
          • fry_pF
            fry_p Moderator @UWPVIOLATOR
            last edited by

            @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
            

            Like open source community computing? Why not do it for a good cause?
            Use your computer/server for humanitarian projects when it is idle!
            https://join.worldcommunitygrid.org?recruiterId=1026912

            1 Reply Last reply Reply Quote 1
            • S
              Sebastian Roth Moderator
              last edited by

              @UWPVIOLATOR Did you get to test the script?

              Meanwhile we have released a new version of the fog-client which should print out a text instead of the hash when it catches the unhandled exception.

              Either you can update to the latest dev-branch version to get the new fog-client or you can switch over manually: Download SmartInstaller and MSI and put those in /var/www/html/fog/client/ (rename the old binaries to be sure you have a backup copy in case). Then edit /var/www/html/fog/lib/fog/system.class.php and change the line where you see the client version from 0.11.16 to 0.11.17. Be aware that all your hosts with running fog-client will download the SmartInstaller from your FOG server and attempt to auto update!

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              1 Reply Last reply Reply Quote 0
              • 1 / 1
              • First post
                Last post

              166

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project