Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
OctoPrint 1.3.5rc1 fails to start with error Address already in use #2035
What were you doing?
I'm on the
This appears to happen (just guessing here) when
(see below for octoprint.log)
Only OctoPrint is supposed to be listening on port 5000 (which I'm guessing is the culprit here, unless OctoPrint listens on more sockets..). Interestingly it appears as if
Before the crash, I had two OctoPrint processes, one doing
In case it is related, I usually have browser tabs with previous sessions to OctoPrint open when OctoPrint is restarted (and fails to start up).
What did you expect to happen?
OctoPrint should start successfully and listen on port 5000 after booting up the Raspberry Pi Zero W.
What happened instead?
OctoPrint's main process crashed with
I can workaround the problem by manually removing
Did the same happen when running OctoPrint in safe mode?
Sorry, I didn't bother testing this.
Branch & Commit or Version of OctoPrint
Operating System running OctoPrint
Raspbian latest, Python virtualenv install of OctoPrint.
Printer model & used firmware incl. version
Browser and Version of Browser, Operating System running Browser
Link to octoprint.log
Link to contents of terminal tab or serial.log
Screenshot(s)/video(s) showing the problem:
I have read the FAQ.
Thank you for the hint with