Skip to main content
Start with:

​
Health checks

Every component serves GET /healthz on port 8080 as its readiness probe. A ready pod answers {"status":"ok"}. An unready pod answers 503 with status and the reason in error, and stays running rather than restarting.

​
Installation

​
A claim stays Pending

For the in-process claim: the EFS CSI driver is missing, its controller lacks AmazonEFSCSIDriverPolicy, or fileSystemId is wrong. For mnesia-fineparser-orchestrator-0: the cluster has no default StorageClass, or its driver is missing.

​
Pods are stuck in ContainerCreating

kubectl describe pod shows the cause.
  • EFS mounts time out: no mount target in the node’s Availability Zone, or TCP 2049 is blocked.
  • S3 mounts fail: wrong bucket or region, or the Mountpoint driver’s role cannot access the bucket. No signing credentials available means the role’s trust policy does not match the cluster’s OIDC provider.

​
Pods fail with exec format error

The pod is on an arm64 node. See Run on amd64.

​
Workers

​
No workers start

If the Deployment wants workers but they are Pending, the cluster has no room: check that your node autoscaler can add amd64 nodes matching worker.nodeSelector and worker.tolerations. With worker.prepull enabled, also check the pre-pull DaemonSet is running on the new nodes.

​
Workers exit at startup

The line billing refused this worker, exiting: gives the reason. billing: RegisterUsage failed, retrying is a transient error the worker retries.

​
Workers are unready

FineReader Engine refused the default profile. The worker’s log and /healthz give the reason. Fix worker.predefinedProfile or worker.userProfile, upgrade, and restart the workers.

​
Workers restart with exit code 2

A worker that fails five units in a row restarts. Check the failed jobs’ failure.message. If every document fails, look at the volumes or the profile.

​
Jobs

​
Upgrades