[HOME] [DOWNLOAD] [DOCS] [BLOG] [SUPPORT] [TIPS] [ISSUES] [Priority Support]

Build error "prepare-build-machine"


#1

Hello Whonix Team !!

When Im building latest Whonix from source have this main error
1100_prepare-build-machine detected!

git checkout 14.0.0.3.2-developers-only

sudo ~/Whonix/whonix_build --build --target qcow2 --flavor whonix-gateway – --build --arch amd64 --kernel linux-image-amd64 --headers linux-headers-amd64 --vmsize 2G

I know its related to Whonix already installed system name,but have this error all the time,even on clean reinstalled Debian system.

Any help would be appreciated
Thanks

############################################################
ERROR in ././build-steps.d/1100_prepare-build-machine detected!
anon_dist_build_version:
(whonix_build_error_counter: 1)
(benchmark: 00:00:05)
trap_signal_type_previous: unset
trap_signal_type_last : ERR
process_backtrace_result:
1: : /sbin/init
2: : /usr/bin/konsole
3: : /bin/bash
4: : sudo /home/c/Whonix/whonix_build --build --target qcow2 --flavor whonix-gateway – --build --arch amd64 --kernel linux-image-amd64 --headers linux-headers-amd64 --vmsize 2G
5: : /bin/bash /home/c/Whonix/whonix_build --build --target qcow2 --flavor whonix-gateway – --build --arch amd64 --kernel linux-image-amd64 --headers linux-headers-amd64 --vmsize 2G
6: : /bin/bash ././build-steps.d/1100_prepare-build-machine
function_trace_result:
main (line number: 403)
main (line number: 398)
build_machine_setup (line number: 287)
errorhandlergeneral (line number: 335)
errorhandlerprocessshared (line number: 170)
last_failed_bash_command: sudo -u “$user_name” git submodule update --init --recursive --jobs=200
last_failed_exit_code: 1
ERROR in ././build-steps.d/1100_prepare-build-machine detected!
############################################################

++ ‘[’ ERR = INT ‘]’
++ ‘[’ ERR = TERM ‘]’
++ ‘[’ ERR = ERR ‘]’
++ true ‘INFO: trap_signal_type_last: ERR, considering auto retry…’
++ ‘[’ ‘!’ 1 = 0 ‘]’
++ ‘[’ ‘’ = ‘’ ‘]’
++ whonix_build_auto_retry_counter=1
++ ‘[’ -n 1 ‘]’
++ ‘[’ -n 5 ‘]’
++ local first
++ read -r first _
++ ‘[’ sudo = error_ ‘]’
++ ‘[’ 1 -gt 1 ‘]’
++ true 'INFO: Auto retry attempt number: 1. Max retry attempts: 1 (–retry-max). Auto retry… '
++ whonix_build_auto_retry_counter=2
++ ‘[’ ‘!’ 5 = 0 ‘]’
++ true 'INFO: Waiting (–retry-wait) 5 seconds before auto retry… '
++ wait 18712
++ sleep 5
++ ignore_error=true
++ error_handler_do_retry=true
++ errorhandlerretry
++ ‘[’ ‘!’ ‘’ = ‘’ ‘]’
++ true ‘INFO: Skipping whonix_build_dispatch_before_retry (–retry-before), because empty, ok.’
++ true 'INFO: Retrying last_failed_bash_command…: sudo -u “$user_name” git submodule update --init --recursive --jobs=200 '
++ retry_last_failed_bash_command_exit_code=0
++ eval sudo -u ‘"$user_name"’ git submodule update --init --recursive --jobs=200
+++ sudo -u c git submodule update --init --recursive --jobs=200
usage: git submodule [–quiet] add [-b ] [-f|–force] [–name ] [–reference ] [–] []
or: git submodule [–quiet] status [–cached] [–recursive] [–] […]
or: git submodule [–quiet] init [–] […]
or: git submodule [–quiet] deinit [-f|–force] [–] …
or: git submodule [–quiet] update [–init] [–remote] [-N|–no-fetch] [-f|–force] [–checkout|–merge|–rebase] [–reference ] [–recursive] [–] […]
or: git submodule [–quiet] summary [–cached|–files] [–summary-limit ] [commit] [–] […]
or: git submodule [–quiet] foreach [–recursive]
or: git submodule [–quiet] sync [–recursive] [–] […]
++ retry_last_failed_bash_command_exit_code=1
++ true
++ ‘[’ 1 = 0 ‘]’
++ true 'INFO: Retry failed. exit code of last_failed_bash_command: 1 '
++ last_failed_exit_code=1
++ last_failed_bash_command=‘sudo -u “$user_name” git submodule update --init --recursive --jobs=200’
++ ‘[’ ‘!’ ‘’ = ‘’ ‘]’
++ true ‘INFO: Skipping whonix_build_dispatch_after_retry (–retry-after), because empty, ok.’
++ ‘[’ 1 = 0 ‘]’
++ errorhandlerprocessshared ‘NONE_(called_by_errorhandlerretry)’
++ last_script=././build-steps.d/1100_prepare-build-machine
++ trap_signal_type_previous=ERR
++ ‘[’ ERR = ‘’ ‘]’
++ trap_signal_type_last=‘NONE_(called_by_errorhandlerretry)’
++ whonix_build_error_counter=2
+++ benchmarktimeend 1488722545
++++ date +%s
+++ benchmarktimeend=1488722555
+++ benchmark_took_seconds=10
++++ convertsecs 10
++++ local h m s
++++ (( h=10/3600 ))
++++ true
++++ (( m=(10%3600)/60 ))
++++ true
++++ (( s=10%60 ))
++++ printf ‘%02d:%02d:%02d\n’ 0 0 10
+++ echo 00:00:10
++ benchmark_took_time=00:00:10
++ processbacktracefunction
++ true ‘INFO: BEGIN: processbacktracefunction’
++ ‘[’ -o xtrace ‘]’
++ set +x
++ true ‘INFO: END : processbacktracefunction’
++ functiontracefunction
++ true ‘INFO: BEGIN: functiontracefunction’
++ ‘[’ -o xtrace ‘]’
++ set +x
++ true ‘INFO: END : functiontracefunction’
++ output_cmd_set
++ ‘[’ -o xtrace ‘]’
++ output_cmd=true
++ true ‘
############################################################
ERROR in ././build-steps.d/1100_prepare-build-machine detected!
anon_dist_build_version:
(whonix_build_error_counter: 2)
(benchmark: 00:00:10)
trap_signal_type_previous: ERR
trap_signal_type_last : NONE_(called_by_errorhandlerretry)
process_backtrace_result:
1: : /sbin/init
2: : /usr/bin/konsole
3: : /bin/bash
4: : sudo /home/c/Whonix/whonix_build --build --target qcow2 --flavor whonix-gateway – --build --arch amd64 --kernel linux-image-amd64 --headers linux-headers-amd64 --vmsize 2G
5: : /bin/bash /home/c/Whonix/whonix_build --build --target qcow2 --flavor whonix-gateway – --build --arch amd64 --kernel linux-image-amd64 --headers linux-headers-amd64 --vmsize 2G
6: : /bin/bash ././build-steps.d/1100_prepare-build-machine
function_trace_result:
main (line number: 403)
main (line number: 398)
build_machine_setup (line number: 287)
errorhandlergeneral (line number: 335)
errorhandlerprocessshared (line number: 221)
errorhandlerretry (line number: 155)
errorhandlerprocessshared (line number: 170)
errorhandlerprocessshared (line number: 170)
errorhandlergeneral (line number: 335)
build_machine_setup (line number: 287)
main (line number: 398)
main (line number: 403)
last_failed_bash_command: sudo -u “$user_name” git submodule update --init --recursive --jobs=200
last_failed_exit_code: 1
ERROR in ././build-steps.d/1100_prepare-build-machine detected!
############################################################

++ ‘[’ ‘NONE_(called_by_errorhandlerretry)’ = INT ‘]’
++ ‘[’ ‘NONE_(called_by_errorhandlerretry)’ = TERM ‘]’
++ ‘[’ ‘NONE_(called_by_errorhandlerretry)’ = ERR ‘]’
++ ‘[’ ‘NONE_(called_by_errorhandlerretry)’ = ‘NONE_(called_by_errorhandlerretry)’ ‘]’
++ true ‘INFO: trap_signal_type_last: NONE_(called_by_errorhandlerretry), considering auto retry…’
++ ‘[’ ‘!’ 1 = 0 ‘]’
++ ‘[’ 2 = ‘’ ‘]’
++ ‘[’ -n 1 ‘]’
++ ‘[’ -n 5 ‘]’
++ local first
++ read -r first _
++ ‘[’ sudo = error_ ‘]’
++ ‘[’ 2 -gt 1 ‘]’
++ true 'INFO: Auto retried (–retry-max) already 1 times. No more auto retry. '
++ unset whonix_build_auto_retry_counter
++ true
++ ignore_error=false
++ answer=
++ ‘[’ ‘NONE_(called_by_errorhandlerretry)’ = ERR ‘]’
++ ‘[’ ‘NONE_(called_by_errorhandlerretry)’ = ‘NONE_(called_by_errorhandlerretry)’ ‘]’
++ true 'INFO: whonix_build_non_interactive: '
++ ‘[’ ‘’ = true ‘]’
++ ‘[’ -t 0 ‘]’
++ true ‘INFO: stdin connected to terminal, using interactive error handler.’
++ true ’ ERROR in ././build-steps.d/1100_prepare-build-machine detected!
Please have a look above (the block within ###…), note the command that failed, last_failed_exit_code and its output (further above).

  • Please enter c and press enter to ignore the error and continue building. (Recommended against!)
  • Please press r and enter to retry.
  • Please press s and enter to open an chroot interactive shell.
  • Please press a and enter to abort.’
    ++ read -p 'Answer? ’ answer

14.0.0.2.6 no internet connection
#2

You need to build on Debian stretch. (Has a newer version of git among
other things.)


#3

Thanks,
will try it,between is there a build option for grsec kernel or any new options?

I discovered that build options have changed in 14 from 13 previous version.


#4

VIN:

is there a build option for grsec kernel or any new options?

No.


#5

Thanks, Patrick


#6

Does not work,maybe its because 14 version uses Debian hidden services?


#7

Yes.


#8

Thanks


#9

Besides what exactly repositories is used and is it possible to add a repo before building steps?


#10

This isn’t documented yet but it’s possible.

Your options:

  • disable onion sources in build_sources folder inside Whonix source folder
  • need to edit *_current.list only (we don’t use frozen sources lists at the moment)
  • this will count as uncommitted change so you need to set the build parameter accordingly
  • torify apt-cacher-ng using torsocks and it as apt-cache
  • build behind a Tor transparent proxy such as Whonix-Gateway 13

#11

torsocks apt-cacher-ng method is now documented here:


#12

Im still dont have any success with build process,i would be gratefull if someone could check my build error:
https://pastebin.ca/3833107


#13

Just scroll up the log and see the apt-get errors. There are errors in your /etc/apt/sources.list. Fix them.

You mixed in a lot non-default Debian repositories. This may be okay for private builds (only used by you), but would be unacceptable for redistributable builds. Probably best to use a clean Debian VM to build Whonix.

Also note:

  • If you want to build Whonix 13, build on Debian jessie.
  • If you want to build Whonix 14, build on Debian stretch.
  • You apparently mixed with Debian sid, this may not work.

#14

Ok,i cleaned sources.list and sources.list.d files and leave only default official sources from Debian

https://wiki.debian.org/SourcesList

replaces jessie with stretch,i also tried on clean VM result was the same,im building Whonix 14 on stretch,what actually repos you recommend,the default ones?


#15

And if the problem really in sources.list so why there is the same issue on Whonix VM 14.0.0.2.0 ?

Patrick did you tried to build the latest 14.0.0.4.0,do you have success?


#16

Last version that I successfully build is 14.0.0.2.6. Others may not
build. A developers-only tag does not mean it can be successfully be build.

Note, 14 is the development version. If you cannot scroll up, read the
log and fix it, then you’re not a developer, and no support can be
provided. As a user you have to wait until 14 is released.


#17

Im half a user and half a developer,if i cant fix some things its because there is no information,i dont need step by step support,but at least some info about build process,just to say i dont have such problems earlier.

Even on this wiki page


there is no any info how to fix errors,only description of them.

I will not just waiting the new release,but tried until have success,between could you tell when exactly it comes?
Thanks.


#18

There is no fixed time.


#19

Ok,anyway i appreciate your work.