API failing with http code 500 on Servicestatus request

[grenley]

BTW, we are actually doing that.
The API calls are to delete all the monitored agents that have been moved.
Kind of important. Seems like a Catch-22

[tgriep]

The API should work, it is just that there are so many services, it will take a long time to Apply the Config.
Splitting up the servers will make the Apply Config work faster.

[grenley]

Wow. This is going from bad to worse.
I just issued API deletes for all the services on a number of hosts.
When I looked at a couple of servers in Home->Hosts, they showed no services under them.
I then ran an Apply Config from the GUI, which completed in quite short order this time.
So, I then tried to delete the hosts from CCM and they all failed due to service dependencies.
And, lo and behold, the hosts' services were all magically repopulated after the apply config.
We need to take this to a problem ticket.
I'll send the email.
Can I just reference this post so I don't have to respell out all this stuff?

[dwhitfield]

Can I just reference this post so I don't have to respell out all this stuff?

Yep, that's exactly what you should do.

Once sent, please post here so we can verify that we got it.

[ssax]

In addition, it is normal when an apply config fails for it to revert the files back to the last known good configuration.

[grenley]

I have sent in an email request for a problem ticket.
Also, the Apply Configuration appeared to work properly though it finished extremely quickly (under a minute).

[tgriep]

Shall I close and lock this post so you can continue on in the support ticket?