(SOLVED) Error getting data from moonraker

[dense plinth]

Since the last update i get this error on every machine start. https://termbin.com/5ytd <@&1304550334839918672>

[knotty mortar]

Check out this software prereq part https://www.armoredturtle.xyz/docs/afc-klipper-add-on/installation/getting-started.html#step-2-software-pre-configuration

[dense plinth]

this was not the solution

[dense plinth]

the 3 software prerequisites are up-to-date on both my printers.

[knotty mortar]

I meant this part, it was just added.

trusted_clients:
127.0.0.0/8

Also

[stray python]

Please run this debugging script when not printing and post the resulting link in chat.

[dense plinth]

https://termbin.com/jid4

I ran the debug script again

[dense plinth]

Are there any new findings?

[proud void]

Can you upload your Moonraker log as this might help us out as well

[proud void]

hmm, you log seems kinda small. Do you have a long thats bigger? Also if you restart your klipper service(or firmware restart) does the error go away?

[dense plinth]

Last week I pressed the button for "rollover logs" in mainsail. That should be the reason. A firmware restart solves this error message.

[proud void]

Ok, so I think its this issue we create a bug for already. I just need to find the correct way to fix this problem https://github.com/ArmoredTurtle/AFC-Klipper-Add-On/issues/452

[dense plinth]

sounds like the same issue

so it's a timing problem?

[proud void]

yeah something like that, moonraker is taking longer to load so AFC cannot communicate with moonraker when trying

so I am curious, what happens if you comment out all the update_manager lines and restart your printer. Does moonraker start faster and not cause the error?

[dense plinth]

i'll give it a try

I commented out all lines from the update_manager, restarted my printer and the error still occurs

[proud void]

Ok

Can you upload that full Moonraker log since you just restarted please

[proud void]

@dense plinth You mind trying this file out when you get a chance and upload it to your AFC-Klipper-Add-On/extras folder and reboot your printer. This change 🤞 might work

[dense plinth]

After reboot

after pressing restart

and a firmware restart everything is ok

[short bear]

this is normal as firmware restart didn't happen

[dense plinth]

but with whatever is changed in this file you get a "Timer too close" error

[proud void]

can you upload your klipper log from this?

All I added was a wait during klipper starting up, would not think that would cause a TTC...

hmm, yeah maybe not the best change. I forced a 30 second wait and got this, back to the drawing board

[short bear]

well thats a whole different thing

[proud void]

yeah I just make it that big since I made the change to wait up to 30s and was curious what would happen..

[proud void]

@dense plinth I think I may have fixed this a different way, whenever you get a chance can you replace these files in your AFC-Klipper-Add-On/extras folder and reboot your machine. I would like to know if these changes fix the race condition for you.

[dense plinth]

Ok I’ll give it a try

the error still exists

[proud void]

can you upload your AFC.log please

[dense plinth]

16:53:52 41.828 DEBUG: Connected to moonraker after 2 tries

[proud void]

Ah it connected, just need to fix that error

[dense plinth]

so at the end the error message just has to disappear automatically

[proud void]

Ok update this file and reboot again, it should not print that error this time

[dense plinth]

with that I have to do a firmware restart

[proud void]

this after rebooting your printer?

the change should of not caused that

[dense plinth]

I tested it on both my printers. This is from my V2.4 . My Trident boots normal but with the error message

My Trident has a Pi 4 and the 2.4 has a Pi 5

[proud void]

can you upload your AFC.log from your trident

[proud void]

ok I missed a print to not print for this, try this 🤞

[dense plinth]

now I have to perform a firmware restart on both printers

[proud void]

when updating files you normally have to do that, you should not have to if you just reboot your printer

[dense plinth]

no after a reboot I have to restart the klipper service and then a firmware restart

[proud void]

why do you have to restart the klipper service?

[dense plinth]

I thought you could tell me

[dense plinth]

this appears after a restart

then I press on the klipper restart Icon

[proud void]

I will need your klippy.log to help figure this one out

[proud void]

hmmm, interesting you are getting a TTC on startup for some reason. I think I need to update how I do the wait

[proud void]

Ok, did a wait a different way. Hope this solves it this time...

[dense plinth]

no error message and both printers are booting normal

looks like you found the solution

[proud void]

sweet!! So I am going to commit this to DEV and call this the fix

[dense plinth]

@proud void When will a new update with your fix be released?

[proud void]

So I have the fix into dev, currently not sure when it will be pushed to main. Maybe soon 😬

[dense plinth]

@proud void Are your changes part of the latest update? Because the bug is back.

[proud void]

No it's not, if you updated it reverted the files that you manually updated. The only thing that was updated were the config templates

[dense plinth]

Is a major update planned?

[proud void]

Not yet, it would be best for you to manually put the files back and just don't update AFC until an announcement in #afc-updates saying that this issue is fixed in main

[proud void]

@dense plinth This is now in main you should be good to update now, let me know if it still works for you and then we can call this solved

[dense plinth]

I updated it on my mashines. Everything is fine. No Moonraker error message.