@Phuc Duong hi! could you check you don’t have a space after each line in the flagfile? If you check the error closely each value seems to have been read with a space in it.
04/14/2020, 5:54 PM
Does windows flag files care about EOL? Maybe Linux vs windows?
04/14/2020, 6:02 PM
No that shouldn't be the issue; I've reproduced it exactly by having a space at the end of each line in the flagfile
04/14/2020, 7:37 PM
maybe its not a space - but a control character, have you treid changing eol?
04/14/2020, 7:58 PM
I did try to change the eol and do this test, no issue there, so only @Phuc Duong can tell us when he gets to it 🙂
I mean it's a common mistake when converting a series of flags from command line to file to leave a space at the end, since they originally had it 🙂.
i did that countless times in other cases when separating long lines.
I had that weird quote issue i wrote on his other thread - mine could not run like how they have it
04/15/2020, 3:10 AM
@Stefano Bonicatti Thanks bro. You are right. After I checked the space after each line then I can start osquery service without error but Fleet server still marks this windows's status is offline. I waited it to change the status to online in 2 mins but nothing changed. So I run the command again and the status of windows machine changes to online immediately. How can we fix this?
@Stefano Bonicatti Could you please help me again? Thanks