Details
-
Bug
-
Status: Open
-
Medium
-
Resolution: Unresolved
-
2.26.0
-
None
-
None
-
Yes
-
Yes
-
Yes
Description
We are running a dockerized PMM server with a couple of AWS RDS instances added a couple of years ago while still on 1.x. (currently on 2.26.0).
Now I'm trying to add a new RDS instance with IAM key/secret, but when I click 'Discover' the route returns a 502 Bad Gateway error.
I checked the nginx logs and it does not show anything, but I found this in the pmm-managed.log when the request happens:
INFO[2022-03-24T19:01:09.768+00:00] Round-trip time: 407.239µs. Estimated clock drift: 53.021µs. agent_id=pmm-server request=b85ba07a-aba4-11ec-92d1-0242ac110002 INFO[2022-03-24T19:01:10.444+00:00] Starting RPC /management.RDS/DiscoverRDS ... request=c4af254b-aba4-11ec-92d1-0242ac110002 panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x10aa472] goroutine 867 [running]: github.com/percona/pmm-managed/services/management.(*RDSService).DiscoverRDS.func1() /home/builder/rpm/BUILD/pmm-managed-6914083707b5478605e7bc816de8fc68b5f511f6/src/github.com/percona/pmm-managed/services/management/rds.go:186 +0x292 golang.org/x/sync/errgroup.(*Group).Go.func1() /home/builder/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:57 +0x67 created by golang.org/x/sync/errgroup.(*Group).Go /home/builder/go/pkg/mod/golang.org/x/[email protected]/errgroup/errgroup.go:54 +0x92 time="2022-03-24T19:01:10Z" level=info msg="Environment variable \"PERCONA_PLATFORM_API_TIMEOUT\" is not set, using \"30s\" as a default timeout for platform API." request="saasreq init"
Please let me know if I can provide you with more useful information.
