Our personal Browsertrix instance on Docker Desktop’s builtin Kubernetes on Windows sometimes only says:
15:34:30 Crawler Instance Crashed
15:34:30 Crawl failed, no pages crawled successfully
The standard log file is empty then.
How can we debug and avoid such errors on container level? (Sorry, still Kubernetes noob here, just followed your excellent guides for installation.)
This crawl initially ran fine, only the second and subsequent calls no longer run (after finetuning some parameters). Also other crawls still run just fine.
Regards,
Heinz