Mainsail - Klipper GitHub repo connection problem

Frontends
1

Basic Information:

Printer Model: Elegoo Neptune 3 Pro
MCU / Printerboard: BTT PAD7 (stm32f401xc), Version: v0.11.0-122-ge6ef48cd
Host / SBC: (aarch64, 64bit), Version: v0.12.0-302-g87ac69363
klippy.log

Describe your issue:

Since three weeks, Klipper behaves unpredictable. Some print work absolutely fine, and some prints my Klipper Mainsail just shuts down the whole printer during printing. sometimes 5min in sometimes 4h in… and it drives me nuts… after reboot and moving free the printer, everything connects as normal.

at the same time, my update manager tells me practically everthing GitHub related is “invalid” (see screenshots). I tried both soft and hard recovery. (results in screenshots). It’s unable to acces the Klipper Git repo, but if I go directly on GitHub, the Klipper repo has still the same link…? (same same for “Moonraker”, “sonar”, “timelaps”, “crowsnest”) so I’m very lost here right now…

SSH from [quote=“Sineos, post:7, topic:19529”] Update Manager shows suddenly almost everything "Invalid" - #7 by Sineos

Run following commands in a shell and copy and paste the output here, formatted as code:
[/quote]

gives me dangling commits (9pc), see below:

biqu@BTT-CB1:~$ cd ~/klipper
biqu@BTT-CB1:~/klipper$ git branch -vv
* master 87ac69363 [origin/master] fan: Wait full kick_start_time even if request is for ful                       l speed
biqu@BTT-CB1:~/klipper$ git status -v
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
biqu@BTT-CB1:~/klipper$ git fsck
Checking object directories: 100% (256/256), done.
Checking objects: 100% (67083/67083), done.
dangling commit 7f62f0d873657de02058d0c2d1e453593c22c2ba
dangling commit fcd848fab2d2dce629eb98d497627882bb27639b
dangling commit 142a855c98d03ee709862c9505fb112498b3b447
dangling commit 6930896f69be240ea0c990328e0316de38db1698
dangling commit ee58822e2b340d557b7a83e0e396287c1baa4e5a
dangling commit c8700a70faa8c9e104744d22e0d8199f092de94c
dangling commit 67ae7eb044461eaef8fde164ea6191f5be1fe1df
dangling commit ddb22fad45545eb7845ae036fa862e7f9d01b0fe
dangling commit afb3ff3952272e6d7eecc61200cfdbc63ed1a1bc

Thanks for any info or help in advance!

Sincerly, Mike
20250412_Log_screenshot.zip (484.1 KB)

2

This sounds like a problem on the SBC’s Linux level or internet connection.
The dangling commits are usually nothing to worry about. Can be probably cleared with git gc

3

Hi @Sineos ,

thank you for your analysis. You were right… something on the SBC with my Gateway got tangled up. Most likely due to an update of my Fritzbox.

Cheers