Starting Telegraf Agent as service with invalid statefile does not produce error message about telegraf HOT 6 CLOSED

OK, thank you for that information! So we can live very good with this logging "anomaly" and with the prospect of refactoring logging in the future.

from telegraf.

Hi,

does not produce correct error message

To clarify, it isn't that it is the wrong error message, it is that you are not seeing the final error message when running Telegraf as a service on windows and logging to a file?

from telegraf.

Yes thats exactly what I mean: You see this correct error message only when you start Telegraf manually.
When Telegraf is started as service no error message is produced (inside logfile).

Scenario: Statefile get currupted during Telegraf shutdown/crash and server reboots. Telegraf tries to start as service with corrupt statefile but cant. It does not log this usefull log message. You have to manually connect to server to start Telegraf on command line to see this eror message.

from telegraf.

@1tft can you please check the Windows event-log for any errors!?

from telegraf.

Yes, Windows event-log includes this error: "[telegraf] Error running agent: unmarshalling states failed: invalid character 'Z' looking for beginning of value"
Source: telegraf
Event ID: 100

Regarding linux I have to correct my inital statement: I can see log message "[telegraf] Error running agent: unmarshalling states failed: invalid character 'Z' looking for beginning of value" inside Telegraf log and not inside journal etc..

So we have to "live" with this "inconsistency"?

from telegraf.

The issue is the "early" logging in Telegraf currently isn't consistent over platforms as the timing to switch outputs differs. I'm currently working on revamping the logging and might be able to provide a more consistent way of "early logging"...

At least the error message is not dropped on the floor, that's good news for me. ;-)

from telegraf.