OTTER / Long time for Linux server for first configuraiton collection

[atripp]

Hi @philippe-camelio_3885 ,

Sorry this must have fell through the cracks...

Few questions.

• How soon after you add the server do you run a configuration run?
• When you say "reset otter", do you mean the Otter Service?
• Are you able to cancel those executions? Like, if you navigate to them?
• Does running the Server Checker task (on the Service Page, same page that shows Execution Dispatcher) cause them to kick off? What output do you see when you run that task, if not?

Thanks,
Alana

[philippe.camelio_3885]

@atripp said in OTTER / Long time for Linux server for first configuraiton collection:

How soon after you add the server do you run a configuration run?

YES

When you say "reset otter", do you mean the Otter Service?

I restart the docker stack -

Are you able to cancel those executions? Like, if you navigate to them?

No action (link) is available to stop them

Does running the Server Checker task (on the Service Page, same page that shows Execution Dispatcher) cause them to kick off? What output do you see when you run that task, if not?

Sometimes, when I restart the server checker, the configuration run thru

I have to make more consistent tests, but the problem occurs when I register several servers in the same time.

[atripp]

@philippe-camelio_3885 thanks for clarifying.

Next time, can you try running the Server Checker task and seeing if that clears the problem within a short time?

A configuration execution will wait until a server is in a specific status (the Server Checker puts it in that status), so I wonder if it's not being triggered. I didn't look further but confirming it twould help us isolate the issue.

[philippe.camelio_3885]

@atripp
I will make a test with few servers and check how long it takes .

[philippe.camelio_3885]

I created 4 servers (linux) and register to otter.
Start Server checker.
After few minutes, otter reports the server need to be remediated.

It is looking good if I start server checker on" rather the runnig "check configuraiton" from the server itself

Thanks for the tips

[atripp]

Thanks for confirming @philippe-camelio_3885

The "Server Checker" and "Check Configuration" are two different functions, so that kind of makes sense. The "Server Checker" should be triggered immediately after adding or modifying agent details (like IP, etc), but it clearly isn't here.

One more question - are you adding these servers via the API?

I just want to make sure we can find/repro/fix this :)

[philippe.camelio_3885]

@atripp
Servers are registered using api

[philippe.camelio_3885]

This post is deleted!

[atripp]

@philippe-camelio_3885 thanks! I've logged this as OT-495, and we'll try to get it fixed in the next mainteance release (scheduled Sept 15)

[philippe.camelio_3885]

@atripp
Good to know
Thanks