Internal: Object store client not present, cannot stream logs from store when clicking Show more...
When Windmill truncates the logs of a particular run and shows the "Show more..." button, clicking it causes the error from the title.
We do have "Instance object storage" configured in the Instance settings, and clicking both "Test from a server" and "Test from a worker" results in a success. Any ideas?
20 Replies
Not sure no, it works fine on prod on latest
We're on the Windmill Pro plan and not EE if that makes any difference
I'm not sure if the S3 logging is supposed to be working for us
yeah I think it doesn't
will improve the error message
I guess the real question is whether Windmill would fall back to trying to read the logs from the filesystem or it'd keep failing unless we disable the instance object storage
It will fallback to logs from filesystem
actually, not fully certain
@rubenf btw, I checked on my community edition instance at home and the error I get is different, so my assumption is that windmill is trying to use S3 for logs even though we're not supposed to have it included in the Pro plan (or so you've told me), so it looks like there is a bug here, as I'd expect it to fall back to logs from filesystem, but the error indicates it's trying S3 only
I set up a shared mount for the server and workers mounted on /tmp/windmill/logs, disabled the instance object store, yet I still get Internal: Object store client not present, cannot stream logs from store
Windmill appears to be writing stuff to the shared volume already, I'm not sure why it's trying to read from an object store
I will investigate
I can confirm the log I'm trying to read is located in /tmp/windmill/logs/ under the job id, so it's just trying to read from the wrong location it seems, writing is fine
👍
@rubenf sorry for the noise, just wanted to check if this issue is being worked on/planned. We currently have to manually SSH and piece together the logs each time we need them, which is very cumbersome and makes debugging very painful
I'm on it today
I believe the shared mount must not be working properly @invakid404
the code is very clear, it's checking first if the file exist on the expected location
this is weird, we have a shared mount on both the workers and the server
I'm sure it works on the workers' end, as logs are indeed being written to said shared mount
and I can see that it's mounted on the server as well: https://img.qilin-qilin.ts.net/2024-11-25_10-04-51_BKyZj.webp
on very latest, the error message will indicates what file is missing
I'll update once the image is out and I'll let you know
@rubenf
there's logs twice in the path for whatever reason
can you show me the request being done please
it's hitting
/api/w/mandel-staging/jobs_u/get_log_file/logs/019362d9-bf87-ca69-d0a8-58e7d0535117/1732530257874_9276.txt
the log_file_index
column in postgres appears to contain the logs/
prefix as well, so i'd assume it's coming from thereWill investigate, thanks
Ok found the issue and fixed on very latest
thanks! I'll update once the image is out and I'll let you know if it's fixed on our end