The issue was that there was a bug in the install.sh script from the
impala-setup/ repo that always assumed that the repo would reside in
/home/$user.
The Jenkins AMIs seem to have had a very old checkout (8 months old) at
/home/ubuntu/ which was being used for the GVOs. The Jenkins job would make
"from-scratch" is a misnomer: only the first build to run on a given node
is truly from-scratch, because running impala-setup takes effect
system-wide, and is run once, when the node is created.
For http://jenkins.impala.io:8080/job/ubuntu-14.04-from-scratch/1371/ , the
worker's build history sugg
Thanks Michael and Jim,
It looks like adding to bin/bootstrap_build.sh makes the ub14-build-only
job work fine, however, updating the impala-setup still doesn't seem to
work. I submitted a pull request that was merged by Dimitris here:
https://github.com/awleblang/impala-setup/commits/master
Also
Thanks Jim; I had forgotten bin/bootstrap_build.sh.
On Wed, May 24, 2017 at 3:14 PM, Jim Apple wrote:
> I'd recommend against #2 using the node setup to install Impala
> dependencies. The only reason it installs openjdk is that Jenkins
> needs Java to talk to it. All of the other Impala dependen
I'd recommend against #2 using the node setup to install Impala
dependencies. The only reason it installs openjdk is that Jenkins
needs Java to talk to it. All of the other Impala dependencies are
installed in the jobs themselves.
On Wed, May 24, 2017 at 3:11 PM, Michael Brown wrote:
>> Is there
> Is there a way to add a new dependency to these machines?
Our builds use two worker labels:
1. ubuntu14.04-c4.4xlarge-gp2
2. ub14-build-only
1 uses https://github.com/awleblang/impala-setup, and I think you should
add libffi to there. It's something you should do anyway so new users get
set up
They run https://github.com/awleblang/impala-setup. One of the jobs
run as part of this is
http://jenkins.impala.io:8080/view/Utility/job/ubuntu-14.04-build-only/
which runs ./bin/bootstrap_build.sh (in the Apache Impala repo), so
you'll need to update that file, too, I suspect.
On Wed, May 24,
I have a question regarding dependencies on the jenkins machines. (
http://jenkins.impala.io:8080/job/ubuntu-14.04-from-scratch/)
How do the Jenkins machines used to GVO have dependencies pre-packaged in
them? For eg., openssl, etc. Are they baked into an AMI?
I have a patch (https://gerrit.cloud
'sudo service ntp restart' WFM. Thanks!
On Wed, May 24, 2017 at 12:09 PM, Tim Armstrong wrote:
> I see that with some frequency when restarting my system.
>
> I usually manage to fix it with a non-scientific approach of running some
> combination of these commands until ntp-wait works:
>
> sudo s
Yes it's also possible that my solution "works" because it distracts me for
long enough for NTP to sync :)
On Wed, May 24, 2017 at 12:20 PM, Zachary Amsden
wrote:
> This is similar to what I hit with NTP the other day after a restart. I
> tried a number of things, and I think the only thing tha
This is similar to what I hit with NTP the other day after a restart. I
tried a number of things, and I think the only thing that worked was
waiting for NTP to sync. Pitfalls: ntpdate requires a host on the command
line, and doesn't read the configuration file.
There was some circumstantial evid
I see that with some frequency when restarting my system.
I usually manage to fix it with a non-scientific approach of running some
combination of these commands until ntp-wait works:
sudo service ntp restart
sudo ntpdate -s ntp.ubuntu.com
ntp-wait -v
On Wed, May 24, 2017 at 11:33 AM, Jim Apple
testdata/cluster/admin
calls ntp-wait which returns an error:
"ntpq: read: Connection refuseLeap status not avalaible"
Has anyone seen this? There are 0 Google hits for refuseLeap and the
string is not present in my repository or my /etc/.
13 matches
Mail list logo