Telegraf for ARM systems? (e.g. Netgate SG-3100).
-
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.
-
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.
-
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.
