This message was deleted.
# troubleshooting
s
This message was deleted.
b
Mind sharing a screen recording
b
Shared
b
My
query-controller
task - report works fine
The
query_worker
has 404 as well
Has it always worked for you ?
b
No
It’s from first day
I am getting 494
404
While checking success report
Runner status code is waiting always
b
All of the tasks reports are failing for you ?
b
Yes
b
How about MSQE?
I am using v25
query-controller
report works fine
b
Mine is v24.02
In common runtime.properties
Am I supposed to put that server host ip or master
p
You may want to check out https://druid.apache.org/docs/latest/ingestion/tasks.html#task-logs – 404 would indicate that the API endpoint that’s being asked to provide you with the logs is unable to find them. That doc may give you an indication of how to find the root cause.
b
I am using local storage to store logs
Is that the problem
p
Quite possibly – best practice would be to set up long term storage for log files.
OHHH sorry I am talking about logs and not reports…> 😄
I will go back to my dark cave 😄
b
People will correct me but I think the log files are more important
Can you access the log files ?
b
I
No
b
Can you run a MSQE job on wikipedia ?
is this a production system for you ?
If not , upgrade to v25 and run /bin/start-druid
b
It’s production system
v
does the task otherwise work? Like does it ingest the data?
the reports are stored in deep storage (like S3 if you are using AWS). Is something deleting these files there? If you tell me what kind of deep storage you have I can tell you where to look for the report files