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
wrote:
> That does make sense and I do see a bunch of killed processes. I'm
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
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
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
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
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
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
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