system stopped writing files!
Ok, on top of my previous Q about no time lapse files being generated...I now find linear_motion testing does not gen any files either!
a quick SSH, sure enough...no new filed in those default dirs. all perms for those directories are 0644.
No errors show up in moonraker or klipper logs What I do see...is the association with the 'info' prompts, now showing up in the Update Manager.... Klipper show the linear_movement and moonraker shows the timelapse.
So how do I get these two functions working again?
No errors show up in moonraker or klipper logs What I do see...is the association with the 'info' prompts, now showing up in the Update Manager.... Klipper show the linear_movement and moonraker shows the timelapse.
So how do I get these two functions working again?
13 Replies
That info prompt tells you that the linear motion extension is installed. (untracked because it's not an official part of klipper - it's an extension)
Things to look for:
1) Any errors anywhere?
2) Free disk space?
3) SD card going into write only mode because it's nearing end of life (try a new one)
4) which folders did you look in? Look at the linear motion source code for the actual file path, and make sure you're checking in the right place.
You should only be concerned about that info prompt if it dissappears (then you can use the configurator to restore the files, a simple update of klipper, moonraker or RatOS will restore them as well).
Thanks mikl . what you've suggested is where I've already been. I realize my system has not gen'ed a timelapse since 7/29/23. Along that timeline nothing was edited save managed updates. I even went as far as to removes and completely re-install all the timelapse software, without change in ops.
This VC500 is running an RPi 4 8g, running off a 250gig SSD disk not a TF card. Testing validates ther is no issue with disk access. I'll have to verify later.... /usr/tmp as well as tmp paths under /home/pi I found the framesxxx.jpg files, but all wee only 4k in size, and not viewable as normal jpgs. so something is not writing out the data itself., thus creting an issue when the script calls ffmpeg
I guess I should validate that ffmpeg is operational at the command line. But after starting this debug round, I have since found the linear vibration routines are not generating files either. It runs the scripts and etc as expected, just no data files getting written to the directories, although the csv files were written. I have verified I can read and write to these directories without issue. I have to assume some (most?) of my confusion is simply not enough knowledge of the inner workings of all the software for me to logically analyze a path to debug but I did note I'm not alone, as there is now a report on github, and it has come up on the discourse site. (code above was from the moonraker.log
I guess I should validate that ffmpeg is operational at the command line. But after starting this debug round, I have since found the linear vibration routines are not generating files either. It runs the scripts and etc as expected, just no data files getting written to the directories, although the csv files were written. I have verified I can read and write to these directories without issue. I have to assume some (most?) of my confusion is simply not enough knowledge of the inner workings of all the software for me to logically analyze a path to debug but I did note I'm not alone, as there is now a report on github, and it has come up on the discourse site. (code above was from the moonraker.log
So it's a klipper issue?
Can you link those?
no idea! The last updates (in update manager) were a couple system level, and a klipper screen only
Do you have a link to this "report on github"? and the discourse thread?
mailsail...... https://github.com/mainsail-crew/moonraker-timelapse/issues/129 crap...too early this a.m. ... brain fart.... was on mainsail github
GitHub
timelapse not rendering after print job · Issue #129 · mainsail-cre...
as title says, ever since updating via klipper, i noticed that it kept failing and there are no timelpase records anymore. what should i check? camera works fine on main fluidd page.
looking for others now
sorry...back pedaling in my brain here..... webrtc changes for crowsnest.... in my minds eye, when I got that change working.... is roughly when the timelapse stuff started messing up. Since it appears to be the frames themselves not being written, might is simply be something in crowsnest actually causing the timelapse ills.
yeah that seems likely, might just need to change something in the timelapse config
will have to go fire up the printer and take a gander. But cams work fine (on screen anyway)
You probably just need to fix
snapshoturl: http://localhost:8080/?action=snapshot
To be the snapshot url you're using for your camera
@ptegler i'd try and ask around on the mainsail discord
So those snapshot urls are wrong, they should be /webcam/?action=snapshot and /webcam3/?action=snapshot
That could be the issue.