Forum Discussion
Lewis_Beard
2 months agoExpert
I just went to several other collectors, both Windows and Linux, all at 36.000, and I can't reproduce your error. At least one was a new deploy, but most of the others are all upgrades.
I cant reproduce the error, my !tlist works fine. Not sure if that helps in any way, but maybe it will.
- Anonymous2 months ago
I wonder if it's something i have customized in the config. The only thing that would be on all my collectors is:
lmlogs.syslog.enable=true
vault.bypass=false- Anonymous2 months ago
We'll see what support says. They were pretty quick to lump it into an existing bug ticket.
Related Content
- 2 years ago
- 2 months ago