Skip to content
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

Minio errors when following quickstart for clickhouse #1727

Open
zachblume opened this issue May 16, 2024 · 1 comment
Open

Minio errors when following quickstart for clickhouse #1727

zachblume opened this issue May 16, 2024 · 1 comment
Assignees

Comments

@zachblume
Copy link
Contributor

zachblume commented May 16, 2024

  • Followed https://docs.peerdb.io/quickstart/quickstart
  • Installed on Ubuntu on hetzner with a local network and firewall rules allowing local network open port on 9000 for clickhouse
  • Added valid remote postgres peer, worked
  • Created clickhouse peer via web interface -- got errors. Tried via sql via the SQL get started guide -- same errors
root@peerdb:~/peerdb# psql "port=9900 host=localhost password=peerdb"
psql (16.2 (Ubuntu 16.2-1ubuntu4), server 14)
Type "help" for help.

root=> CREATE PEER local_clickhouse FROM CLICKHOUSE
WITH
(
    host='10.0.0.2',
    port=9000,
    user='default',
    password='...',
    database='default',
    disable_tls = true
);
ERROR:  User provided error: ErrorInfo {
  severity: "ERROR",
  code: "internal_error",
  message: '[peer]: invalid configuration: failed to validate peer local_clickhouse:
failed to validate S3 bucket: failed to write to bucket: operation error S3: PutObject,
exceeded maximum number of attempts, 3, https response error StatusCode: 0, RequestID: ,
HostID: , request send failed, Put "http://host.docker.internal:9001/peerdbbucket/peerdb_check9550a006-9868-451c-ae8a-ab63c31e0b0d?x-id=PutObject": dial tcp 127.0.0.1:9001: connect: connection refused',
  detail: None,
  hint: None,
  position: None,
  internal_position: None,
  internal_query: None,
  where_context: None,
  file_name: None,
  line: None,
  routine: None,
}
root=> 

Note: I had a different error before, referring to host.docker.internal as well. I added a /etc/hosts for host.docker.internal to 127.0.0.1 on the machine as well and now got the above error.

@mithleshjs
Copy link

Replace host.docker.internal with Public or Private IP of the server in http://host.docker.internal:9001

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants