Manual log collection
  • 19 Mar 2025
  • 1 Minute to read
  • Contributors

    Manual log collection


      Article summary

      How to manually collect Logs in case the automatic collection encounters an issue

      In case the automatic log collection tool fails, you can manually collect and send logs using the following dedicated scripts for each operating system:



      Windows

      1. Right-click Windows PowerShell and click Run as administrator.
      2. Run:
        Invoke-Expression ((New-Object System.Net.WebClient).DownloadString('https://supportbucketshare.s3.us-east-1.amazonaws.com/Custom+Scripts/Log+Collector/Log+Collector+PS.ps1'))
      3. When prompted, enter Y. If support requests extended logs, enter Y again.
        Note - Enable extended logs only if instructed by support, as they are significantly larger.
      4. Once the script completes, an Explorer window opens with the log files.
      5. Submit the required files to your support ticket.
      6. Once the support confirms receipt, manually delete the Harmony SASE Logfiledirectory from the Downloads folder.

      MacOS

      Download and extract this script file:

      Open the Terminal application (search "Terminal" in the Launchpad).360007501440ScreenShot2019-12-29at164804.png

      Copy and execute the following command. Make sure you're aware of the path where the script file was extracted: 

      sudo bash /Users/*/Downloads/Customer_logs*.sh

      This will automatically send the log files to our Support Team. Please ensure to provide your email, workspace name, and ticket number (if applicable).

      How to manually locate log files in MacOS

      Should you wish to review the logs independently, they can be found at the following locations:
      ##Connection Logs
      /var/log/Perimeter81 
      ##Application Logs
      /tmp/Perimeter81.log

      Linux

      1. Run the following command in Terminal:
        Shell
        /opt/Perimeter81/perimeter81 collect-logs

         2. Send the log file to sase-support@checkpoint.com


      Was this article helpful?