{"record":{"id":"59fbcb9b1437bc42","repo":"remotion-dev/remotion","slug":"failed-to-upgrade-remotion-run-with-log-info-in","errorCode":null,"errorMessage":"Failed to upgrade Remotion, run with --log=info info to see logs","messagePattern":"Failed to upgrade Remotion, run with --log=info info to see logs","errorType":"exception","errorClass":"Error","httpStatus":null,"severity":"error","filePath":"packages/cli/src/upgrade.ts","lineNumber":295,"sourceCode":"\tconst task = spawn(manager, command, {\n\t\tenv: {\n\t\t\t...process.env,\n\t\t\tADBLOCK: '1',\n\t\t\tDISABLE_OPENCOLLECTIVE: '1',\n\t\t},\n\t\tstdio: RenderInternals.isEqualOrBelowLogLevel(logLevel, 'info')\n\t\t\t? 'inherit'\n\t\t\t: 'ignore',\n\t});\n\n\tawait new Promise<void>((resolve) => {\n\t\ttask.on('close', (code) => {\n\t\t\tif (code === 0) {\n\t\t\t\tresolve();\n\t\t\t} else if (RenderInternals.isEqualOrBelowLogLevel(logLevel, 'info')) {\n\t\t\t\tthrow new Error('Failed to upgrade Remotion, see logs above');\n\t\t\t} else {\n\t\t\t\tthrow new Error(\n\t\t\t\t\t'Failed to upgrade Remotion, run with --log=info info to see logs',\n\t\t\t\t);\n\t\t\t}\n\t\t});\n\t});\n};\n","sourceCodeStart":277,"sourceCodeEnd":302,"githubUrl":"https://github.com/remotion-dev/remotion/blob/78fe4bb3fdb5a2cd68724393d63cb223db333fa7/packages/cli/src/upgrade.ts#L277-L302","documentation":"Thrown by the upgrade command when the spawned package manager exits non-zero AND the log level is above 'info' (e.g. warn/error), so stdio was 'ignore' and the installer's output was suppressed. Because no logs were shown, the message tells you to re-run with --log=info to see them.","triggerScenarios":"Same underlying failure as error 116 (installer non-zero exit) but the command was invoked with a quiet log level such as `--log=warn` or `--log=error`, hiding the installer output.","commonSituations":"CI pipelines or scripts that set --log=warn to reduce noise, then cannot diagnose an upgrade failure; default-log users who muted output.","solutions":["Re-run with verbose logs: `npx remotion upgrade --log=info`.","Once the installer error is visible, follow the same steps as for error 116.","If running in CI, temporarily set --log=info to capture the cause."],"exampleFix":"// before\n$ npx remotion upgrade --log=warn\nFailed to upgrade Remotion, run with --log=info info to see logs\n// after\n$ npx remotion upgrade --log=info","handlingStrategy":"try-catch","validationCode":"const shouldRunVerbose = (logLevel: string) => {\n  if (!['info', 'verbose'].includes(logLevel)) {\n    throw new Error('Run `remotion upgrade` with --log=info to capture installer output on failure');\n  }\n};\n\nshouldRunVerbose(currentLogLevel);","typeGuard":null,"tryCatchPattern":"try {\n  await upgradeCli({logLevel: 'info'});\n} catch (err) {\n  if (err instanceof Error && err.message.includes('run with --log=info')) {\n    // retry with verbose logs to capture root cause\n    await upgradeCli({logLevel: 'info'});\n  }\n  throw err;\n}","preventionTips":["Always run `remotion upgrade` with at least --log=info in CI to capture failures.","Pipe CI command output to a log artifact for post-mortem."],"tags":["cli","upgrade","logging","package-manager"],"backgroundTag":null,"analyzedSha":"78fe4bb3fdb5a2cd68724393d63cb223db333fa7","analyzedAt":"2026-08-12T17:18:50.444Z","schemaVersion":2},"datasetVersion":"2026-08-12T23:17:12.415Z"}