Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timelapses not rendering #909

Closed
stevelucky opened this issue May 26, 2015 · 26 comments

Comments

Projects
None yet
3 participants
@stevelucky
Copy link

commented May 26, 2015

I'm having an issue where my timelapses aren't rendering after a print.

  1. What were you doing? Printing like normal
  2. What did you expect to happen? A timelapse film to render at the end of my print.
  3. What happened instead? An error appeared in OctoPrint that said:

Rendering of timelapse FILENAME.mpg failed with return code 1

/home/pi/.octoprint/timelapse/tmp/tmp_%05d.jpg: No such file or directory

The log said:

2015-05-16 13:43:19,235 - octoprint.timelapse - WARNING - Could not render movie, got return code 1: /home/pi/.octoprint/timelapse/tmp/tmp_%05d.jpg: No such file or directory

  1. Branch & Commit or Version of OctoPrint: Currently running 1.2.0-dev-854-gfa57f16 (devel branch) but I've had this issue for the last several versions. I've also completely wiped and recreated OctoPi and the issue persists.
  2. Printer model & used firmware incl. version
    (if applicable - always include if unsure): MakerFarm Prusa 10" i3v. Most current firmware, but I don’t have any numbers available at the moment.
  3. Browser and Version of Browser, Operating
    System running Browser (if applicable - always
    include if unsure): OX X Yosemite 10.10.4, Firefox 38.0.1
  4. Link to octoprint.log on gist.github.com or pastebin.com
    (ALWAYS INCLUDE AND DO NOT TRUNCATE):

http://pastebin.com/raw.php?i=QPb9CfUq

  1. Link to contents of terminal tab or serial.log on
    gist.github.com or pastebin.com (if applicable - always
    include if unsure or reporting communication issues AND
    DO NOT TRUNCATE):

serial.log is empty

  1. Link to contents of Javascript console in the browser
    on gist.github.com or pastebin.com or alternatively a
    screenshot (if applicable - always include if unsure
    or reporting UI issues):

http://pastebin.com/raw.php?i=c2nmfGCH

  1. Screenshot(s) showing the problem (if applicable - always
    include if unsure or reporting UI issues): I'm running a print right now and will attach a screenshot of the error as soon as it's done.

I have read the FAQ.

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

I'm currently running a print and when I SSH into the ~/.octoprint/timelapse/tmp directory, it's still empty even though I should have several Z change snapshots in there.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

Have you tried with a "Timed" timelapse? Might be that OctoPrint does not correctly detect your z-changes and that this is the actual issue.

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

This is a screenshot of the error.
screen shot 2015-05-26 at may 26 8 43 28am

l'll start another print right now that is timed instead of z change.

@GitIssueBot

This comment has been minimized.

Copy link
Collaborator

commented May 26, 2015

Hi @stevelucky,

It looks like there is some information missing from your ticket that will be needed in order to process it properly. Please take a look at the Contribution Guidelines and the page How to file a bug report on the project wiki, which will tell you exactly what your ticket has to contain in order to be processable.

If you did not intend to report a bug, please take special note of the title format to use as described in the Contribution Guidelines.

I'm closing this one now as it is currently incomplete. Please feel free to comment here to request a reopen of this issue once you can provide all required information.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

I'd like to request a reopen. I'm not sure what info is missing as I read the FAQ and gave all the information that was asked for.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

I was just about to click reopen for these exact reasons. A crucial line from the original post you since added was missing which triggered it ;)

@foosel foosel reopened this May 26, 2015

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Okay, that's what I was hoping. I noticed I missed that line. :-)

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

I just started a timed timelapse (every 20 seconds) and snapshots are appearing in the ~/.octoprint/timelapse/tmp directory. The print won't be done for a while so I can't say whether or not it's going to render, but the fact that snapshots are appearing is good. So, it sounds like you were right, OctoPrint is not detecting z changes. Any idea why that could be or how to fix it?

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

I just tried with my current devel build, and there z triggering still appears to work just fine. So maybe it's caused by files you are trying to print in some way. Could you upload a file with which the issue can be reproduced somewhere and provide the link? If you don't want to do this publicly, you can also mail me the link to osd@foosel.net

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Here's what I'm printing right now.
https://www.dropbox.com/s/zpojagdxyembxdi/Mandible-SUPPORT_fixed-PLA.gcode?dl=0

It should be noted that this happens with every single thing I print. I'm using Slic3r version .9.9

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Yes, a timed timelapse worked great. It's just the z-change timelapse that isn't.

foosel added a commit that referenced this issue May 26, 2015

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

I think I found and fixed it (see above commit). Please verify.

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Hmmm. I'm just having a little trouble finding those two files so that I can change them. What is their full path?

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Or do I just need to perform an update?

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

Just perform an update.

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Hmmm. Now I can't connect to octopi.local at all. I can still SSH in so I know it's up, but the GUI won't appear. I just get:

503 Service Unavailable

No server is available to handle this request.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

Something went wrong while updating then, or you did forget to (re)start the server. Take a look into the log: ~/.octoprint/logs/octoprint.log.

(I assume you followed this)

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Yes, I followed it exactly. Here's my octoprint.log

http://pastebin.com/raw.php?i=WWnwzRZ9

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

This is still trying to start up your old version (note the version it prints during startup: Starting OctoPrint 1.2.0-dev-854-gfa57f16-dirty (devel branch) - the "-854" there should rather be a "-862", definitely not the same version you reported this ticket on). I also notice that your copy is dirty. Try the following (note that this will throw away all your changes, so if you still want them, save them somewhere first):

cd ~/OctoPrint
git reset --hard
git pull
~/oprint/bin/python setup.py clean
~/oprint/bin/python setup.py version

Verify that this prints out something along the lines of

 Version is currently: 1.2.0-dev-862-g3ac2d5d

If yes, continue

~/oprint/bin/pip uninstall --yes OctoPrint
~/oprint/bin/python setup.py install
sudo service octoprint restart
@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

This is what I'm getting:

Version is currently: 1.2.0-dev-854-gfa57f16-dirty

I just want to restate, I followed the upgrade to the letter as per the FAQ.

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Also, when I do git pull, this is what I get:

pi@octopi ~/OctoPrint $ git pull
Updating fa57f16..3ac2d5d
error: unable to unlink old 'docs/modules/index.rst' (Permission denied)
error: unable to create file docs/modules/server.rst (Permission denied)
error: unable to unlink old 'docs/plugins/hooks.rst' (Permission denied)
error: unable to unlink old 'src/octoprint/server/util/init.py' (Permission denied)
error: unable to unlink old 'src/octoprint/server/util/tornado.py' (Permission denied)

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

Is this a current nightly of OctoPi?

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

It's from an update sometime last week.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

Yeah, but was it originally a nightly or a regular release version of OctoPi? If the former, it might be that there's an issue with the build that @guysoft needs to know about.

Anyway, your user can't write the update since it can't overwrite some of the changed files and so it ran into some very odd partial update situation. Try this:

sudo chown -R pi.pi ~/OctoPrint

This should fix the permissions hopefully. Then try the update steps again.

@stevelucky

This comment has been minimized.

Copy link
Author

commented May 26, 2015

Yes, I downloaded the 2015-02-16-octopi-wheezy-0.12.0.img from the nightlies. That permission fixed seems to have fixed it. I did that then re-ran the update and now it's showing: Version: 1.2.0-dev-862-g3ac2d5d (devel branch)

Also, it seems to have fixed the z change issue. screenshots are showing up in the ~/.octoprint/timelapse/tmp directory as I'm printing.

@foosel

This comment has been minimized.

Copy link
Owner

commented May 26, 2015

Ok, great, then this is fixed.

@foosel foosel closed this May 26, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.