Collector panic
Für unser Daily gleich:
collector_1 | ERRO[2021-05-18T06:14:42Z]/go/src/api/collector.go:485 main.listMetsInBucketV2() failed to list objects for bucket dzeit, due to RequestError: send request failed
collector_1 | caused by: Get "https://dzeit.s3.fs.example.com/?list-type=2&max-keys=250&prefix=mets": dial tcp 172.18.0.3:443: connect: connection refused
redis | 1:M 18 May 2021 06:14:38.280 * monotonic clock: POSIX clock_gettime
redis | 1:M 18 May 2021 06:14:38.281 * Running mode=standalone, port=6379.
redis | 1:M 18 May 2021 06:14:38.281 # Server initialized
redis | 1:M 18 May 2021 06:14:38.281 * DB loaded from append only file: 0.000 seconds
redis | 1:M 18 May 2021 06:14:38.281 * Ready to accept connections
s3_1 | Endpoint: http://172.18.0.3 http://127.0.0.1
s3_1 |
s3_1 | Browser Access:
s3_1 | http://172.18.0.3 http://127.0.0.1
s3_1 |
s3_1 | Object API (Amazon S3 compatible):
s3_1 | Go: https://docs.min.io/docs/golang-client-quickstart-guide
s3_1 | Java: https://docs.min.io/docs/java-client-quickstart-guide
s3_1 | Python: https://docs.min.io/docs/python-client-quickstart-guide
s3_1 | JavaScript: https://docs.min.io/docs/javascript-client-quickstart-guide
s3_1 | .NET: https://docs.min.io/docs/dotnet-client-quickstart-guide
s3_1 | IAM initialization complete
collector_1 | panic: runtime error: invalid memory address or nil pointer dereference
collector_1 | [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x921a09]
collector_1 |
collector_1 | goroutine 1 [running]:
collector_1 | main.listMetsInBucketV2(0xc0002ba8f0, 0x5)
collector_1 | /go/src/api/collector.go:528 +0x6a9
collector_1 | main.main()
collector_1 | /go/src/api/collector.go:323 +0x413
indexer_collector_1 exited with code 2
Ich kann mir gerade noch keinen Reim drauf machen, können wir gleich drüber sprechen...