Ali, Based on the log, it's all Go-specific thus far... unfortunately, Go has never officially supported kernels that old, and newer versions seem to be less and less likely to work at all. My only practical advice would be to (a) ensure you're using the latest point release of the kernel provided by RH or whomever, and (b) use the oldest version of Go supported by Heka, which is 1.3. And then pray ;)
Ali writes: > Hi, all. > > I'm trying to set up Heka on an older host and am running into problems. > I'm sure a lot of this is Go-specific, but since my goal is to end up with > a working Heka on this host I thought I'd see if anyone has other ideas. > > First, I tried running the packaged Heka 0.9.1 for amd64 and got an error > that GLIBC was too old. (Heka expects 2.7 and I have 2.5.) From what I > read, upgrading GLIBC will cause the box to "blow up". :-) > > Second, I tried building Heka on this box. I followed the instructions and > manually installed the dependencies. I finally got the part where I run > build.sh and got this: > > ***************************** > [root@janmsdlxwas04 heka]# source build.sh > -- Found Go: /opt/go/bin/go (found suitable version "1.4.2", required is > "1.3") > -- Found Git: /usr/bin/git > -- GeoIP.h was not found, GeoIP functionality will not be included in this > build. > -- Docker plugins enabled. > -- sphinx-build was not found, the documentation will not be generated. > -- Found Hg: /usr/bin/hg (found version "version 2.2.2") > Submodule 'docs/source/_themes/mozilla' ( > https://github.com/rafrombrc/mozilla-sphinx-theme.git) registered for path > 'docs/source/_themes/mozilla' > Cloning into 'docs/source/_themes/mozilla'... > remote: Counting objects: 87, done. > remote: Total 87 (delta 0), reused 0 (delta 0), pack-reused 87 > Unpacking objects: 100% (87/87), done. > Submodule path 'docs/source/_themes/mozilla': checked out > '6c054de5f69fbb3b24396ed77e64b879a8b8cbd2' > -- Configuring done > -- Generating done > -- Build files have been written to: /opt/heka/build > Scanning dependencies of target gogoprotobuf > [ 1%] Creating directories for 'gogoprotobuf' > [ 1%] Performing download step (git clone) for 'gogoprotobuf' > Cloning into 'gogoprotobuf'... > remote: Counting objects: 2260, done. > Receiving objects: 100% (2260/2260), 2.04 MiB | 1.70 MiB/s, done. > Resolving deltas: 100% (1548/1548), done. > Note: checking out '7008a93e68bf'. > > You are in 'detached HEAD' state. You can look around, make experimental > changes and commit them, and you can discard any commits you make in this > state without impacting any branches by performing another checkout. > > If you want to create a new branch to retain commits you create, you may > do so (now or later) by using -b with the checkout command again. Example: > > git checkout -b new_branch_name > > HEAD is now at 7008a93... blended unsafe and safe marshaler into one plugin > [ 2%] No patch step for 'gogoprotobuf' > [ 2%] No update step for 'gogoprotobuf' > [ 2%] No configure step for 'gogoprotobuf' > [ 3%] No build step for 'gogoprotobuf' > [ 3%] No install step for 'gogoprotobuf' > [ 4%] Completed 'gogoprotobuf' > FATAL: kernel too old > go build code.google.com/p/gogoprotobuf/proto: > /opt/go/pkg/tool/linux_amd64/6g: signal: segmentation fault > make[2]: *** [gogoprotobuf] Error 1 > make[1]: *** [CMakeFiles/gogoprotobuf.dir/all] Error 2 > make: *** [all] Error 2 > ***************************** > > Here's uname -a : > "Linux janmsdlxwas04 2.6.18-308.4.1.el5 #1 SMP Wed Mar 28 01:54:56 EDT 2012 > x86_64 x86_64 x86_64 GNU/Linux" > > Any ideas, or should I give up? (BTW, I tried building > https://github.com/google/protobuf and "make check" failed in many ways so > I didn't bother installing.) > > -Ali > _______________________________________________ > Heka mailing list > [email protected] > https://mail.mozilla.org/listinfo/heka -- _______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
