I’m looking for a bit of advice on getting unstuck with a local install using the helm charts + minikube.
I’ve gotten the whole cluster up and running on minikube (on an m2 mbp), the cluster health seems to be fine, and i can log in to the front end and create & save workflows.
However, the crawls never start, and just sit waiting to start. I assume that some crawlers are supposed to spawn and pick the jobs up, but i’m not certain where to start looking to figure out what’s stuck.
I’m looking for recommendations on logs to poke through, things to check/touch, and any other general advice while i halfheartedly poke through kubernetes documentation
I think it’s related to v1.16.2. I experienced the same issue and downgraded to v1.16.0. I was in a hurry to run some crawls and didn’t have time to debug it.
I will try again on a disposable VM.
$ sudo kubectl get pods -n crawlers
No resources found in crawlers namespace.
$ sudo kubectl get cjs -n crawlers
NAME STATE PAGES DONE PAGES FOUND SIZE TIME STARTED TIME FINISHED STOPPING FILES ADDED SCALE
crawljob-manual-20250602070102-3a6f719f-9a7 starting 0 0 6m35s false 0 1
Hey, i was having the same problem as @knowtheory although i’m using docker desktop instead of minikube. But as of today, instead of the crawl starting up but not doing anything i simply get the error ‘Sorry, couldn’t run crawl at this time.’
kubectl get pods -n crawlers
No resources found in crawlers namespace.
kubectl get cjs -n crawlers
NAME STATE PAGES DONE PAGES FOUND SIZE TIME STARTED TIME FINISHED STOPPING FILES ADDED SCALE
crawljob-manual-20250602123743-2603af6f-a95 starting 0 0 43h false 0 1
i assume this is the crawl i did before the helm fix? the one that got stuck on starting.
kubectl logs --tail=20 svc/browsertrix-cloud-backend -c op
We just released 1.17.0, please try this version to see if it works now. It sounds like a different issue, though. The finalize returning 400 seems like something got into a bad state. Try with a fresh install.