Step-by-Step: Finding Your Redshift Log File

Netinho Da Costa
Netinho Da Costa
  • Updated



When you’re experiencing an issue with Redshift, sharing a log file can help us understand what may have caused the problem, so we can get you back up and running smoothly. Below, we’ll guide you through finding and sharing the latest log file on Windows, macOS, and Linux.

 

You can find the location of the Redshift log files via redshift Renderview panels inside your 3D application. Here are a few examples:

Example: In Cinema 4D

Cinema_4D_m27u4tlFRe.gif 
Example in Maya:
Maya_log_files.gif

Example in Houdini:
Redshift_Houdini_log_folder.gif



Alternatively you can also locate the Redshift log file manually.

 

For Windows Users

1) Locate the Log Folder:

  • Option 1: Navigate Manually
    • Open File Explorer.
    • Go to the C: drive.
    • Open the ProgramData folder.
      • Note: If you don't see the ProgramData folder, it might be hidden.
        To display hidden folders:
        1. Click on the View tab in File Explorer.
        2. Check the box next to "Hidden items" in the Show/hide section.
    • Inside ProgramData, open the Redshift folder.
    • Open the Log folder.
  • Option 2: Use the Address Bar
    • Click on the address bar at the top of File Explorer.
    • Paste the following path and press Enter:

      C:\ProgramData\Redshift\Log

2) Find the Latest Log File:

  • Open the folder named Log.Latest.0.
  • Look for a file named redshift_log.html.
    • If there are multiple log files, select the most recent one based on the date modified.

3) Attach and Send to support:

  • Attach the redshift_log.html or a compressed redshift_log.zip file to your support ticket or email.

    You can share your log file with support via:
    https://support.maxon.net/hc/en-us/requests/new
    Make sure to get a log file right after an error or crash happens. Also make sure to clearly communicate what steps we must take in order to be able to replicate your error.

 

For macOS Users

1) Navigate to the Log Folder:

  • Option 1: Using Finder's Go Menu
    • Open Finder.
    • Click on "Go" in the menu bar at the top of the screen.
    • Select "Go to Folder..." or press Shift + Command + G.
    • Enter the following path and click Go:

      ~/Library/Logs/Redshift

    • Note: If you can't find the Library folder, it might be hidden. To access it:
      • Click on "Go" in the menu bar.
      • Hold down the Option key to reveal "Library" in the dropdown menu, then click on it.
      • Navigate to the Logs folder, then open the Redshift folder.

2) Identify the Latest Log File:

  • Inside the Redshift folder, locate the file named redshift_log.html.
    • If there are multiple log files, choose the most recent one based on the date modified.

3) Attach and Send to support:

  • Attach the redshift_log.html or a compressed redshift_log.html.zip file to your support ticket or email.

    You can share your log file with support via:
    https://support.maxon.net/hc/en-us/requests/new
    Make sure to get a log file right after an error or crash happens. Also make sure to clearly communicate what steps we must take in order to be able to replicate your error.

 

For Linux Users


1) Navigate to the Log Directory:

  • Open your Terminal application.
    Enter the following command to navigate to the Redshift log directory:

    cd ~/.redshift/Log

2) Find the Latest Log File:

  • Navigate to the latest log directory:

    cd Log.Latest.0

  • Locate the file named redshift_log.html.
    • Use the command ls -lt to list files sorted by date, with the most recent at the top.

 

3) Attach and Send to support:

  • Attach the redshift_log.html or a compressed redshift_log.html.zip file to your support ticket or email.

    You can share your log file with support via:
    https://support.maxon.net/hc/en-us/requests/new
    Make sure to get a log file right after an error or crash happens. Also make sure to clearly communicate what steps we must take in order to be able to replicate your error.

 

Was this article helpful?

/

Comments

0 comments

Article is closed for comments.