Telegraf for ARM systems? (e.g. Netgate SG-3100).
-
Is there any update on getting Telegraf working on Netgate's ARM devices?
Is this something that will be fixed in pfSense 2.5?
Or will it be fixed in pfSense 2.4.x?
-
It requires a native ARMv6/7 build environment for the GO Telegraf client and currently we are cross-building those packages.
There are now a number of things that will require native builders and work is underway to add those, initially for ARM64.There is no ETA though as far as I know.
Steve
-
Is there any update on this please? =)
Will we see packages like Telegraf working again on Netgate ARM devices soon?
-
I recently upgraded one of our SG-3100 units to pfSense 2.5.0 (Build from January 1, 2019).
However, Telegraf still does not appear to be available in the list of packages.
Is there any idea of when it might be available for ARM-based Netgate devices again?
-
Our ARM64 build server is now up and running but it looks like it's not yet building Telegraf/Rust etc. I'll see if there's a reason for that.
No news on ARMv6/7 though.Steve
-
Any update on whether Telegraf packages are available for Netgate ARM devices (e.g. SG-3100) yet?
-
Telegraf is not available for armv6 (SG-3100) for the same reason. It requires a native build because of the language chosen to write it in. We do not currently have any armv6 build hardware so cannot build the package.
Steve
-
Ah ok - so the build pipeline for Rust/Golang is still not working for the SG-1100/SG-3100 etc, right?
Do you know if this is likely to be fixed in the future?
It would be a real bummer if all the SG-1100 and SG-3100 units out there were no longer able to run anything written in Rust or Golang
=(. -
The SG-1100 is aarch64 and we do have build hardware for that which is why it has Suricata 5.
https://twitter.com/NetgateUSA/status/1179190143225417735I believe that should allow Telegraph there unless there is another obstacle I'm unaware of (which I might be).
Steve
-
Aha got it - but the SG-3100 is ARMv6/7, right, so that is still pending?
Basically, we have around 10 x SG-3100's - and we'd like to get Telegraf (Golang), Suricata (Rust) etc. all working on it.
Do you know if getting working build support for SG-3100 is on the roadmap?
Or if the SG-3100 isn't being supported anymore - is there a replacement device on the roadmap? (Although it'd be a bummer if the SG-3100 is being EOLed, since we bought them only last year).
-
Telegraf is now available on the SG-1100. Please test it if you can.
We are working on what we can do on armv6.
Steve
-
I just installed the package on my SG-1100 and in the System Log I get
Apr 1 00:30:46 kernel pid 72858 (telegraf), jid 0, uid 0: exited on signal 4 (core dumped)
and when I try and run telegraf from the console I get
Illegal instruction (core dumped)
-
Thanks for the report, we are investigating.
Steve
-
I have a SG-1100 and getting the same results, signal 4 (core dump).
-
It is still being looked at but is much lower priority than some other things right now.
-
I can confirm it compiles and runs on SG-3100 with the following flags when using telegraf's master and go 1.14.1:
CGO_ENABLED=0 GOOS=freebsd GOARCH=arm GOARM=7 go build ./cmd/telegraf
I'm downloading the ports repository now to try and make the package.
-
@stephenw10 I installed the latest Telegraf 0.9_3 package on my SG-1100 today. I'm on pfSense 2.4.5. When I try to start the service I get a continuous stream of core dumps in the system log.
Apr 19 19:36:18 kernel pid 29205 (telegraf), jid 0, uid 0: exited on signal 4 (core dumped)
Apr 19 19:36:21 kernel pid 29379 (telegraf), jid 0, uid 0: exited on signal 4 (core dumped)
Apr 19 19:36:25 kernel pid 29647 (telegraf), jid 0, uid 0: exited on signal 4 (core dumped) -
Thanks for the feedback.
We are are aware of the problems and are looking at it. We are very busy right now though so no ETA I'm afraid.Steve
-
@stephenw10 Is there anyway to assist in the progress? I've done lot's of compiling on Linux systems, never on a BSD system, but should be similar after learning the file structure and lib locations.
-
Updated to the 0.9_4 package version, still no joy.
