Shutdown of s3 cluster with invalid AWS credentials never succeeds
pashkinelfe opened this issue · comments
If I try to shutdown cluster with invalid aws credentials and some (little amount of) inserted data it comes into never-ending loop of starting-stopping bgworkers. Wrong AWS credentials don't prohibit cluster starting, but will prevent it from stopping later.
FATAL: could not put object to S3
2023-12-26 08:19:41.545 UTC [260830] DETAIL: return code = 0, http code = 403, response = <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>****************</AWSAccessKeyId><RequestId>*****************</RequestId><HostId>**********************************</HostId></Error>
2023-12-26 08:19:41.545 UTC [260857] LOG: orioledb s3 worker 9 started
2023-12-26 08:19:41.545 UTC [260857] DEBUG: S3 part put orioledb_data/1/1/16.0.0 orioledb_data/1/16-1
2023-12-26 08:19:41.545 UTC [260859] LOG: orioledb s3 worker 17 started
2023-12-26 08:19:41.545 UTC [260859] DEBUG: S3 dir put data/1/orioledb_data/ orioledb_data
2023-12-26 08:19:41.545 UTC [260861] LOG: orioledb s3 worker 11 started
2023-12-26 08:19:41.545 UTC [260861] DEBUG: S3 dir put data/1/pg_tblspc/ pg_tblspc
2023-12-26 08:19:41.546 UTC [2196] LOG: background worker "orioledb s3 worker" (PID 260830) exited with exit code 1
2023-12-26 08:19:41.546 UTC [2196] DEBUG: starting background worker process "orioledb s3 worker 15"
2023-12-26 08:19:41.547 UTC [260864] LOG: orioledb s3 worker 15 started
2023-12-26 08:19:41.547 UTC [260864] DEBUG: S3 dir put data/1/pg_multixact/members/ pg_multixact/members
2023-12-26 08:19:41.548 UTC [260783] FATAL: could not put object to S3
2023-12-26 08:19:41.548 UTC [260783] DETAIL: return code = 0, http code = 403, response = <?xml version="1.0" encoding="UTF-8"?>
Checked and found fixed at a1d7320