!tlist in 36.xxx+ versions of the collector
Has anyone else noticed that !tlist doesn't work in versions 36.000 of the collector and above? This is the collector that just came out of EA and is now GA.
LM User
Posted 1 year ago·Last reply 1 year ago
15 comments
EvanTempel
·1 year agoRan it on 3 of our collectors on 36.x, tlist with no arguments or params. No issues.
LM User
OP1 year agohehe, LM's just messing with me personally...
Lewis_Beard
·1 year agoI dont have that vault setting at all in any of my 5 configs. And on the first one there, I dont know if you made a typo or were in a hurry or if I'm being overly picky, but mine has a "d" on the end, on ours the value is lmlogs.syslog.enabled with a d at the end. And mine is set to false, if that helps.
Lewis_Beard
·1 year agoWhen I say 5, I mean, I looked in Agent, WatchDog, Wrapper, Sbproxy, and Website ... just to be sure. I only checked a couple of different collectors, some of the ones that worked on my side.
LM User
OP1 year agoYep, i meant enabled. Was in a hurry. It would be in the agent config. As far as i can tell, those are the only differences. I'll let support know. I wonder how much faster they would find bugs like this if they just involved the community. I'm sure they could say, "hey does anyone have a collector with a, b, and c in the collector config, running version x? Could we run a debug command and grab the output or test this thing?" I'm sure with all of us someone would have a matching scenario.
Lewis_Beard
·1 year agoI 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.
LM User
OP1 year agoI 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
LM User
OP1 year agoWe'll see what support says. They were pretty quick to lump it into an existing bug ticket.
Lewis_Beard
·1 year agoIts an upgrade. It was deployed in 2021.
LM User
OP1 year agoInteresting. This is what I get:
Is your collector a new install or an upgrade? Mine's an upgrade. Wonder if something breaks during the upgrade that doesn't break during the new install.
Lewis_Beard
·1 year agoAnd here is an image showing I'm on 36.000 .... headed to lunch but good luck
Lewis_Beard
·1 year agoI can. When I run !tlist without params, I get back the results I expect.
I redacted the IPs but here is a shot from the command with no args.