Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telegraf throws Illegal Instruction on arm A9 system #4526

Closed
russorat opened this issue Aug 7, 2018 · 1 comment · Fixed by #4608
Closed

Telegraf throws Illegal Instruction on arm A9 system #4526

russorat opened this issue Aug 7, 2018 · 1 comment · Fixed by #4608
Labels
area/packaging bug unexpected problem or unintended behavior
Milestone

Comments

@russorat
Copy link
Contributor

russorat commented Aug 7, 2018

Relevant telegraf.conf:

N/A

System info:

arm A9 system
telegraf 1.7.2

Steps to reproduce:

  1. try to install and run telegraf_1.7.2-1_armel.deb on an arm A9 system
  2. notice the illegal instruction when trying to run telegraf

Expected behavior:

telegraf runs

Actual behavior:

illegal instruction thrown when starting

Additional info:

basically, you need to try to get to setting GOARM=5 in the build script but the logic is incorrect. If you try to build with --arch=armel, then on line https://github.com/influxdata/telegraf/blob/master/scripts/build.py#L455 the arch is overwritten to be arm and then the logic on line https://github.com/influxdata/telegraf/blob/master/scripts/build.py#L461 is never executed.

@russorat russorat added bug unexpected problem or unintended behavior area/agent labels Aug 7, 2018
@osingla
Copy link

osingla commented Aug 7, 2018

The issue is that the armel.deb image currently built using build.py with this command:
./scripts/build.py --platform=linux --arch=armel --version 1.7.2 --package
generate actually an armhf image (GOARM=6) instead of the expected armel (GOARM=5), and this image will require a cpu with floating point and a kernel built with armhf support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/packaging bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants