Telegraf for ARM systems? (e.g. Netgate SG-3100).



  • Hi,

    I have quite a few SG-3100 unit we bought, and I'd love to get Telegraf working on them.

    There was this Github PR before:

    https://github.com/pfsense/FreeBSD-ports/pull/627

    However, I believe that might have been blocked on this FreeBSD bug regarding Go on ARM. However, that bug is fixed.

    Then I noticed this commit that seems to enable ARMv7 anyhow.

    But when I refreshed packages on my SG-3100, Telegraf doesn't show up.

    Is there something I can do to make it show up? Or are we still waiting on something that pushes from pfsense/FreeBSD-ports to actual packages?


  • Netgate Administrator

    Like @rbgarga said there in the pull request there are additional problems building it using our current builder setup. It will require further changes.

    Steve



  • Is it possible to get an idea from Netgate on how difficult it is to fix the Telegraf issues on ARM boxes?

    We have quite a few XG-7100's deployed - but we also use SG-3100's for many of our lab rooms.

    This is causing issues, as we can't pull the metrics we need via Telegraf.

    We do have a few spare Qotom Intel i5 boxes from before we started buying up Netgate gear, which I've been asked to in the meantime. Cheap and will do for now.

    I'm keen to stick with Netgate gear if possible, and support the project - but there doesn't seem to be anything in the sub $500 price range that would actually work with Telegraf.

    Is there anything else you can suggest to get Telegraf working on our ARM-based SG-3100's?

    Thank you!



  • 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?


  • Netgate Administrator

    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?


  • Netgate Administrator

    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?


  • Netgate Administrator

    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 ☹ =(.


  • Netgate Administrator

    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/1179190143225417735

    I 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).


  • Netgate Administrator

    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)


  • Netgate Administrator

    Thanks for the report, we are investigating.

    Steve



  • I have a SG-1100 and getting the same results, signal 4 (core dump).


  • Netgate Administrator

    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)


  • Netgate Administrator

    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.



  • i am also waiting for this official release



  • We were going to buy a batch of the 3100's for home users and offices, but knowing it won't support Telegraf is a deal breaker for us and we may have to look at other options now.



  • While we wait for the official plugin. Is there any community documentation I can follow to get telegraf up and running on a SG-3100 without going via the official plugin system?



  • I believe @kamushadenes was trying to make a package before (https://forum.netgate.com/post/904312), I wonder how that went.

    That being said - it would be awesome if the Netgate team was able to get this working again .
    I'm in the same boat as @g0nz0uk - looking to get a couple more SG-3100's - but I want to make sure it's still a support platform.

    Is there a replacement for the SG-3100 (similar pricepoint and capacity) coming out? I'd rather get whatever you have new than buy the SG-3100 and find out it's deprecated.



  • Hi everyone. So the last post in this thread got me thinking. I have a raspberry pi 3b+ laying around it has a A53 (ARMv8) 64-bit processor. I'm wondering if I install FreeBSD on the Pi and then run a clean build of telegraf will it port over? Does anyone see any reason why this wouldn't work? This may get us running on the SG-1100. I'd really like to hear your thoughts before I attempt this.



  • I’ve looked only a little for the FreeBSD source for telegraf with the intention of compiling directly on the SG-1100 then making the binary available for others. Didn’t think about a Pi, or about 7 other SBCs laying around. Not sure how a cross compile on FreeBSD would look, but could be interesting.


  • Netgate Administrator

    I seem to recall suggesting that, or something similar, to our developers when we first saw this issue and it was dismissed as impractical due to the time it would require.
    But if you've got the device and the time then give it a whirl.

    Cross compiling is problem for the dependencies here. I believe GO will not compile using our current setup which is the root of the problem here.

    Steve



  • @stephenw10 Honestly this may be something that, if the community could help, may provide beneficial to everyone. I can go out and grab the source and compile it myself, but that doesn't really help the community as a whole unless everyone compiles it themselves.
    Sounds like there are a couple of us willing to throw our hats in the ring to help in some way with this.



  • I'd just like to add one more vote for getting Telegraf running on the SG-1100



  • Well, I upgraded my SG-1100 to 2.4.5 p1 and out of the blue Telegraf started working. I didn't even notice it at first until I was looking at my Grafana dashboard and saw more than one pfSense host reporting data. So not sure what changed with the p1 release, but that seems to have been the puzzle piece to getting this working.



  • This is interesting! I wonder if others are also working after the upgrade.



  • I experienced the same thing, Telegraf seems to work on my SG-1100 since the 2.4.5 p1 update.



  • is it back on the package manager? i cant seem to find it anymore, i also upgraded to p1



  • The SG-3100 is a different architecture than the SG-1100. Hence why telegraf is available for some (SG-1100) users and not the rest of. Note: the thread is about Telegraf on ARM devices including the SG-3100, my understanding is that Go complied cleanly on the SG-1100 so they can build for that. This leave those of us who paid for a beefier system from Netgate in a bind. If I'd have went with a cheaper Intel Potectli or Qotom, I'd have x86_64 architecture and the ability to run just about anything, while saving money. I can't see a reason to buy the SG-3100 going forward, Telegraf being just one example of how this architecture is a second-class citizen for Netgate.



  • I wouldn't say Netgate is to blame in this particular instance. The A57 in the SG-3100 is a newer, more advanced processor than the A9 that is in the SG-1100, so there's going to be some compiler challenges there.

    But more so, this whole ARM journey fundamentally is a FreeBSD problem of being way behind the bar in this area. Until using pfSense and FreeNAS, I wouldn't touch BSD or any variant with a 10 foot pole, and outside of these two uses I still won't as there's jsut too many quarks with it in my humble opinion.

    Anyway, Go is being distributed separately from anything Netgate has control over, so can't blame them for those shortcomings.

    Now with that, I have my little SG-1100 which does not impress me in the least, and I have my larger Protectcli device, the FW2 to be exact, and going forward I will stay with my instincts and not go with the ARM based platforms for running freeBSD on to avoid the quarks. I will continue to have my assortment of ARM based systems mind you, just running Linux instead.

    I do feel that the release of the ARM hardware for pfSense was a mistake on Netgate's part, it just created very bad feedback for them unfortunately without more support and maturity on the part of the freeBSD foundation.



  • @jlw52761 said in Telegraf for ARM systems? (e.g. Netgate SG-3100).:

    I wouldn't say Netgate is to blame in this particular instance. The A57 in the SG-3100 is a newer, more advanced processor than the A9 that is in the SG-1100, so there's going to be some compiler challenges there.

    But more so, this whole ARM journey fundamentally is a FreeBSD problem of being way behind the bar in this area. Until using pfSense and FreeNAS, I wouldn't touch BSD or any variant with a 10 foot pole, and outside of these two uses I still won't as there's jsut too many quarks with it in my humble opinion.

    Anyway, Go is being distributed separately from anything Netgate has control over, so can't blame them for those shortcomings.

    Now with that, I have my little SG-1100 which does not impress me in the least, and I have my larger Protectcli device, the FW2 to be exact, and going forward I will stay with my instincts and not go with the ARM based platforms for running freeBSD on to avoid the quarks. I will continue to have my assortment of ARM based systems mind you, just running Linux instead.

    I do feel that the release of the ARM hardware for pfSense was a mistake on Netgate's part, it just created very bad feedback for them unfortunately without more support and maturity on the part of the freeBSD foundation.

    The funny thing is... the package from github has worked on my sg3100 since being released. Even after updates.



  • Hi,

    Which package from Github is this please?

    How did you set it up?

    Thanks,
    Victor


Log in to reply