Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
octoprint --daemon is broken in 1.3.0 #1641
What were you doing?
Trying to start OctoPrint after updating to version 1.3.0.
What did you expect to happen?
That OctoPrint starts ;-)
What happened instead?
OctoPrint seems to be stuck in a loop. There is a recurring process which takes full CPU load for a few seconds then disappears and appears again and so on.... Restarted my RaspberryPi but OctoPrint is stuck again.
Branch & Commit or Version of OctoPrint
Printer model & used firmware incl. version
Browser and Version of Browser, Operating System running Browser
Link to octoprint.log
The Log ends after updating. The endless loop doesn't produce any message in the log file.
Link to contents of terminal tab or serial.log
Screenshot(s) showing the problem:
It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).
If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.
Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.
I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2016-12-24 22:20 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!
PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.
If there's no logging output at all after the update, it doesn't look like the server process is even starting (logging that it is starting is pretty much the first thing it will do after basic initialisation of config and logging).
Let's see if there's some error thrown before the logging system is initialised. Please try SSHing into your Pi, then
What output does this produce?
PS: do not remove any lines not in [ and ] from the bug template or the bot will complain
Found the issue "Daemon operation via "octoprint --daemon start|stop|restart" is deprecated, please use "octoprint daemon start|stop|restart" from now on". But I can't remember seeing a note on it in the change log. Do I overlooked it or is it missing?
referenced this issue
Dec 12, 2016
That explains why I could not get the thing to work... I'd just updated it and was confused as to why it continued to show the service was active when it wasn't.
I even tried to update it to do "sudo octoprint serve" in the UI... but that didn't work, either... mostly for obvious reasons. I will note that
Additional note: I applied the fix at line 149 in your maintenance branch to see if that'd change things, no go on that, I think.
This is on Minibian.
First of all please try either the full
Try what happens when you do a
Also provide your
Should now really be fixed on
I couldn't reproduce any issues with the above commit anymore. I tested various permutations of
If anyone is still running into issues with the deprecated commands, please specify exactly what you are calling how in which order and what it outputs.
Will provide deets shortly.
As per your request to try
So it looks like your latest commit fixes the issue I just described with the traceback. :)
That init script definitely also still contains the bug I mentioned, you need to update that to the fixed version, see #1657 for details.
I'll probably release 1.3.1 either today or tomorrow though, so far I haven't heard anything bad about RC2. It's always a bit tricky to juggle between "enough time for people to test the RCs" and "getting fixes out to people as fast as possible".
In general though I strongly suggest to switch to a fixed branch or even RC/release channel instead of manually applying individual patches - those ARE usually self contained, but I do not test each individual commit against
I've only run a few prints through 1.3.1.rc2, but seems fine so far.