Telegraf is not starting

KxmischerLasse commented 1 year ago

Relevant telegraf.conf

Default config

Logs from Telegraf

× telegraf.service - Telegraf
     Loaded: loaded (/lib/systemd/system/telegraf.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Sun 2023-08-13 13:00:30 CEST; 37min ago
       Docs: https://github.com/influxdata/telegraf
   Main PID: 681 (code=exited, status=1/FAILURE)
        CPU: 131ms

Aug 13 13:00:30 HOSTNAME systemd[1]: telegraf.service: Scheduled restart job, restart counter is at 5.
Aug 13 13:00:30 HOSTNAME systemd[1]: Stopped telegraf.service - Telegraf.
Aug 13 13:00:30 HOSTNAME systemd[1]: telegraf.service: Start request repeated too quickly.
Aug 13 13:00:30 HOSTNAME systemd[1]: telegraf.service: Failed with result 'exit-code'.
Aug 13 13:00:30 HOSTNAME systemd[1]: Failed to start telegraf.service - Telegraf.

System info

Telegraf 1.27.3, Debian 12 and Ubuntu 22.04

Docker

No response

Steps to reproduce

1.Install Telegraf on Debian 12 or Ubuntu 22.04

run systemctl status telegraf

Expected behavior

Telegraf should start

Actual behavior

telegraf doesnt start

Additional info

i have the issue on debian 12 and ubuntu 22.04

powersj commented 1 year ago

Hi,

Default config

The default config does not come with an output configured. So it will not start. That is up to you to configure.

Logs from Telegraf

These are not the logs from telegraf ;) You provided the output of systemctl status telegraf. What you should look at, are the actual logs via: journalctl --no-pager --unit telegraf.

Closing this as not starting by default is the correct behavior.

Omkar8284 commented 2 months ago

ul 25 23:05:32 omkar systemd[1]: telegraf.service: Failed with result 'exit-code'. Jul 25 23:05:32 omkar systemd[1]: Failed to start Telegraf. Jul 25 23:05:32 omkar systemd[1]: telegraf.service: Scheduled restart job, restart counter is at 4. Jul 25 23:05:32 omkar systemd[1]: Stopped Telegraf. Jul 25 23:05:32 omkar systemd[1]: Starting Telegraf... Jul 25 23:05:32 omkar telegraf[134147]: time="2024-07-25T23:05:32+05:30" level=warning msg="DBUS_SESSION_BUS_ADDRESS envvar looks to be not set, this can lead to runaway dbus-daemon processes. To avoid this, set envvar DBUS_SESSION_BUS_ADDRESS=$XDG_RUNTIME_DIR/bus (if it exists) or DBUS_SESSION_BUS_ADDRESS=/dev/null." func="gosnowflake.(*defaultLogger).Warn" file="log.go:244" Jul 25 23:05:32 omkar telegraf[134147]: 2024-07-25T17:35:32Z I! Loading config: /etc/telegraf/telegraf.conf Jul 25 23:05:32 omkar telegraf[134147]: 2024-07-25T17:35:32Z I! Loading config: /etc/telegraf/telegraf.d/system.conf Jul 25 23:05:32 omkar telegraf[134147]: 2024-07-25T17:35:32Z E! error loading config file /etc/telegraf/telegraf.d/system.conf: error parsing data: line 128: invalid TOML syntax Jul 25 23:05:32 omkar systemd[1]: telegraf.service: Main process exited, code=exited, status=1/FAILURE Jul 25 23:05:32 omkar systemd[1]: telegraf.service: Failed with result 'exit-code'. Jul 25 23:05:32 omkar systemd[1]: Failed to start Telegraf. Jul 25 23:05:32 omkar systemd[1]: telegraf.service: Scheduled restart job, restart counter is at 5. Jul 25 23:05:32 omkar systemd[1]: Stopped Telegraf. Jul 25 23:05:32 omkar systemd[1]: telegraf.service: Start request repeated too quickly. Jul 25 23:05:32 omkar systemd[1]: telegraf.service: Failed with result 'exit-code'. Jul 25 23:05:32 omkar systemd[1]: Failed to start Telegraf.

influxdata / telegraf