How to update to the latest Telegraf version
-
Just in case anyone is have any issues:
A good read below:
https://www.freshports.org/net-mgmt/telegraf/#historypfsense 24.03_1 - Telegraf freebsd-15
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/telegraf-1.32.1.pkg
pfsense 2.7.2 - Telegraf freebsd-14
pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/telegraf-1.32.0.pkg
-
@rocket said in How to update to the latest Telegraf version:
Just in case anyone is have any issues:
A good read below:
https://www.freshports.org/net-mgmt/telegraf/#historypfsense 24.03_1 - Telegraf freebsd-15
pkg add -f https://pkg.freebsd.org/FreeBSD:15:amd64/latest/All/telegraf-1.32.1.pkg
pfsense 2.7.2 - Telegraf freebsd-14
pkg add -f https://pkg.freebsd.org/FreeBSD:14:amd64/latest/All/telegraf-1.32.0.pkg
This is an excellent way to completely break your pfSense installation. It is a complete random toss of the dice as to whether a given package install or update from an outside repo will succeed or flame out spectacularly.
The regular FreeBSD public repositories can contain versions of shared library dependencies that are incompatible with the pfSense core product. That can break pfSense badly up to and including making it unbootable if these incompatible shared libaries are pulled in as part of a package installation from a non-pfSense package repository.
There have been a number of posts to the forum in the past advising against installing packages from any repository other than the officially sanctioned pfSense ones (CE, DEVEL, or Plus).
Not saying it can't sometimes work, but be warned you are playing with fire when installing packages on pfSense from non-Netgate repos.
