** Description changed:
- [Description]
+ [Impact]
The latest ESM release of telegraf on Jammy has caused the application
to crash to start due to the version string not meeting the semver
standard anymore.
The application shows the following logs on start before crashing:
2026-02-11T07:40:36Z I! Starting Telegraf 1.21.4+ds1-0ubuntu2+esm2
panic: failed to validate metadata: ds1-0ubuntu2+esm2 is not a valid semver
identifier
goroutine 1 [running]:
github.com/coreos/go-semver/semver.Must(...)
-
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/vendor/github.com/coreos/go-semver/semver/semver.go:65
+
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/vendor/github.com/coreos/go-semver/semver/semver.go:65
github.com/coreos/go-semver/semver.New({0x59a46897b3a0, 0x0})
-
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/vendor/github.com/coreos/go-semver/semver/semver.go:49
+0x45
+
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/vendor/github.com/coreos/go-semver/semver/semver.go:49
+0x45
github.com/influxdata/telegraf/config.NewConfig()
- /build/telegraf-k12Ia1/telegraf-1.21.4+ds1/config/config.go:118 +0x2d3
+ /build/telegraf-k12Ia1/telegraf-1.21.4+ds1/config/config.go:118 +0x2d3
main.runAgent({0x59a46c00e408, 0xc0001e4200}, {0x59a46ecb9810, 0x0, 0x0},
{0x59a46ecb9810, 0x0, 0x0})
-
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf.go:201 +0xea
+
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf.go:201 +0xea
main.reloadLoop({0x59a46ecb9810, 0x0, 0x0}, {0x59a46ecb9810, 0x0, 0x0})
-
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf.go:147 +0x28a
+
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf.go:147 +0x28a
main.run(...)
-
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf_posix.go:8
+
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf_posix.go:8
main.main()
-
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf.go:485 +0xa9a
+
/build/telegraf-k12Ia1/telegraf-1.21.4+ds1/cmd/telegraf/telegraf.go:485 +0xa9a
telegraf.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
The issue does not affect Jammy outside of ESM.
[Test Case]
1- Install telegraf on Jammy from ESM. Make sure the version ends in "+esmX"
where X can be any number. The current ESM version is 1.21.4+ds1-0ubuntu2+esm2.
2- After installing it, make sure the telegraf service starts: $ systemctl
status telegraf.
3- if the "Active" field is "failed" than the application is still crashing
on startup. If the Active field is "active (running)" than the application is
starting as expected.
[Where problems could occur]
* Since telegraf makes use of its own version number to verify if any
plugins are deprecated or close to being deprecated, problems might
arise with the plugin deprecation warning and error system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2141508
Title:
Telegraf crashes on startup due to esm release not meeting semver
standard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2141508/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
