Aller au contenu principal
This page is not translated yet. Français is switched on so the navigation and URLs can be tested; the text below is the English original. Use the language selector in the header to switch back, or see the documentation home.

Read job logs

how-to · Reviewed 2026-07-30 GA

There are three log sources on a Rescale job. This page maps a diagnostic question to the log that answers it.

Pick the right log​

Your questionOpen
Is the platform making progress?Job Logs on the Status tab
What did my solver print?process_output.log on the Results page
Why did it converge that way?The solver's own log on the Results page
Who did what in the workspace?Audit logs in the admin portal

Job Logs: what the platform did​

The Job Logs section on the Status tab captures platform-level events: validation passing, the cluster starting, individual runs launching and completing, and any stop initiated by you or the system.

For a DOE or Optimization job, each run's start and finish appears here. This is the right place to confirm a multi-run job is progressing: not to debug the physics.

Job Logs will not contain solver output. If you're looking for residuals or a solver error message, you want process_output.log.

process_output.log: what your software printed​

Every job produces process_output.log. It captures stdout from your software: license checkout messages, modeling parameters, solver progress, and error text.

To open it:

  1. Go to the job's Results page.
  2. Search the file list for log or process.
  3. Click the screen icon in the Actions column to view it inline.

Download it instead if it's too large to open in the browser.

The end of the file contains the process exit code. See exit codes for what each one means, and for why exit code 0 doesn't prove the run was good.

Solver logs. The detail process_output.log doesn't have​

Most solvers write their own logs in addition to stdout, and those usually contain far more detail. On the Results page, look for files ending in .log, .out, .live, or .dat.

  • LS-DYNA writes ls-dyna.log with a run summary.
  • ANSYS Fluent writes a transcript plus case-specific logs.

Keeping ANSYS client-side logs​

ANSYS writes client-side logs to ~/.ansys/ during the run. Rescale only copies files from ~/work/ and below back to your Results page, so those logs are destroyed with the cluster unless you move them first.

Add this as the last line of your launch command:

cp -r ~/.ansys ~/work/shared/dotansys

For more, see How to Find Ansys Debug Logs for Troubleshooting.

This applies to any tool, not just ANSYS

Any solver that writes outside the job directory loses those files at cluster teardown. If you need them, copy them into ~/work/ before your command exits.

Audit and transfer logs: workspace activity​

Two admin-level log streams sit outside the job itself, in the Security tab of the organization and workspace admin portals:

  • Event audit logs — user invites, logins, promotions, SSO failures, job deletion and sharing, admin shutdowns, budget changes, and project membership changes.
  • Transfer logs — file uploads and downloads, with filename, size, IP, user email, and client.

Access is limited to Org Admins and Workspace Admins, on editions that include audit logs. There is no API for exporting these today: use the UI.

Troubleshooting​

The job page itself won't load. See "We Could Not Load the Job That You Requested".

I need Rescale Transfer Manager logs. See How to Access and Save RTM Logs.

The log is empty. If the job failed before the Running Job stage, your software never started and there's no stdout to capture. Check the lifecycle for which stage failed.