Problem installing OctoPrint

What is the problem?
I can't start the server because some plugins are causing problems on startup.

When starting the server I get a WARNING message:
WARNING - Plugin "OctoPi Support Plugin" did not pass check

There are other problems I can see in the logs, but that is the one that seems most troublesome.

I also find this line at the end to be very weird:
Listening on http://[::]:5000

I'm following the instructions from this link.

What did you already try to solve it?
Reinstalled multiple times on freshly flashed Raspbian.

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)

Hardware: RASPBERRY PI 3 MODEL B+
Firmware: Raspbian GNU/Linux 9.4 (stretch)
OctoPrint version: 1.3.9

debug log from starting the server:

2018-08-29 14:31:39,445 - octoprint.startup - INFO - Starting OctoPrint 1.3.9
2018-08-29 14:31:39,448 - octoprint.startup - INFO - ******************************************************************************
2018-08-29 14:31:41,122 - octoprint.plugin.core - INFO - Loading plugins from /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins, /home/pi/.octoprint/plugins and installed plugin packages...
2018-08-29 14:31:41,124 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for discovery from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/discovery/__init__.py
2018-08-29 14:31:41,519 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for announcements from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/announcements/__init__.py
2018-08-29 14:31:42,881 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for logging from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/logging/__init__.py
2018-08-29 14:31:42,911 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for corewizard from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/corewizard/__init__.py
2018-08-29 14:31:42,931 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for softwareupdate from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/softwareupdate/__init__.py
2018-08-29 14:31:43,130 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for printer_safety_check from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/printer_safety_check/__init__.py
2018-08-29 14:31:43,152 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for octopi_support from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/octopi_support/__init__.py
2018-08-29 14:31:43,170 - octoprint.plugin.core - WARNING - Plugin "OctoPi Support Plugin" did not pass check
2018-08-29 14:31:43,173 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for cura from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/cura/__init__.py
2018-08-29 14:31:43,240 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for virtual_printer from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/virtual_printer/__init__.py
2018-08-29 14:31:43,248 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for pluginmanager from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/pluginmanager/__init__.py
2018-08-29 14:31:43,400 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for action_command_prompt from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/action_command_prompt/__init__.py
2018-08-29 14:31:44,505 - octoprint.plugins.discovery - INFO - pybonjour is not installed, Zeroconf Discovery won't be available
2018-08-29 14:31:44,506 - octoprint.plugin.core - DEBUG - Loaded plugin discovery: Discovery
2018-08-29 14:31:44,649 - octoprint.plugin.core - DEBUG - Loaded plugin announcements: Announcement Plugin
2018-08-29 14:31:44,652 - octoprint.plugin.core - DEBUG - Loaded plugin logging: Logging
2018-08-29 14:31:44,654 - octoprint.plugin.core - DEBUG - Loaded plugin corewizard: Core Wizard
2018-08-29 14:31:44,657 - octoprint.plugin.core - DEBUG - Loaded plugin softwareupdate: Software Update
2018-08-29 14:31:44,660 - octoprint.plugin.core - DEBUG - Loaded plugin printer_safety_check: Printer Safety Check
2018-08-29 14:31:44,663 - octoprint.plugin.core - DEBUG - Loaded plugin cura: CuraEngine (<= 15.04)
2018-08-29 14:31:44,665 - octoprint.plugin.core - DEBUG - Loaded plugin virtual_printer: Virtual Printer
2018-08-29 14:31:44,669 - octoprint.plugin.core - DEBUG - Loaded plugin pluginmanager: Plugin Manager
2018-08-29 14:31:44,670 - octoprint.plugin.core - DEBUG - Loaded plugin action_command_prompt: Action Command Prompt Support
2018-08-29 14:31:44,671 - octoprint.plugin.core - DEBUG - Enabled plugin discovery: Discovery
2018-08-29 14:31:44,673 - octoprint.plugin.core - DEBUG - Enabled plugin announcements: Announcement Plugin
2018-08-29 14:31:44,674 - octoprint.plugin.core - DEBUG - Enabled plugin logging: Logging
2018-08-29 14:31:44,676 - octoprint.plugin.core - DEBUG - Enabled plugin corewizard: Core Wizard
2018-08-29 14:31:44,681 - octoprint.plugin.core - DEBUG - Enabled plugin softwareupdate: Software Update
2018-08-29 14:31:44,685 - octoprint.plugin.core - DEBUG - Enabled plugin printer_safety_check: Printer Safety Check
2018-08-29 14:31:44,689 - octoprint.plugin.core - DEBUG - Enabled plugin cura: CuraEngine (<= 15.04)
2018-08-29 14:31:44,701 - octoprint.plugin.core - DEBUG - Enabled plugin virtual_printer: Virtual Printer
2018-08-29 14:31:44,707 - octoprint.plugin.core - DEBUG - Enabled plugin pluginmanager: Plugin Manager
2018-08-29 14:31:44,711 - octoprint.plugin.core - DEBUG - Enabled plugin action_command_prompt: Action Command Prompt Support
2018-08-29 14:31:44,714 - octoprint.plugin.core - INFO - Found 10 plugin(s) providing 10 mixin implementations, 8 hook handlers
2018-08-29 14:31:44,943 - octoprint.server.heartbeat - INFO - Starting server heartbeat, 900.0s interval
2018-08-29 14:31:45,001 - octoprint.server - DEBUG - Starting intermediary server on http://[::]:5000
2018-08-29 14:31:45,005 - octoprint.server - INFO - Intermediary server started
2018-08-29 14:31:45,007 - octoprint.plugin.core - INFO - Loading plugins from /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins, /home/pi/.octoprint/plugins and installed plugin packages...
2018-08-29 14:31:45,013 - octoprint.plugin.core - DEBUG - Parsing plugin metadata for octopi_support from AST of /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/octopi_support/__init__.py
2018-08-29 14:31:45,030 - octoprint.plugin.core - WARNING - Plugin "OctoPi Support Plugin" did not pass check
2018-08-29 14:31:46,274 - octoprint.plugin.core - INFO - Found 10 plugin(s) providing 10 mixin implementations, 8 hook handlers
2018-08-29 14:31:46,362 - octoprint.filemanager.storage - INFO - Initializing the file metadata for /home/pi/.octoprint/uploads...
2018-08-29 14:31:46,365 - octoprint.filemanager.storage - INFO - ... file metadata for /home/pi/.octoprint/uploads initialized successfully.
2018-08-29 14:31:46,370 - octoprint.events - DEBUG - Subscribed listener <function on_settings_update at 0x739ec370> for event SettingsUpdated
2018-08-29 14:31:46,379 - octoprint.events - DEBUG - Subscribed listener <bound method Printer._on_event_MetadataAnalysisFinished of <octoprint.printer.standard.Printer object at 0x739ea030>> for event MetadataAnalysisFinished
2018-08-29 14:31:46,380 - octoprint.events - DEBUG - Subscribed listener <bound method Printer._on_event_MetadataStatisticsUpdated of <octoprint.printer.standard.Printer object at 0x739ea030>> for event MetadataStatisticsUpdated
2018-08-29 14:31:46,387 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin logging
2018-08-29 14:31:46,393 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin virtual_printer
2018-08-29 14:31:46,399 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin action_command_prompt
2018-08-29 14:31:46,404 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin corewizard
2018-08-29 14:31:46,410 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin printer_safety_check
2018-08-29 14:31:46,466 - octoprint.plugins.softwareupdate - INFO - Loaded version cache from disk
2018-08-29 14:31:46,467 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin softwareupdate
2018-08-29 14:31:46,474 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin cura
2018-08-29 14:31:46,479 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin announcements
2018-08-29 14:31:49,232 - octoprint.util.pip - INFO - Using "/home/pi/OctoPrint/venv/bin/python2 -m pip" as command to invoke pip
2018-08-29 14:31:52,242 - octoprint.util.pip - INFO - Version of pip is 18.0
2018-08-29 14:31:52,245 - octoprint.util.pip - INFO - pip installs to /home/pi/OctoPrint/venv/lib/python2.7/site-packages (writable -> yes), --user flag needed -> no, virtual env -> yes
2018-08-29 14:31:52,248 - octoprint.util.pip - INFO - ==> pip ok -> yes
2018-08-29 14:31:52,249 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin pluginmanager
2018-08-29 14:31:52,258 - octoprint.plugin.core - DEBUG - Initialized plugin mixin implementation for plugin discovery
2018-08-29 14:31:52,259 - octoprint.plugin.core - INFO - Initialized 10 plugin implementation(s)
2018-08-29 14:31:52,273 - octoprint.plugin.core - INFO - 10 plugin(s) registered with the system:
|  Action Command Prompt Support (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/action_command_prompt
|  Announcement Plugin (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/announcements
|  Core Wizard (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/corewizard
|  CuraEngine (<= 15.04) (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/cura
|  Discovery (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/discovery
|  Logging (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/logging
|  Plugin Manager (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/pluginmanager
|  Printer Safety Check (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/printer_safety_check
|  Software Update (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/softwareupdate
|  Virtual Printer (bundled) = /home/pi/OctoPrint/venv/lib/python2.7/site-packages/octoprint/plugins/virtual_printer
2018-08-29 14:31:52,308 - octoprint.environment - INFO - Detected environment is Python 2.7.13 under Linux (linux2). Details:
|  hardware:
|    cores: 4
|    freq: 1400.0
|    ram: 972238848
|  os:
|    id: linux
|    platform: linux2
|  python:
|    pip: '18.0'
|    version: 2.7.13
|    virtualenv: /home/pi/OctoPrint/venv
2018-08-29 14:31:52,324 - octoprint.server - DEBUG - Deleting /home/pi/.octoprint/generated/webassets...
2018-08-29 14:31:52,327 - octoprint.server - DEBUG - Creating /home/pi/.octoprint/generated/webassets...
2018-08-29 14:31:52,330 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/webassets...
2018-08-29 14:31:52,332 - octoprint.server - DEBUG - Deleting /home/pi/.octoprint/generated/.webassets-cache...
2018-08-29 14:31:52,335 - octoprint.server - DEBUG - Creating /home/pi/.octoprint/generated/.webassets-cache...
2018-08-29 14:31:52,337 - octoprint.server - INFO - Reset webasset folder /home/pi/.octoprint/generated/.webassets-cache...
2018-08-29 14:31:52,382 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event ALERT
2018-08-29 14:31:52,384 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CAPTURE_DONE
2018-08-29 14:31:52,385 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CAPTURE_FAILED
2018-08-29 14:31:52,386 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CAPTURE_START
2018-08-29 14:31:52,391 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CLIENT_CLOSED
2018-08-29 14:31:52,392 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CLIENT_OPENED
2018-08-29 14:31:52,394 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CONNECTED
2018-08-29 14:31:52,397 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CONNECTING
2018-08-29 14:31:52,399 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CONNECTIVITY_CHANGED
2018-08-29 14:31:52,401 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event CONVEYOR
2018-08-29 14:31:52,403 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event COOLING
2018-08-29 14:31:52,405 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event DISCONNECTED
2018-08-29 14:31:52,407 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event DISCONNECTING
2018-08-29 14:31:52,409 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event DWELL
2018-08-29 14:31:52,412 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event EJECT
2018-08-29 14:31:52,414 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event ERROR
2018-08-29 14:31:52,415 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event E_STOP
2018-08-29 14:31:52,417 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event FILE_ADDED
2018-08-29 14:31:52,420 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event FILE_DESELECTED
2018-08-29 14:31:52,422 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event FILE_REMOVED
2018-08-29 14:31:52,423 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event FILE_SELECTED
2018-08-29 14:31:52,425 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event FIRMWARE_DATA
2018-08-29 14:31:52,426 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event FOLDER_ADDED
2018-08-29 14:31:52,428 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event FOLDER_REMOVED
2018-08-29 14:31:52,430 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event HOME
2018-08-29 14:31:52,431 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event METADATA_ANALYSIS_FINISHED
2018-08-29 14:31:52,432 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event METADATA_ANALYSIS_STARTED
2018-08-29 14:31:52,435 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event METADATA_STATISTICS_UPDATED
2018-08-29 14:31:52,437 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event MOVIE_DONE
2018-08-29 14:31:52,440 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event MOVIE_FAILED
2018-08-29 14:31:52,441 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event MOVIE_RENDERING
2018-08-29 14:31:52,443 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event POSITION_UPDATE
2018-08-29 14:31:52,445 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event POSTROLL_END
2018-08-29 14:31:52,447 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event POSTROLL_START
2018-08-29 14:31:52,449 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event POWER_OFF
2018-08-29 14:31:52,451 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event POWER_ON
2018-08-29 14:31:52,452 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINTER_PROFILE_ADDED
2018-08-29 14:31:52,454 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINTER_PROFILE_DELETED
2018-08-29 14:31:52,457 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINTER_PROFILE_MODIFIED
2018-08-29 14:31:52,459 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINTER_RESET
2018-08-29 14:31:52,461 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINTER_STATE_CHANGED
2018-08-29 14:31:52,463 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINT_CANCELLED
2018-08-29 14:31:52,465 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINT_CANCELLING
2018-08-29 14:31:52,467 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINT_DONE
2018-08-29 14:31:52,469 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINT_FAILED
2018-08-29 14:31:52,472 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINT_PAUSED
2018-08-29 14:31:52,474 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINT_RESUMED
2018-08-29 14:31:52,477 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event PRINT_STARTED
2018-08-29 14:31:52,479 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event REGISTERED_MESSAGE_RECEIVED
2018-08-29 14:31:52,482 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SETTINGS_UPDATED
2018-08-29 14:31:52,484 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SHUTDOWN
2018-08-29 14:31:52,486 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SLICING_CANCELLED
2018-08-29 14:31:52,489 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SLICING_DONE
2018-08-29 14:31:52,491 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SLICING_FAILED
2018-08-29 14:31:52,494 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SLICING_PROFILE_ADDED
2018-08-29 14:31:52,496 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SLICING_PROFILE_DELETED
2018-08-29 14:31:52,498 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SLICING_PROFILE_MODIFIED
2018-08-29 14:31:52,499 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event SLICING_STARTED
2018-08-29 14:31:52,501 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event STARTUP
2018-08-29 14:31:52,505 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event TOOL_CHANGE
2018-08-29 14:31:52,507 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event TRANSFER_DONE
2018-08-29 14:31:52,510 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event TRANSFER_FAILED
2018-08-29 14:31:52,512 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event TRANSFER_STARTED
2018-08-29 14:31:52,514 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event UPDATED_FILES
2018-08-29 14:31:52,516 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event UPLOAD
2018-08-29 14:31:52,518 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event WAITING
2018-08-29 14:31:52,521 - octoprint.events - DEBUG - Subscribed listener <bound method DebugEventListener.eventCallback of <octoprint.events.DebugEventListener object at 0x739eaf10>> for event Z_CHANGE
2018-08-29 14:31:52,739 - octoprint.server - DEBUG - Registered API of plugin announcements under URL prefix /plugin/announcements
2018-08-29 14:31:52,751 - octoprint.server - DEBUG - Registered API of plugin corewizard under URL prefix /plugin/corewizard
2018-08-29 14:31:52,763 - octoprint.server - DEBUG - Registered API of plugin cura under URL prefix /plugin/cura
2018-08-29 14:31:52,775 - octoprint.server - DEBUG - Registered API of plugin discovery under URL prefix /plugin/discovery
2018-08-29 14:31:52,799 - octoprint.server - DEBUG - Registered API of plugin logging under URL prefix /plugin/logging
2018-08-29 14:31:52,814 - octoprint.server - DEBUG - Registered API of plugin pluginmanager under URL prefix /plugin/pluginmanager
2018-08-29 14:31:52,832 - octoprint.server - DEBUG - Registered API of plugin softwareupdate under URL prefix /plugin/softwareupdate
2018-08-29 14:31:52,839 - octoprint.server - DEBUG - Registered assets of plugin action_command_prompt under URL prefix /plugin/action_command_prompt
2018-08-29 14:31:52,847 - octoprint.server - DEBUG - Registered assets of plugin printer_safety_check under URL prefix /plugin/printer_safety_check
2018-08-29 14:31:52,909 - octoprint.server - DEBUG - Adding maximum body size of 52428800B for POST requests to /plugin/pluginmanager/upload_archive)
2018-08-29 14:31:52,910 - octoprint.server - INFO - Shutting down intermediary server...
2018-08-29 14:31:53,141 - octoprint.server - INFO - Intermediary server shut down
2018-08-29 14:31:53,147 - octoprint.events - INFO - Processing startup event, this is our first event
2018-08-29 14:31:53,148 - octoprint.events - DEBUG - Firing event: Startup (Payload: None)
2018-08-29 14:31:53,149 - octoprint.events - INFO - Adding 0 events to queue that were held back before startup event
2018-08-29 14:31:53,155 - octoprint.filemanager - INFO - Adding backlog items from all storage types to analysis queue...
2018-08-29 14:31:53,163 - octoprint.filemanager - INFO - Added 0 items from storage type "local" to analysis queue
2018-08-29 14:31:53,177 - octoprint.plugins.cura - INFO - Path to CuraEngine has not been configured or does not exist (currently set to None), Cura will not be selectable for slicing
2018-08-29 14:31:53,199 - octoprint.plugins.discovery - INFO - Registered OctoPrint instance on raspberrypi for SSDP
2018-08-29 14:31:53,207 - octoprint.server - INFO - Listening on http://[::]:5000
2018-08-29 14:31:53,284 - octoprint.plugins.pluginmanager - INFO - Loaded plugin repository data from disk, was still valid
2018-08-29 14:31:53,899 - octoprint.plugins.pluginmanager - INFO - Loaded notice data from disk, was still valid

Since we're talking about Raspbian, there are a couple of install paths and you haven't mentioned which. I routinely install via the OctoPi image and it's much much faster and more pain-free if you go that route. It takes care of dependencies like the expected pip version, which is rather important for successful plugin installation.

1 Like

I was using OctoPi, but I also wanted to install it from scratch to learn how to do it, and because I'm also doing some other projects with that same Pi when it's not being used for OctoPrint.

From that link, this are exactly the commands I ran to get to that point:

cd ~
sudo apt update
sudo apt install python-pip python-dev python-setuptools python-virtualenv git libyaml-dev build-essential
mkdir OctoPrint && cd OctoPrint
virtualenv venv
source venv/bin/activate
pip install pip --upgrade
pip install https://get.octoprint.org/latest
sudo usermod -a -G tty pi
sudo usermod -a -G dialout pi
~/OctoPrint/venv/bin/octoprint serve

This was don on a fresh Raspbian install, where I had only executed sudo apt update, sudo apt dist-upgrade and then updated the time-zone and country.

This is the one that worries me. I know that my own installation of OctoPrint during every single invocation of pip suggests that I should upgrade to the latest version. I haven't because I haven't been told to by @foosel. Perhaps the latest version breaks the plugin-installation code?

pi@octopi:~/oprint $ ps -ax|grep octoprint
  489 ?        Sl    32:46 /home/pi/oprint/bin/python2 /home/pi/oprint/bin/octoprint serve --host=127.0.0.1 --port=5000

Not sure why there's a difference, but it looks like my OctoPi-imaged installation is using a virtual environment under the ~/oprint rather than ~/OctoPrint.

source ~/oprint/bin/activate
pip --version
  pip 10.0.0 from /home/pi/oprint/local/lib/python2.7/site-packages/pip (python 2.7)

Well, the commands I'm running are in a post written by @foosel that was updated 8 days ago, and pip seems to be working fine from what the logs say:
2018-08-29 14:31:52,248 - octoprint.util.pip - INFO - ==> pip ok -> yes

Also, as far as I know, during the installation of octoprint pip will not necessarily install the latest version of the packages, but the version that octoprint needs.

I mean, isn't that the whole reason OctoPrint is installed in a virtual enviroment? If it were installed on the regular python path the users could unknowingly crash it by updating the packages it depends on.

From what I found searching, there was someone with a slightly similar problem, but the solution wouldn't apply to my case.

That's your problem. @guysoft has done more than just install OctoPrint on a fresh Raspbian install. OctoPi also has, among other things, a configured installation of haproxy, which is a reverse proxy sitting on ports 80 and 443 (80 forwards to https on 443), in front of OctoPRint (port 5000) and mjpeg-streamer on (I believe) 5050.

OctoPrint and mjpeg-streamer can both be configured to use other ports and you could use NginX or Apache if you prefer something other than haproxy for your reverse proxying needs. OctoPrint appears to be working just fine, it's just that you're not connecting to it.

The original post suggests that something's running on port 5000 (OctoPrint).

http://octopi.local:5000/ might be the next thing to try.

As mentioned above, the http://octopi.local/ (port 80) version of that presumably isn't available since haproxy isn't running nor configured, one would think.

Pretty sure Guy also did some cleverness with respect to the pi user's rights and group inclusions and such.

My problem is not so much with it not running correctly as much as it is with the instructions to install on raspbian not being correct.

The link I provided is the most up-to-date set of instructions to install OctoPrint on Raspbian, Following them exactly as they are written returns an error that neither the instructions nor any documentation provide an explanation for.

I have already managed to access the server by calling the ip address of the pi with the port 5000 selected, but that still doesn't solve the error I'm getting when calling serve, and it is not what the instructions say should be done.

I have already managed to access the server by calling the ip address of the pi with the port 5000 selected, but that still doesn't solve the error I'm getting when calling serve, and it is not what the instructions say should be done.

My problem is not so much with it not running correctly as much as it is with the instructions to install on raspbian not being correct.

The link I provided is the most up-to-date set of instructions to install OctoPrint on Raspbian, Following them exactly as they are written returns an error that neither the instructions nor any documentation provide an explanation for.

Maybe @foosel can weigh in because she'll want to know about this.

Well, I think I know what's the problem with the OctoPi Support Plugin, but It's weird because I didn't ran into it when I was using the OctoPi image, or maybe I did, but I never saw the logs in there.

The plugin file doesn't seem have the RPi 3B+ model revision data needed for the tests.

I'll try to fork, correct, and install with what I think is the fix, but I've never installed from a fork before so I'm not sure whether I'll be able to do it.

I'll update later with my results.

This is not an error (and also says so - it's a warning after all, and in the next version these kind of messages will also be downgraded to info). It is merely the plugin detecting that it can't run in this environment (since it is not OctoPi) and not starting. I get this every time I fire up OctoPrint on my dev machine, it definitely isn't causing run time issues.

That means it has bound to all interface in both ipv4 and ipv6 on port 5000 ([::]:5000). Also completely normal.

Should be fixed at least in current maintenance, might even have made it into 1.3.9 still (unsure). In any case, that will only lead to the Pi model to be detected as "unknown" but not cause general problems.

To be honest, I'm kinda at a loss here what the problem is, as far as I understood you you can access the server, it's running, and the only issue are some lines in the log that caused a bit of confusion? Or did I miss something here?

It seems to me they are correct and work just fine. I suspect it's more your expectations that may need to be adjusted slightly. OctoPi is a complete image, distributed with OctoPrint, mjpeg-streamer, and haproxy set up already, in a manner that requires very little configuration before it can be used as an appliance.

OctoPrint itself is a server and application stack for controlling 3D printers. It isn't tied specifically to the RPi, and it, like many other stacks that are purpose built, it has a default port that it runs on, and can be configured to use another port. This is so that more advanced users can use it (or multiple instances of it) on hardware that may or may not be running other services.

I suspect this is just a case of a mistaken expectation as to what following those directions gets you.

I'm a teacher and most of my students have a hard time with instructions such as these for MongoDB. I will even directly say to someone "I want you to install this using Brew. Got it?" An hour later, they will be flailing with the manual version of the install. I would say that the majority of students fail this single test.

I will call this a "problem of lost juxtaposition". You can't see that there are two choices unless you first scroll all the way down. On my Safari browser with reasonable resolution, the first Install section takes up the vertical space of my screen and I can't see the Install with Homebrew version just below that. It reminds me of the video of a mouse trap design I was watching yesterday; the mice just kept making the wrong decisions over and over again.

I suspect that if the installation instructions for OctoPrint more clearly define the two paths, the average person might then get this.

In my opinion, Ubuntu does a pretty good job in this area. See example. The boxes tend to confine and segregate the available install paths. Obviously, they are a well-funded company but the instructions break things down into bite-sized pieces.

Just as you said, the lines where what threw me off and everything is working now, but it was mostly because the instructions led me to expect a different result.

What I expected was this:

pi@raspberrypi ~ $ ~/OctoPrint/venv/bin/octoprint serve
 * Running on http://0.0.0.0:5000/

but I got that long log with warnings and instead of http://0.0.0.0:5000/ I got http://[::]:5000, which at first looked like an error to me, after doing research I now know it is an ipv6 address, but it was not apparent at first.

As an extra, I was used to going to octopi.local, and had a hard time figuring out I couldn't get there, It would be useful to have a note about it on the instructions.

Pretty sure IPv6 support is new for OctoPrint v1.3.9 perhaps and we're all getting used to the new binding style for that. But every hurdle makes us smarter and we've all learned a little something, right?

Earlier, in the beginning, I was facing issues with OCtoprint Installation. Sometimes with setup and sometimes with the application. Anyways, it all feels worth it once you are done with the process. I got help from this article on Octoprint. You can ping me here anytime you get issues with Octoprint.