-
Notifications
You must be signed in to change notification settings - Fork 386
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
envtool
panics on timeout
#2486
Comments
I revisioned the problem and it seems that the issue appeared not because of mongo, but rather because of tigris setup, which caused panic here: FerretDB/cmd/envtool/envtool.go Line 183 in 1479b0c
Mongo containers do provide their logs once I comment out the tigris setup:
Tigris itself fails of some illegal instructions I'm not sure about, but I assume it may be because my cpu does not support AVX:
Full env-up logs with disabled tigris setup: Full task env-up logs``` yaroslav@helen-N53Jg:~/go/src/FerretDB$ sudo "PATH=$PATH" bin/task env-up task: [env-up-detach] docker version task: [gen-version] go generate -x ./build/version go run ./generate.go Client: Docker Engine - Community Version: 23.0.4 API version: 1.41 (downgraded from 1.42) Go version: go1.19.8 Git commit: f480fb1 Built: Fri Apr 14 10:32:03 2023 OS/Arch: linux/amd64 Context: defaultServer: package.txt: bin
|
Both |
envtool
fails if MongoDB can't be startedenvtool
panics on timeout
Sure! |
What should be done?
See #2451 (comment)
envtool
should not fail like that. It should provide a helpful error message.Where?
envtool.go
Definition of Done
On that system, the error message should be about timeout, and Docker Compose logs should be provided.
The text was updated successfully, but these errors were encountered: