It was indeed resource issue. I move to AWS and I've successfully bootstrapped an Impala dev env.
Thanks for the help, team. Appreciate it! On Fri, Sep 8, 2017 at 2:13 PM, Manaswini Maharana <[email protected]> wrote: > That does make sense and I do see a bunch of killed processes. I'm going > to increase the available memory and give it a try > > dmesg | egrep -i 'killed process' > > [297232.422990] Killed process 375 (cc1plus) total-vm:883640kB, > anon-rss:538308kB, file-rss:276kB, shmem-rss:0kB > > [298364.710758] Killed process 3696 (cc1plus) total-vm:876052kB, > anon-rss:635320kB, file-rss:136kB, shmem-rss:0kB > > [298376.012778] Killed process 3684 (cc1plus) total-vm:864812kB, > anon-rss:379416kB, file-rss:1892kB, shmem-rss:0kB > > [298411.700382] Killed process 3706 (cc1plus) total-vm:893552kB, > anon-rss:384688kB, file-rss:4412kB, shmem-rss:0kB > > [298455.166373] Killed process 3755 (cc1plus) total-vm:1130268kB, > anon-rss:663688kB, file-rss:1884kB, shmem-rss:0kB > > [309264.984740] Killed process 6931 (cc1plus) total-vm:949988kB, > anon-rss:346136kB, file-rss:828kB, shmem-rss:0kB > > [309304.546262] Killed process 7074 (cc1plus) total-vm:1033296kB, > anon-rss:454552kB, file-rss:2048kB, shmem-rss:0kB > > [309360.538354] Killed process 7414 (cc1plus) total-vm:1008084kB, > anon-rss:523108kB, file-rss:704kB, shmem-rss:0kB > > [309386.679456] Killed process 7563 (cc1plus) total-vm:1138576kB, > anon-rss:674876kB, file-rss:2092kB, shmem-rss:0kB > > [310031.942027] Killed process 10059 (cc1plus) total-vm:776956kB, > anon-rss:472768kB, file-rss:2980kB, shmem-rss:0kB > > [310051.011532] Killed process 10061 (cc1plus) total-vm:833576kB, > anon-rss:463844kB, file-rss:1740kB, shmem-rss:0kB > > [310099.311829] Killed process 10168 (cc1plus) total-vm:947264kB, > anon-rss:630504kB, file-rss:3176kB, shmem-rss:0kB > > [310143.369177] Killed process 10258 (cc1plus) total-vm:901536kB, > anon-rss:638176kB, file-rss:1072kB, shmem-rss:0kB > > On Fri, Sep 8, 2017 at 1:01 PM, Henry Robinson <[email protected]> wrote: > >> Yeah, it's likely you're out of memory. These messages: >> >> "Please submit a full bug report,* >> >> *with preprocessed source if appropriate.* >> >> *Please include the complete backtrace with any bug report.*" >> >> come from gcc failing with an internal error, which in my experience is >> almost always the OOM killer getting involved. You could try building with >> less parallelism, or increasing the available memory. You can check >> something like 'dmesg | egrep -i 'killed process' to check the OOM >> killer's >> activity. >> >> On 8 September 2017 at 10:46, Philip Zeyliger <[email protected]> >> wrote: >> >> > It's a little bit of a shot in the dark, but your CPU/memory ratio may >> be >> > significantly different than what most folks are using. I've seen gcc >> and >> > friends fail kind of opaquely when you're out of memory. (Or out of disk >> > space, for that matter.) >> > >> > I've been personally following the Docker instructions successfully on >> an >> > Ubuntu16 host in Google Compute Engine. I've run into >> > https://issues.apache.org/jira/browse/IMPALA-5765, but not reliably. >> > >> > -- Philip >> > >> > On Fri, Sep 8, 2017 at 9:44 AM, Jim Apple <[email protected]> wrote: >> > >> > > Hm. Haven't seen this before. Does "MBP" stand for "Mac Book Pro"? >> > > This could be an issue with the Docker instructions in >> > > bootstrap_development.sh not accounting for some transparency in >> > > Docker exposing the host to the container. >> > > >> > > If possible, can you send the full stdout and stderr from that last >> > > command? >> > > >> > > On Fri, Sep 8, 2017 at 8:57 AM, Manaswini Maharana >> > > <[email protected]> wrote: >> > > > Here you go - >> > > > >> > > > >> > > > 1. The command you used to start the docker container >> > > > mmaharana-MBP:~ mmaharana$ *docker pull ubuntu:16.04* >> > > > mmaharana-MBP:~ mmaharana$ *docker run --privileged --interactive >> --tty >> > > > --name impala-dev ubuntu:16.04 bash* >> > > > >> > > > 2. The output of gcc --version inside your docker container >> > > > impdev@ea385187b032:~$ *gcc --version* >> > > > *gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609* >> > > > *Copyright (C) 2015 Free Software Foundation, Inc.* >> > > > *This is free software; see the source for copying conditions. >> There >> > is >> > > NO* >> > > > *warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR >> > > > PURPOSE.* >> > > > >> > > > >> > > > 3. The output of lsb_release -a both in the host and inside the >> docker >> > > > container >> > > > On Host: >> > > > mmaharana-MBP:~ mmaharana$* lsb_release -a* >> > > > *-bash: lsb_release: command not found* >> > > > >> > > > On Container: >> > > > *impdev@ea385187b032:~$ lsb_release -a * >> > > > *No LSB modules are available.* >> > > > *Distributor ID: Ubuntu* >> > > > *Description: Ubuntu 16.04.3 LTS* >> > > > *Release: 16.04* >> > > > *Codename: xenial* >> > > > >> > > > 4. The commands you ran inside the container >> > > > root@ea385187b032:/# *apt-get update* >> > > > root@ea385187b032:/# *apt-get install sudo* >> > > > root@ea385187b032:/# *adduser --disabled-password --gecos '' >> impdev* >> > > > root@ea385187b032:/# *echo 'impdev ALL=(ALL) NOPASSWD:ALL' >> >> > > /etc/sudoers* >> > > > root@ea385187b032:/#* su - impdev* >> > > > impdev@ea385187b032:~$ *sudo apt-get --yes install git* >> > > > impdev@ea385187b032:~$* git clone >> > > > https://git-wip-us.apache.org/repos/asf/incubator-impala.git >> > > > <https://git-wip-us.apache.org/repos/asf/incubator-impala.git> >> > ~/Impala* >> > > > impdev@ea385187b032:~$ *source ~/Impala/bin/bootstrap_develop >> ment.sh* >> > > > >> > > > >> > > > Thanks! >> > > > Mansi >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > On Fri, Sep 8, 2017 at 10:11 AM, Jim Apple <[email protected]> >> > wrote: >> > > > >> > > >> Can you provide: >> > > >> >> > > >> 1. The command you used to start the docker container >> > > >> >> > > >> 2. The output of gcc --version inside your docker container >> > > >> >> > > >> 3. The output of lsb_release -a both in the host and inside the >> docker >> > > >> container >> > > >> >> > > >> 4. The commands you ran inside the container >> > > >> >> > > >> Thank you! >> > > >> >> > > >> On Fri, Sep 8, 2017 at 7:58 AM, Manaswini Maharana >> > > >> <[email protected]> wrote: >> > > >> > Hello team, >> > > >> > >> > > >> > I'm trying to setup docker for development and encountering the >> > below >> > > >> issue >> > > >> > during bootstrap_development.sh sourcing. Any pointers on how to >> > > resolve >> > > >> > this? If you need more stack trace to backtrack or any other >> kind of >> > > >> > information to debug let me know. >> > > >> > >> > > >> > >> > > >> > *Please submit a full bug report,* >> > > >> > >> > > >> > *with preprocessed source if appropriate.* >> > > >> > >> > > >> > *Please include the complete backtrace with any bug report.* >> > > >> > >> > > >> > *See <http://gcc.gnu.org/bugs.html <http://gcc.gnu.org/bugs.html >> >> >> > > for >> > > >> > instructions.* >> > > >> > >> > > >> > *be/src/service/CMakeFiles/Service.dir/build.make:123: recipe >> for >> > > target >> > > >> > 'be/src/service/CMakeFiles/Service.dir/impala-server.cc.o' >> failed* >> > > >> > >> > > >> > *make[2]: *** [be/src/service/CMakeFiles/ >> > > Service.dir/impala-server.cc.o] >> > > >> > Error 4* >> > > >> > >> > > >> > *CMakeFiles/Makefile2:5694: recipe for target >> > > >> > 'be/src/service/CMakeFiles/Service.dir/all' failed* >> > > >> > >> > > >> > *make[1]: *** [be/src/service/CMakeFiles/Service.dir/all] Error >> 2* >> > > >> > >> > > >> > *Linking CXX static library ../../build/debug/testutil/ >> > libTestUtil.a* >> > > >> > >> > > >> > *[ 23%] Built target TestUtil* >> > > >> > >> > > >> > *Makefile:85: recipe for target 'all' failed* >> > > >> > >> > > >> > *make: *** [all] Error 2* >> > > >> > >> > > >> > *Error in /home/impdev/Impala/bin/make_impala.sh at line 178: >> > > >> ${MAKE_CMD} >> > > >> > ${MAKE_ARGS}* >> > > >> > >> > > >> > Thanks! >> > > >> > >> > > >> > Mansi >> > > >> >> > > >> > >> > >
