Pi 3 Model B+ Octoprint Build

Jeff_Holverson · April 20, 2018, 12:12am

Yes, worked through all the tips. It is a simple internal configuration error but massively frustrating. Imagine, buying a Koenigsegg, getting it home, then being told that it won't run on the gas in your country.

This is the lengthy output from the interrogative:
wlan0 Scan completed :
Cell 01 - Address: A0:04:60:B6:DB:78
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=70/70 Signal level=-28 dBm
Encryption key:on
ESSID:"NETGEAR16"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 80ms ago
IE: Unknown: 00094E4554474541523136
IE: Unknown: 010882848B961224486C
IE: Unknown: 030103
IE: Unknown: 2A0104
IE: Unknown: 32040C183060
IE: Unknown: 2D1AEC1117FFFF000001000000000000000000000000000000000000
IE: Unknown: 3D1603000600000000000000000000000000000000000000
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 7F080100000000000000
IE: Unknown: 0B05060003127A
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F080100000000000000
IE: Unknown: 0706555320010B10
IE: Unknown: DDA60050F204104A0001101044000102103B0001031047001038833092309218838FA5A00460B6DB781021000D4E4554474541522C20496E632E1023001D4E45544745415220576972656C6573732041636365737320506F696E741024000552363232301042000831323334353637381054000800060050F20400011011001352363232302028576972656C6573732041502910080002210C103C0001011049000600372A000120
IE: Unknown: DD07000C4303000000
Cell 02 - Address: B8:3E:59:47:4C:DB
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=70/70 Signal level=-32 dBm
Encryption key:on
ESSID:"DIRECT-roku-694-2BB274"
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 2410ms ago
IE: Unknown: 00164449524543542D726F6B752D3639342D324242323734
IE: Unknown: 01088C129824B048606C
IE: Unknown: 030103
IE: Unknown: 0706555320010B1E
IE: Unknown: 200100
IE: Unknown: 23021200
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 2D1ABC1916FFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1603001300000000000000000000000000000000000000
IE: Unknown: 7F080400000000000040
IE: Unknown: DD090010180201004C0000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
IE: Unknown: DD050050F20500
IE: Unknown: DDA00050F204104A0001101044000102103B0001031047001022210203040506070809B83E59474CDB10210004526F6B7510230006526F6B7520331024001834323030582076657220382E30206275696C6420343138341042000C31472A2A2A2A2A2A2A3639341054000800060050F2040001101100164449524543542D726F6B752D3639342D324242323734100800020000103C0001011049000600372A000120
IE: Unknown: DD30506F9A09020200372B0D2100BA3E59474CD9008000080050F2040005001011000C526F6B752033202D203639340E0000
IE: Unknown: DD16506F9A0A00000601111C4400960A0006BA3E59474CD9
Cell 03 - Address: B8:3E:59:47:4C:DB
Channel:3
Frequency:2.422 GHz (Channel 3)
Quality=70/70 Signal level=-38 dBm
Encryption key:on
ESSID:"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 80ms ago
IE: Unknown: 001600000000000000000000000000000000000000000000
IE: Unknown: 01088C129824B048606C
IE: Unknown: 030103
IE: Unknown: 050400030000
IE: Unknown: 0706555320010B1E
IE: Unknown: 200100
IE: Unknown: 23021200
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 2D1ABC1916FFFF000000000000000000000000000000000000000000
IE: Unknown: 3D1603001300000000000000000000000000000000000000
IE: Unknown: 7F080400000000000040
IE: Unknown: DD090010180201004C0000
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
IE: Unknown: DD050050F20500
IE: Unknown: DD520050F204104A00011010440001021047001022210203040506070809B83E59474CDB1049000600372A0001201054000800060050F2040001101100164449524543542D726F6B752D3639342D324242323734
IE: Unknown: DD12506F9A09020200372B030600BA3E59474CD9
IE: Unknown: DD0D506F9A0A00000601111C440096
Cell 04 - Address: 58:8B:F3:16:20:86
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=28/70 Signal level=-82 dBm
Encryption key:on
ESSID:"CenturyLink2672"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000000000000000
Extra: Last beacon: 80ms ago
IE: Unknown: 000F43656E747572794C696E6B32363732
IE: Unknown: 010882848B962430486C
IE: Unknown: 03010B
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: 2D1AAC181BFFFF000000000000000000000000000000000000000000
IE: Unknown: 3D160B081500000000000000000000000000000000000000
IE: Unknown: 7F080000000000000040
IE: Unknown: DD7B0050F204104A0001101044000102103B00010310470010C863F372B3EE5BED5F9D173D3FE70C21102100055A7958454C1023000643313130305A1024000643313130305A1042000839363332363847571054000800060050F20400011011000643313130305A10080002200C103C0001011049000600372A000120
IE: Unknown: DD090010180203000C0000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00

Also tried compiling it denovo from the Github instructions, that ended in this at the build prompt:pi@raspberrypi:~/OctoPi/src $ sudo bash -x ./build_dist
+++ dirname ./build_dist
++ cd .
++ pwd

DIR=/home/pi/OctoPi/src
export DIST_PATH=/home/pi/OctoPi/src
DIST_PATH=/home/pi/OctoPi/src
export CUSTOM_PI_OS_PATH=/home/pi/CustomPiOS/src
CUSTOM_PI_OS_PATH=/home/pi/CustomPiOS/src
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/pi/CustomPiOS/src
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/pi/CustomPiOS/src
echo /home/pi/CustomPiOS/src
/home/pi/CustomPiOS/src
/home/pi/CustomPiOS/src/build_custom_os
echo 'Distro path: /home/pi/OctoPi/src'
Distro path: /home/pi/OctoPi/src
echo 'CustomPiOS path: /home/pi/CustomPiOS/src'
CustomPiOS path: /home/pi/CustomPiOS/src
echo ================================================================
================================================================
+++ dirname /home/pi/CustomPiOS/src/build_custom_os
++ cd /home/pi/CustomPiOS/src
++ pwd
DIR=/home/pi/CustomPiOS/src
/home/pi/CustomPiOS/src/build
'[' -n '' ']'
LOG=build.log
define SCRIPT
IFS='\n'
read -r -d '' SCRIPT
true
'[' build.log '!=' no ']'
touch build.log
chmod 666 build.log
eval 'BUILD_SCRIPT_PATH=(dirname (realpath -s BASH_SOURCE)) source {BUILD_SCRIPT_PATH}/common.sh
install_cleanup_trap

CUSTOM_OS_PATH=(dirname (realpath -s $0))
pushd $CUSTOM_OS_PATH
export OCTOPI_COMMIT=git rev-parse HEAD
popd

source {CUSTOM_PI_OS_PATH}/config {@}
${CUSTOM_PI_OS_PATH}/config_sanity

[ "CONFIG_ONLY" == "yes" ] || source {CUSTOM_OS_PATH}/custompios

tee build.log
'
++++ realpath -s /home/pi/CustomPiOS/src/build
+++ dirname /home/pi/CustomPiOS/src/build
++ BUILD_SCRIPT_PATH=/home/pi/CustomPiOS/src
++ source /home/pi/CustomPiOS/src/common.sh
++ install_cleanup_trap
++ set -e
++ trap cleanup SIGINT SIGTERM
++++ realpath -s /home/pi/CustomPiOS/src/build
+++ dirname /home/pi/CustomPiOS/src/build
++ CUSTOM_OS_PATH=/home/pi/CustomPiOS/src
++ pushd /home/pi/CustomPiOS/src
/home/pi/CustomPiOS/src /home/pi/OctoPi/src
+++ git rev-parse HEAD
++ export OCTOPI_COMMIT=6b44439433b19e12901a2387eb8a9e87ceaabc91
++ OCTOPI_COMMIT=6b44439433b19e12901a2387eb8a9e87ceaabc91
++ popd
/home/pi/OctoPi/src
++ source /home/pi/CustomPiOS/src/config
+++++ realpath -s /home/pi/CustomPiOS/src/config
++++ dirname /home/pi/CustomPiOS/src/config
+++ CONFIG_DIR=/home/pi/CustomPiOS/src
+++ BUILD_VARIANT=default
+++ BUILD_FLAVOR=default
+++ WORKSPACE_POSTFIX=
+++ '[' 0 -gt 0 ']'
+++ '[' 0 -gt 1 ']'
+++ '[' default '!=' default ']'
+++ echo -e '--> Building VARIANT default, FLAVOR default'
--> Building VARIANT default, FLAVOR default
+++ '[' -n '' ']'
+++ '[' -n '' ']'
+++ '[' -f /home/pi/CustomPiOS/src/config.local ']'
+++ source /home/pi/OctoPi/src/config
++++ export DIST_NAME=OctoPi
++++ DIST_NAME=OctoPi
++++ export DIST_VERSION=0.15.0
++++ DIST_VERSION=0.15.0
++++ export 'MODULES=base(raspicam, network, disable-services(octopi), password-for-sudo)'
++++ MODULES='base(raspicam, network, disable-services(octopi), password-for-sudo)'
+++ '[' -f /home/pi/OctoPi/src/config.local ']'
+++ TMP='base,raspicam, network, disable-services,octopi), password-for-sudo)'
+++ TMP='base,raspicam,network,disable-services,octopi),password-for-sudo)'
+++ MODULES_LIST=base,raspicam,network,disable-services,octopi,,password-for-sudo,
++++ echo base,raspicam,network,disable-services,octopi,,password-for-sudo,
++++ tr , '\n'
+++ for module in (echo "{MODULES_LIST}" | tr "," "\n")
+++ '[' -d /home/pi/OctoPi/src/modules/base ']'
+++ '[' -d /home/pi/CustomPiOS/src/modules/base ']'
+++ export MODULE_PATH=/home/pi/CustomPiOS/src/modules/base
+++ MODULE_PATH=/home/pi/CustomPiOS/src/modules/base
+++ echo loading base config at /home/pi/CustomPiOS/src/modules/base/config
loading base config at /home/pi/CustomPiOS/src/modules/base/config
+++ '[' -f /home/pi/CustomPiOS/src/modules/base/config ']'
+++ source /home/pi/CustomPiOS/src/modules/base/config
++++ '[' -n '' ']'
++++ BASE_PRESCRIPT=
++++ '[' -n '' ']'
++++ BASE_POSTSCRIPT=
++++ '[' -n '' ']'
++++ BASE_IMAGE_PATH=/home/pi/OctoPi/src/image
++++ '[' -n '' ']'
++++ BASE_IMAGE_RASPBIAN=yes
++++ '[' -n '' ']'
+++++ head -n 1
+++++ ls -t /home/pi/OctoPi/src/image/2018-04-18-raspbian-stretch-lite.zip
++++ BASE_ZIP_IMG=/home/pi/OctoPi/src/image/2018-04-18-raspbian-stretch-lite.zip
++++ '[' -n '' ']'
++++ BASE_WORKSPACE=/home/pi/OctoPi/src/workspace
++++ '[' -n '' ']'
++++ BASE_MOUNT_PATH=/home/pi/OctoPi/src/workspace/mount
++++ '[' -n '' ']'
++++ BASE_ROOT_PARTITION=2
++++ '[' -n '' ']'
++++ BASE_IMAGE_ENLARGEROOT=400
++++ '[' -n '' ']'
++++ BASE_IMAGE_RESIZEROOT=200
++++ '[' -n '' ']'
++++ BASE_APT_CACHE=/home/pi/OctoPi/src/workspace/aptcache
++++ '[' -n '' ']'
++++ BASE_APT_PROXY=
++++ '[' -n '' ']'
++++ BASE_PYPI_INDEX=
++++ '[' -n '' ']'
++++ BASE_OVERRIDE_HOSTNAME=octopi
++++ '[' -n '' ']'
++++ BASE_BUILD_REPO_MIRROR=
++++ '[' -n '' ']'
++++ BASE_SSH_ENABLE=yes
++++ '[' -n '' ']'
+++++ pushd /home/pi/CustomPiOS/src
+++++ git rev-parse HEAD
+++++ popd
++++ BASE_COMMIT=6b44439433b19e12901a2387eb8a9e87ceaabc91
+++ echo ================================================================
================================================================
+++ echo 'Using the following config:'
Using the following config:
+++ module_up=BASE
+++ module_up=BASE_
+++ IFS=
+++ read -r var
++++ compgen -A variable BASE_
+++ export BASE_APT_CACHE
+++ echo BASE_APT_CACHE
BASE_APT_CACHE
+++ IFS=
+++ read -r var
+++ export BASE_APT_PROXY
+++ echo BASE_APT_PROXY
BASE_APT_PROXY
+++ IFS=
+++ read -r var
+++ export BASE_BUILD_REPO_MIRROR
+++ echo BASE_BUILD_REPO_MIRROR
BASE_BUILD_REPO_MIRROR
+++ IFS=
+++ read -r var
+++ export BASE_COMMIT
+++ echo BASE_COMMIT
BASE_COMMIT
+++ IFS=
+++ read -r var
+++ export BASE_IMAGE_ENLARGEROOT
+++ echo BASE_IMAGE_ENLARGEROOT
BASE_IMAGE_ENLARGEROOT
+++ IFS=
+++ read -r var
+++ export BASE_IMAGE_PATH
+++ echo BASE_IMAGE_PATH
BASE_IMAGE_PATH
+++ IFS=
+++ read -r var
+++ export BASE_IMAGE_RASPBIAN
+++ echo BASE_IMAGE_RASPBIAN
BASE_IMAGE_RASPBIAN
+++ IFS=
+++ read -r var
+++ export BASE_IMAGE_RESIZEROOT
+++ echo BASE_IMAGE_RESIZEROOT
BASE_IMAGE_RESIZEROOT
+++ IFS=
+++ read -r var
+++ export BASE_MOUNT_PATH
+++ echo BASE_MOUNT_PATH
BASE_MOUNT_PATH
+++ IFS=
+++ read -r var
+++ export BASE_OVERRIDE_HOSTNAME
+++ echo BASE_OVERRIDE_HOSTNAME
BASE_OVERRIDE_HOSTNAME
+++ IFS=
+++ read -r var
+++ export BASE_POSTSCRIPT
+++ echo BASE_POSTSCRIPT
BASE_POSTSCRIPT
+++ IFS=
+++ read -r var
+++ export BASE_PRESCRIPT
+++ echo BASE_PRESCRIPT
BASE_PRESCRIPT
+++ IFS=
+++ read -r var
+++ export BASE_PYPI_INDEX
+++ echo BASE_PYPI_INDEX
BASE_PYPI_INDEX
+++ IFS=
+++ read -r var
+++ export BASE_ROOT_PARTITION
+++ echo BASE_ROOT_PARTITION
BASE_ROOT_PARTITION
+++ IFS=
+++ read -r var
+++ export BASE_SSH_ENABLE
+++ echo BASE_SSH_ENABLE
BASE_SSH_ENABLE
+++ IFS=
+++ read -r var
+++ export BASE_WORKSPACE
+++ echo BASE_WORKSPACE
BASE_WORKSPACE
+++ IFS=
+++ read -r var
+++ export BASE_ZIP_IMG
+++ echo BASE_ZIP_IMG
BASE_ZIP_IMG
+++ IFS=
+++ read -r var
+++ echo ================================================================
================================================================
+++ for module in (echo "{MODULES_LIST}" | tr "," "\n")
+++ '[' -d /home/pi/OctoPi/src/modules/raspicam ']'
+++ '[' -d /home/pi/CustomPiOS/src/modules/raspicam ']'
+++ export MODULE_PATH=/home/pi/CustomPiOS/src/modules/raspicam
+++ MODULE_PATH=/home/pi/CustomPiOS/src/modules/raspicam
+++ echo loading raspicam config at /home/pi/CustomPiOS/src/modules/raspicam/config
loading raspicam config at /home/pi/CustomPiOS/src/modules/raspicam/config
+++ '[' -f /home/pi/CustomPiOS/src/modules/raspicam/config ']'
+++ source /home/pi/CustomPiOS/src/modules/raspicam/config
+++ echo ================================================================
================================================================
+++ echo 'Using the following config:'
Using the following config:
+++ module_up=RASPICAM
+++ module_up=RASPICAM_
+++ IFS=
+++ read -r var
++++ compgen -A variable RASPICAM_
+++ echo ================================================================
================================================================
+++ for module in (echo "{MODULES_LIST}" | tr "," "\n")
+++ '[' -d /home/pi/OctoPi/src/modules/network ']'
+++ '[' -d /home/pi/CustomPiOS/src/modules/network ']'
+++ export MODULE_PATH=/home/pi/CustomPiOS/src/modules/network
+++ MODULE_PATH=/home/pi/CustomPiOS/src/modules/network
+++ echo loading network config at /home/pi/CustomPiOS/src/modules/network/config
loading network config at /home/pi/CustomPiOS/src/modules/network/config
+++ '[' -f /home/pi/CustomPiOS/src/modules/network/config ']'
+++ source /home/pi/CustomPiOS/src/modules/network/config
+++ echo ================================================================
================================================================
+++ echo 'Using the following config:'
Using the following config:
+++ module_up=NETWORK
+++ module_up=NETWORK_
+++ IFS=
+++ read -r var
++++ compgen -A variable NETWORK_
+++ echo ================================================================
================================================================
+++ for module in (echo "{MODULES_LIST}" | tr "," "\n")
+++ '[' -d /home/pi/OctoPi/src/modules/disable-services ']'
+++ '[' -d /home/pi/CustomPiOS/src/modules/disable-services ']'
+++ export MODULE_PATH=/home/pi/CustomPiOS/src/modules/disable-services
+++ MODULE_PATH=/home/pi/CustomPiOS/src/modules/disable-services
+++ echo loading disable-services config at /home/pi/CustomPiOS/src/modules/disable-services/config
loading disable-services config at /home/pi/CustomPiOS/src/modules/disable-services/config
+++ '[' -f /home/pi/CustomPiOS/src/modules/disable-services/config ']'
+++ echo 'WARNING: module disable-services has no config file'
WARNING: module disable-services has no config file
+++ echo ================================================================
================================================================
+++ echo 'Using the following config:'
Using the following config:
+++ module_up=DISABLE-SERVICES
+++ module_up=DISABLE_SERVICES_
+++ IFS=
+++ read -r var
++++ compgen -A variable DISABLE_SERVICES_
+++ echo ================================================================
================================================================
+++ for module in (echo "{MODULES_LIST}" | tr "," "\n")
+++ '[' -d /home/pi/OctoPi/src/modules/octopi ']'
+++ export MODULE_PATH=/home/pi/OctoPi/src/modules/octopi
+++ MODULE_PATH=/home/pi/OctoPi/src/modules/octopi
+++ echo loading octopi config at /home/pi/OctoPi/src/modules/octopi/config
loading octopi config at /home/pi/OctoPi/src/modules/octopi/config
+++ '[' -f /home/pi/OctoPi/src/modules/octopi/config ']'
+++ source /home/pi/OctoPi/src/modules/octopi/config
++++ '[' -n '' ']'
+++++ wget -q -O - https://api.github.com/repos/foosel/OctoPrint/releases/latest
+++++ grep zipball_url
+++++ cut -d : -f 2,3
+++++ tr -d ,
+++++ tr -d '"'
++++ OCTOPI_OCTOPRINT_ARCHIVE=' https://api.github.com/repos/foosel/OctoPrint/zipball/1.3.8'
++++ '[' -n '' ']'
++++ OCTOPI_OCTOPRINT_REPO_SHIP=https://github.com/foosel/OctoPrint.git
++++ '[' -n '' ']'
++++ OCTOPI_INCLUDE_OCTOPRINT=yes
++++ '[' -n '' ']'
++++ OCTOPI_PYBONJOUR_ARCHIVE=https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/pybonjour/pybonjour-1.1.1.tar.gz
++++ '[' -n '' ']'
++++ OCTOPI_CURAENGINE_VERSION=15.04.6
++++ '[' -n '' ']'
++++ OCTOPI_CURAENGINE_ARCHIVE=https://github.com/Ultimaker/CuraEngine/archive/15.04.6.zip
++++ '[' -n '' ']'
++++ OCTOPI_INCLUDE_CURAENGINE=yes
++++ '[' -n '' ']'
++++ OCTOPI_MJPGSTREAMER_REPO_SHIP=https://github.com/jacksonliam/mjpg-streamer.git
++++ '[' -n '' ']'
++++ OCTOPI_MJPGSTREAMER_REPO_BUILD=
++++ '[' -n '' ']'
++++ OCTOPI_MJPGSTREAMER_REPO_BRANCH=master
++++ '[' -n '' ']'
++++ OCTOPI_MJPGSTREAMER_REPO_DEPTH=1
++++ '[' -n '' ']'
++++ OCTOPI_INCLUDE_MJPGSTREAMER=yes
++++ '[' -n '' ']'
++++ OCTOPI_INCLUDE_HAPROXY=yes
++++ '[' -n '' ']'
++++ OCTOPI_INCLUDE_WIRINGPI=yes
++++ '[' -n '' ']'
+++++ wget -q -O - https://api.github.com/repos/mikefarah/yq/releases/latest
+++++ grep browser_download_url
+++++ grep yq_linux_arm
+++++ tr -d ,
+++++ tr -d '"'
+++++ cut -d : -f 2,3
++++ OCTOPI_YQ_DOWNLOAD=' https://github.com/mikefarah/yq/releases/download/1.14.1/yq_linux_arm'
++++ '[' -n 6b44439433b19e12901a2387eb8a9e87ceaabc91 ']'
+++ echo ================================================================
================================================================
+++ echo 'Using the following config:'
Using the following config:
+++ module_up=OCTOPI
+++ module_up=OCTOPI_
+++ IFS=
+++ read -r var
++++ compgen -A variable OCTOPI_
+++ export OCTOPI_COMMIT
+++ echo OCTOPI_COMMIT
OCTOPI_COMMIT
+++ IFS=
+++ read -r var
+++ export OCTOPI_CURAENGINE_ARCHIVE
+++ echo OCTOPI_CURAENGINE_ARCHIVE
OCTOPI_CURAENGINE_ARCHIVE
+++ IFS=
+++ read -r var
+++ export OCTOPI_CURAENGINE_VERSION
+++ echo OCTOPI_CURAENGINE_VERSION
OCTOPI_CURAENGINE_VERSION
+++ IFS=
+++ read -r var
+++ export OCTOPI_INCLUDE_CURAENGINE
+++ echo OCTOPI_INCLUDE_CURAENGINE
OCTOPI_INCLUDE_CURAENGINE
+++ IFS=
+++ read -r var
+++ export OCTOPI_INCLUDE_HAPROXY
+++ echo OCTOPI_INCLUDE_HAPROXY
OCTOPI_INCLUDE_HAPROXY
+++ IFS=
+++ read -r var
+++ export OCTOPI_INCLUDE_MJPGSTREAMER
+++ echo OCTOPI_INCLUDE_MJPGSTREAMER
OCTOPI_INCLUDE_MJPGSTREAMER
+++ IFS=
+++ read -r var
+++ export OCTOPI_INCLUDE_OCTOPRINT
+++ echo OCTOPI_INCLUDE_OCTOPRINT
OCTOPI_INCLUDE_OCTOPRINT
+++ IFS=
+++ read -r var
+++ export OCTOPI_INCLUDE_WIRINGPI
+++ echo OCTOPI_INCLUDE_WIRINGPI
OCTOPI_INCLUDE_WIRINGPI
+++ IFS=
+++ read -r var
+++ export OCTOPI_MJPGSTREAMER_REPO_BRANCH
+++ echo OCTOPI_MJPGSTREAMER_REPO_BRANCH
OCTOPI_MJPGSTREAMER_REPO_BRANCH
+++ IFS=
+++ read -r var
+++ export OCTOPI_MJPGSTREAMER_REPO_BUILD
+++ echo OCTOPI_MJPGSTREAMER_REPO_BUILD
OCTOPI_MJPGSTREAMER_REPO_BUILD
+++ IFS=
+++ read -r var
+++ export OCTOPI_MJPGSTREAMER_REPO_DEPTH
+++ echo OCTOPI_MJPGSTREAMER_REPO_DEPTH
OCTOPI_MJPGSTREAMER_REPO_DEPTH
+++ IFS=
+++ read -r var
+++ export OCTOPI_MJPGSTREAMER_REPO_SHIP
+++ echo OCTOPI_MJPGSTREAMER_REPO_SHIP
OCTOPI_MJPGSTREAMER_REPO_SHIP
+++ IFS=
+++ read -r var
+++ export OCTOPI_OCTOPRINT_ARCHIVE
+++ echo OCTOPI_OCTOPRINT_ARCHIVE
OCTOPI_OCTOPRINT_ARCHIVE
+++ IFS=
+++ read -r var
+++ export OCTOPI_OCTOPRINT_REPO_SHIP
+++ echo OCTOPI_OCTOPRINT_REPO_SHIP
OCTOPI_OCTOPRINT_REPO_SHIP
+++ IFS=
+++ read -r var
+++ export OCTOPI_PYBONJOUR_ARCHIVE
+++ echo OCTOPI_PYBONJOUR_ARCHIVE
OCTOPI_PYBONJOUR_ARCHIVE
+++ IFS=
+++ read -r var
+++ export OCTOPI_YQ_DOWNLOAD
+++ echo OCTOPI_YQ_DOWNLOAD
OCTOPI_YQ_DOWNLOAD
+++ IFS=
+++ read -r var
+++ echo ================================================================
================================================================
+++ for module in (echo "{MODULES_LIST}" | tr "," "\n")
+++ '[' -d /home/pi/OctoPi/src/modules/password-for-sudo ']'
+++ '[' -d /home/pi/CustomPiOS/src/modules/password-for-sudo ']'
+++ export MODULE_PATH=/home/pi/CustomPiOS/src/modules/password-for-sudo
+++ MODULE_PATH=/home/pi/CustomPiOS/src/modules/password-for-sudo
+++ echo loading password-for-sudo config at /home/pi/CustomPiOS/src/modules/password-for-sudo/config
loading password-for-sudo config at /home/pi/CustomPiOS/src/modules/password-for-sudo/config
+++ '[' -f /home/pi/CustomPiOS/src/modules/password-for-sudo/config ']'
+++ echo 'WARNING: module password-for-sudo has no config file'
WARNING: module password-for-sudo has no config file
+++ echo ================================================================
================================================================
+++ echo 'Using the following config:'
Using the following config:
+++ module_up=PASSWORD-FOR-SUDO
+++ module_up=PASSWORD_FOR_SUDO_
+++ IFS=
+++ read -r var
++++ compgen -A variable PASSWORD_FOR_SUDO_
+++ echo ================================================================
================================================================
++ /home/pi/CustomPiOS/src/config_sanity
++ '[' '' == yes ']'
++ source /home/pi/CustomPiOS/src/custompios
+++ set -e
+++ export LC_ALL=C
+++ LC_ALL=C
+++ source /home/pi/CustomPiOS/src/common.sh
+++ mkdir -p /home/pi/OctoPi/src/workspace
+++ mkdir -p /home/pi/OctoPi/src/workspace/mount
+++ install_cleanup_trap
+++ set -e
+++ trap cleanup SIGINT SIGTERM
+++ install_fail_on_error_trap
+++ set -e
+++ trap 'echo_red "build failed, unmounting image..." && cd $DIST_PATH && ( unmount_image $BASE_MOUNT_PATH force || true ) && echo_red -e "\nBUILD FAILED!\n"' ERR
+++ unmount_image /home/pi/OctoPi/src/workspace/mount force
+++ mount_path=/home/pi/OctoPi/src/workspace/mount
+++ force=
+++ '[' 2 -gt 1 ']'
+++ force=force
+++ '[' -n force ']'
++++ sudo lsof /home/pi/OctoPi/src/workspace/mount
++++ awk '{print $2}'
sudo: lsof: command not found
++++ sudo mount
++++ grep /home/pi/OctoPi/src/workspace/mount
++++ awk -F on '{print $2}'
++++ awk '{print $1}'
++++ sort -r
+++ pushd /home/pi/OctoPi/src/workspace
/home/pi/OctoPi/src/workspace /home/pi/OctoPi/src
+++ '[' -e '*.img' ']'
+++ '[' '!' -f /home/pi/OctoPi/src/image/2018-04-18-raspbian-stretch-lite.zip ']'
+++ '[' /home/pi/OctoPi/src/image/2018-04-18-raspbian-stretch-lite.zip == '' ']'
+++ 7za x -aoa /home/pi/OctoPi/src/image/2018-04-18-raspbian-stretch-lite.zip
/home/pi/CustomPiOS/src/custompios: line 46: 7za: command not found
++++ echo_red 'build failed, unmounting image...'
++++ echo -e -n '\e[91m'
++++ echo build failed, unmounting image...
build failed, unmounting image...
++++ echo -e -n '\e[0m'
++++ cd /home/pi/OctoPi/src
++++ unmount_image /home/pi/OctoPi/src/workspace/mount force
++++ mount_path=/home/pi/OctoPi/src/workspace/mount
++++ force=
++++ '[' 2 -gt 1 ']'
++++ force=force
++++ '[' -n force ']'
+++++ sudo lsof /home/pi/OctoPi/src/workspace/mount
+++++ awk '{print $2}'
sudo: lsof: command not found
+++++ sudo mount
+++++ grep /home/pi/OctoPi/src/workspace/mount
+++++ awk -F on '{print $2}'
+++++ awk '{print $1}'
+++++ sort -r
++++ echo_red -e '\nBUILD FAILED!\n'
++++ echo -e -n '\e[91m'
++++ echo -e '\nBUILD' 'FAILED!\n'

BUILD FAILED!

++++ echo -e -n '\e[0m'

exit 1

I know that is blowing up the forum but maybe it will mean something to someone who knows.
I am screwed, guess my ignorance ensures I cannot use the Pi as planned for the Anet A8 and have to use the acursed PC.
Thank you for trying.
Jeff

John_Mc · April 20, 2018, 1:41am

@Jeff_Holverson I think the problem is that your Pi is just not connecting to WiFi. I'd bet that the rest of your OctoPi installation is running fine. Have you tried connecting your Pi to your network with an ethernet cable, rather than via WiFi? Even if this is not a permanent fix for you, it woud confirm that you have everything else set up.

On your output from sudo iwlist wlan0 scan:
The good news is, your Pi's WiFi is turned on and can see activity in your area.

Your pi can see a strong, clear signal for "NETGEAR16". If that's the one you are trying to connect to, it should be possible. There are two other fairly strong cells using the same WiFi channel (one appears to be your Roku, I don't know what the other is). I don't know enough about this to say whether those multiple access points on the same channel are a part of the problem or not. It certainly would not hurt to change your router to some other channel that doesn't have a lot of traffic on it. (If you don't already know how to change the channel, you are going to have to google changing your specific model router's WiFi channel to find out.)

The Pi also sees a very weak signal for WiFi SSID "CenturyLink2672" on WiFi channel 11. If this is what you are trying to connect to, your Pi needs to be a lot closer, or remove obstructions which may be blocking the signal.

John_Mc · April 20, 2018, 1:52am

@DM_Cam - I seem to remember someone else getting the "Could not communicate with wpa-supplicant" error, and it turned out to be that their editing of the /boot/octopi-wpa-supplicant.txt file was messed up. I think they had failed to uncomment one of the needed lines (left a # in where it should have been removed), or messed up the indenting, or some other minor thing. It should look just like this (with your own SSID and password filled in, indentation preserved, and the quotes left in place):

## WPA/WPA2 secured
network={
  ssid="MYSSID"
  psk="MYPASSWORD"
}

If that doesn't work, and you've already worked through the WiFi tips post I linked earlier, you may be approaching the limit of what I can help with, and we'll need to call in someone with more expertise.

What do you see when you issue the sudo iwlist wlan0 scan command I mentioned earlier?

Jeff_Holverson · April 20, 2018, 2:08am

Thank you again.
I use the Netgear16 router and that is my primary router. The other connected devices are on separate channels and so shouldn't effect the RPI-Octoprint connect.
It is hard to explore any further due to the limited options available while the Octoprint image is running, The SSID is Netgear16 and I triple checked the password for typo's and case issues. I also verified that the supplicant file changes were done correctly, three times. It seems that maybe another level might be able to help. I am no expert at this but I use the Pi as my main computer and am fairly competent with the OS.
Please show the information to anyone that can help and if the program needs a RPI 3B+ to work out the kinks they are welcome to one from me. This is the machine that t he whole world will be using for the foreseeable future and I want your program to work seamlessly and be super easy.
Be safe!
Jeff KG7TXI

OutsourcedGuru · April 20, 2018, 3:53am

For what it's worth, I installed the latest nightly for OctoPi this morning on a Raspberry Pi 3 B+ and it connected to my wi-fi without problems.

Router: Netgear Gateway C3000-100NAS using WPA2-PSK [AES] for wi-fi authentication, (2.4GHz b/g/n)

You might check your router's connection table to see if the Raspi is connected and has been issued an IP address.

Adafruit's Pi Finder is helpful when adding a Pi to the network (assuming it's connected of course).

Sometimes I connect a keyboard/mouse/monitor to a new Raspi setup so that I can log in locally and adjust the network settings as necessary. (Once it's happy, it then goes headless.)

DM_Cam · April 20, 2018, 11:21am

Hey John,

Since having the optional power adapter, I took the PI to work and after revising the WPA config, there were some hash tags I know I removed but were not saved. So one # in the WPA area was still there and I had two countries uncommented. Double checked everything, inserted my work wifi info and immediately connected. Thanks for your support.

John_Mc · April 20, 2018, 1:28pm

Jeff - the first three listed were all showing on channel 3 (2.422 GHz). Perhaps some of these may vary from time to time, since some devices have the ability to seek a clear channel. At the time you ran the command, however, three were on the same channel. No guarantee that changing the channel will fix the problem, but it can't hurt.

John_Mc · April 20, 2018, 1:36pm

@OutsourcedGuru - In Jeff's case, the output of the ifconfig command he sent to his Pi already shows that he is not connected to WiFi so has no IP address form that. The output from sudo iwlist wlan0 scan shows that his Pi can see the nerwork (and has a strong signal from it). So between the two, be know the WiFi chip on his Pi is up and running, but for some reason, he is not logging in to the desired network.

He's apparently got some sort of connection to the Pi, since he is able to access the command line.

DM_Cam · April 20, 2018, 1:56pm

Jeff you need to make sure your # are removed correctly in WPA (4 lines )and your correct country code is uncommented if it is not the default UK. If it isnt the UK you need to put the # tag back in. Double check everything, cause I know I did and still a # was left.

candysprinkills · May 16, 2018, 1:45am

I had similar problems with my Pi 3 Model B+ on my Tevo Tornado. There are 2 things I figured out:

My SSID has to be broadcast. If its hidden the Pi is not found. (I use WPA2 encryption)
I have to follow a specific order in how power is applied. First Tornado is powered on, then Pi is powered on and then Pi USB is plugged into the Tornado control box.

If I don't do these things the Pi cannot be found. I was hoping to find a solution to these 2 things here. I prefer not to broadcast my ssid. Maybe either of these steps will help you find a solution to your issue.

supertaz · May 16, 2018, 6:53am

@candysprinkills I wish I had a 3B+ to try to replicate your issue with, but I don't. I will say that I am suspicious of you having to follow a particular power sequence in order to have your Pi be reachable on your WiFi network. I suspect you have a power issue in there somewhere, and possibly a noise issue as well. As for the SSID broadcast issue, I don't believe testing with a Pi 3 will help, as it uses a different chip than the + does. It may be a quirk of the chip, a misconfiguration, or a different issue that's masquerading as being related to unbroadcast SSID.

Food for thought: have you ensured you're giving your 3B+ enough power? They need more power than the 3B, IIRC from the hardware notes, and your power sequencing issue makes me believe you're underpowering it. Resolve your power or noise issue first, then see if the SSID broadcast quirk is still present.

candysprinkills · May 16, 2018, 3:30pm

Thanks for the info. It is powered appropriately according to the documentation provided with the Pi. The Pi isn't powered by the printer, it has its own dedicated power source. My intention is to connect it to the printer power supply with a dc converter but I wanted to get to the bottom of my current power on sequence before taking that next step. I haven't identified a noise issue in the connection as of yet but it may exist so I'll explore this a little more. The good news is once I perform the 2 steps, it works perfectly fine. Even the webcam functions as expected. I can live with the broadcast issue. But the power sequence leaves me only 2 possibilities; never turn the printer and Pi off (which I definitely don't like) or turn off and reconnect every time I want to use it (which defeats the whole purpose of having a WiFi connection). I'm sure I'll find a solution to it. I debated whether going with the Model B or B+ but I might just pick up a Model B and see if it works the same way.

OutsourcedGuru · May 16, 2018, 5:51pm

I described in this post how to troubleshoot an under-volt condition. Throttling in this condition might temporarily remove wi-fi power which would manifest itself like not connecting upon bootup.

It seems like Raspbian Stretch decided to ditch /etc/network/interfaces and in doing so, we may have some "interesting" behavior since we're now missing auto-hotplug for the wi-fi adapter. I discussed that here.

Short(er) version: in a hot or under-bolted Raspi, it might not connect to your wi-fi. After that initial hiccup of under-voltage during bootup, absence of auto-hotplug means that it just sits there stupidly.

candysprinkills · May 17, 2018, 1:03am

I've given them a read and I'm going to test out the workarounds. I certainly wouldn't have arrived at those solutions based off what I was seeing with my issues. So thank you for pointing me in the right direction. If I'm fully understanding all that I read, no firmware fix was released for this. Most of the references were late 2017 so I would think something would already be available...any idea why there isn't one?

supertaz · May 17, 2018, 1:56am

The B+ has only been out for a month or two, for one. Also, I'm not sure what firmware you're referring to here. This is commonly an issue when you think your power supply is sufficient, and it says it is sufficient, but you haven't actually tested the voltage under load. All too often, these supplies are wall wart type supplies, and their voltage drops under load. Since there are things like CPU throttling, SoC components that are turned off by undervoltage protection, and the WiFi connectivity is on a separate chip, which may have its own threshold for undervoltage protection, the best thing you can do is actually check voltages to eliminate it as a cause.

Spyder · May 17, 2018, 2:00am

Another odd thing I've found with the B+ is that, if you're under-voltage, the USB cam will still work, which sucks power from the pi, so it turns off the wifi instead of the USB

I danced around with that problem for quite some time before I figured it out

supertaz · May 17, 2018, 2:27am

I'm not sure that the WiFi is bus powered, or that it's actually actively turning it off. It could be, but it could also be a particularly voltage sensitive chip, as well. In the thread @OutsourcedGuru mentioned, the person responding said that their power adapter was designed for the RPi and was a 5V 2.5A supply. Since it's an older thread, I didn't reply there too, but perhaps I should, since the above is the supply's rating, not the actual working voltage under load. Far too many so-called RPi power supplies provide significantly less than 5V under less than a full load.

Also, I think the 3B+ specs say it requires a 3A supply now, but I could be wrong. Either way, I wouldn't be caught dead using a wall wart that's only rated 5V 2.5A for any RPi 3...I power my OctoPis off a charger brick that can handle 15W per port and doesn't sag on my scope (I also don't use the full wattage it is rated for, as I'm sure it'd sag eventually).

candysprinkills · May 17, 2018, 2:00pm

Power should not be my issue since my Pi is using a dedicated DC12v 3a PSU that is stepped down with a DC 12v/24v to 5v 3a converter. It will be connected to the 24v PSU in my Tevo Tornado the same way. I suppose the converter could be dropping the voltages. The PSU has been tested under load so I know that is fine. I'll haven't checked the output on the converter on Pi bootup so I'll test that.

OutsourcedGuru · May 17, 2018, 4:44pm

And we still don't know that this is the cause yet, it's just a good guess so far.

I did a fair amount of research into the poor quality of the Linux-based wi-fi adapter drivers in the area of power management after my HP laptop was exhibiting some... well... stupid and annoying behavior in this area. It boils down to:

the standard Ethernet drivers were rock solid
some of the wi-fi chipsets have drivers in the Linux/Debian world which simply cannot properly manage the myriad of power/sleep states for the Broadcom brand, for example

So again on the short version: that hotplug option for the wi-fi adapter is really crucial and Raspbian's recent removal of that as a default by moving to wpa_supplicant isn't necessarily a step in the right direction.

candysprinkills · May 17, 2018, 9:28pm

Power may be my issue afterall or my meter is bad (already tried new batteries). What is coming out of the converter is just under 5v. It must be just enough to under power the Pi at load. I can always use spare dc converters so I'm going to buy a new one (a lot cheaper than buying a new meter) and see if it makes a difference. I'll post an update once I try it out. I appreciate the help from all of you! There is no way I would have found it on my own.