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.

Sign up for GitHub

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

Jump to bottom

Parseable fails to run with ceph s3 instances #700

Open
mahdiG opened this issue Mar 12, 2024 · 2 comments
Open

Parseable fails to run with ceph s3 instances #700

mahdiG opened this issue Mar 12, 2024 · 2 comments
Labels
triage

Comments

@mahdiG
Copy link

mahdiG commented Mar 12, 2024

Hi. Parseable works fine with Minio s3 but I tried to run parseable docker with two different Ceph s3 instances but it gives error:

Error: Unhandled Error: response error "<html>
<head><title>400 Bad Request</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx</center>
</body>
</html>
", after 0 retries: HTTP status client error (400 Bad Request) for url (https://s3.ir-thr-at1.arvanstorage.ir/parseable/.parseable.json)

the s3 works fine when used with s3cmd, mc, filestash, golang and python. I'm able to get, put, make bucket etc.

My env file looks like this:

P_STAGING_DIR=/staging
P_ADDR=0.0.0.0:8000
P_USERNAME=myuser
P_PASSWORD=mypass
P_S3_URL=https://s3.ir-thr-at1.arvanstorage.ir/
P_S3_BUCKET=parseable
P_S3_ACCESS_KEY=47xxxxxxa2
P_S3_SECRET_KEY=cdbxxxxxx5c
P_S3_REGION=default

Run command:
docker run -p 8000:8000 --env-file parseable-env -v /parseable/staging:/staging parseable/parseable:v0.8.1 parseable s3-store

Bucket is empty so that isn't the problem. I tried making the bucket public but it didn't make a difference
@nitisht
Copy link
Member

nitisht commented Mar 12, 2024

Thanks for reporting @mahdiG we'll take a look at this and get back.

@nitisht nitisht added the triage label Mar 12, 2024
@vrelk-net
Copy link

I'm having the same issue with MinIO. The error shows up in the Nginx access log instead of error, which makes me think the error is from MinIO, not Nginx.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mahdiG @nitisht @Eshanatnight @vrelk-net