Pangea File Intel initial database sync takes 10 to 20 hours - do not reinstall prematurely

TL;DR

Only if the maintenance jobs are missing entirely should you uninstall and reinstall.

Steps

1. Per Pangea docs: File Intel first sync takes 10-20 hours - check the cronjobs before assuming failure.

When to use

You are seeing this: Per Pangea docs: File Intel first sync takes 10-20 hours - check the cronjobs before assuming failure. Use this skill when you run into "Pangea File Intel initial database sync takes 10 to 20 hours - do not reinstall prematurely".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Problem: The File Intel service seems stuck syncing. This is expected: the initial database sync takes 10-20 hours. Verify progress with kubectl get cronjobs -n [namespace] and kubectl get pods -n [namespace]. Only if the maintenance jobs are missing entirely should you uninstall and reinstall.

Verified resolution: Per Pangea docs: File Intel first sync takes 10-20 hours - check the cronjobs before assuming failure.

Source URL: https://pangea.cloud/docs/deployment-models/private-cloud/troubleshooting