We will relaunch the service.
The service is up.
We had the same problem this morning.
The service is back.
We will check the logs to find the origin of the problem.
The problem seems to come from the sql table events of the vCenter.
The configuration that we have defined: 60 days for events and 120 days for the tasks does not seem to be applied.
We will perform maintenance tonight to purge this table.
The maintenance will begin at 22:30 and is expected to take 2 hours.
During the mainteance the vCenter service will not be available.
Maintenance is still in progress.
After a full backup of the database and stopping the vCenter we still have 9 active connections who prevented us to apply the patches.
Powered by Flyspray