GreptimeDB Crash Report

[zengfanlin]

What type of bug is this?

Crash

What subsystems are affected?

Standalone mode

Minimal reproduce step

I send a export command line .\greptime cli export --addr localhost:4000 --output-dir /tmp/backup/timerange --start-time "2024-01-01 00:00:00" --end-time "2024-01-31 23:59:59"

What did you expect to see?

export data

What did you see instead?

crash

report-e1ce3ef0-c21f-4ba9-ae01-ef93cb3455dd.txt

What operating system did you use?

Windows 10 x64

What version of GreptimeDB did you use?

0.11.2

Relevant log output and stack trace

[yihong0618]

when you use windows -output-dir /tmp/backup/timerange the dir name maybe need to follow windows rules

[evenyag]

when you use windows -output-dir /tmp/backup/timerange the dir name maybe need to follow windows rules

Yes, you may need to check if the database can write to this path.

Could you please check the logs of the server? Does it report any errors?

[discord9]

I test it on windows and it seems if the provided http addr can't be connected then will report this error, maybe check again if the db processs is actually hosting a http server at localhost:4000, meanwhile we can add a more friendly message when failed to connect