s3 compatible storage failed with v4, but it works with v3

[Showfom]

👉 Run our Container based provisioning and document the settings and context that trigger the alleged bug.

*️⃣ Make sure to test the bug in the Docker infra, let us know whatever the bug happens (or not) there.

▶ Reproduction steps

1. Settings > External storage
2. Set same configuration like v3 with storage type s3 compatible
3. Failed

😢 Unexpected result

It shows Something went wrong • Incident ID:61af7316974b4

But same configuration works with V3

📃 Error log message

 

[Rodolfo]

You need to debug the error, here's how: 👉 https://github.com/chevereto/docker/blob/4.0/docs/COMPOSE.md#logs

 

[Showfom]

I install from source, not docker.

 

[Rodolfo]

I install from source, not docker.

We explicit ask to use Docker when reporting bugs as it is easier to work with, specially for the user. Now instead of simply running a command you have to investigate your server logging.

👉 https://v3-docs.chevereto.com/manual/troubleshooting/debug.html#accessing-logs

👍 Please don't ignore the instructions. Is for your own time sake.

 

[Showfom]

Yes I checked, there's no error log

But the json returns 500

 

[Rodolfo]

There's a log, is just that you aren't looking at the right place. You need to check the error log for the alleged incident ID.

The location of the error log is syslog (default). You need to check depending on your server setup.

 

[Showfom]

root@chevereto /var/log # cat syslog | grep 61b23

There's no log from syslog file.

Did you try the s3 compatible storage on latest v4 release?

 

[Rodolfo]

Syslog is by default, it doesn't means that it will log there. Please check your server config.

Review this document: https://v3-docs.chevereto.com/manual/troubleshooting/debug.html#accessing-logs

 

[Showfom]

I configure Apache 2 and there's no content on the error log file

-rw-r--r-- 1 root root     0 Dec  7 12:51 error.log

 

[Showfom]

I also set CHEVERETO_DEBUG_LEVEL=3

 

[Rodolfo]

😞 I'm sorry, but you aren't following the debug guidelines. We requests bugs to be replicated in our Docker infra precisely to avoid this kind of situations. If you are running this on a server configured in your behalf, you are in charge of the entire provisioning. Including debug and error logging, unless you feel comfortable with that responsibility I don't recommend debugging elsewhere Docker.

I will schedule a check (again) for the storage providers, if I'm lucky I will get this bug. 😘

 

[Rodolfo]

👉 I found some minor errors which I've already fixed and pending release. Try again with V4.0.0.beta.4 when it gets out.