Cannot Retrieve File Metadata for Spoolman about moonraker HOT 10 CLOSED

This appears to be an issue with the frontend. Based on the error in your issue, the frontend is requesting metadata for a file named filename.gcode. I would presume that this is not the actual file name, and instead is a placeholder.

from moonraker.

I stuck in "filename" as a placeholder (it was long). The log file has the actual file name in it, sorry for causing the confusion.

from moonraker.

Please attach the full log.

from moonraker.

This is a known issue, but I don't think it's being actively tracked in the fluidd repo yet. So far I haven't been able to reproduce this, the only times I saw this myself was when a file was deleted or moved and the entry in the reprint tab on the dashboard hadn't been updated yet (but then starting the print would fail too).

@Arksine As I think this isn't a moonraker issue, feel free to close this - I'll open an issue in the fluidd repo then.

from moonraker.

OK, I'll close this and open a bug report on Fluidd. I kind of knew whichever of Klipper/Moonraker/Fluidd I tried to identify as the culprit, I'd pick wrong.

from moonraker.

Ok. FWIW, I don't mind looking at the log to see if it provides some context which can help narrow down the issue.
If that isn't fruitful you could try to reproduce with verbose logging enabled, as we could see the exact sequence of events that led to the metadata error.

from moonraker.

Conveniently, one of the printers immediately threw the error this morning. I've also mentioned on a similar issue over at the Fluidd project.
moonraker.log

from moonraker.

I see the error, unfortunately without verbose logging enabled there isn't much context. I presume that it occurred after starting a print? There is an upload of the same file about 13 seconds after the metadata error, was the intent here to overwrite the file to force metadata extraction?

from moonraker.

FWIW, you can enable verbose logging by adding the following to /home/pi/printer_data/systemd/moonraker.env:

MOONRAKER_VERBOSE_LOGGING="y"

That said, it will create large log files, so you will want to disable it after reproducing the error.

from moonraker.

Tagging fluidd-core/fluidd#1408, the issue is now tracked there.

from moonraker.