OVHcloud Web Hosting Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
FS#12629 — call queue
Incident
Report for Web Cloud
Resolved
Some calls in call queues are reportedly not being received. We will investigate.
Update(s):
Date: 2015-02-18 12:12:24 UTC
Yesterday we identified an issue caused by the change in state of call queue members.
In fact, in certain cases, some servers in the cluster were not reloading their cache and considered the member to always be in its former state.
The issue is now resolved. However, we're maintaining the developments identified last night.
Date: 2015-02-17 16:05:33 UTC
All the machines have been rebooted.
We're preparing to change the call queue infrastructure to prevent this type of issue in the future.
We will keep you updated on any implemented changes and our progress.
Date: 2015-02-17 11:53:57 UTC
Half of the machines have been rebooted.
Date: 2015-02-17 10:05:20 UTC
We're going to reboot the machines in the cluster.
Calls in progress won't be impacted.
Date: 2015-02-17 10:04:44 UTC
There are once again non-received calls in certain call queues.
We will investigate.
Date: 2015-02-16 14:19:49 UTC
The sensors are in place.
Date: 2015-02-16 11:10:41 UTC
Resynchronisation has patched the issues related to the availability of agents in certain call queues.
We're looking for the cause of the desynchronisation and adding sensors to monitor the consistency of data on this database.
Date: 2015-02-16 11:08:07 UTC
Resynchronisation complete.
Date: 2015-02-16 11:07:57 UTC
Certain agents in the call queues are not available. The root of the issue seems to be the desynchronisation of one of the databases.
Resynchronisation is in progress.
Update(s):
Date: 2015-02-18 12:12:24 UTC
Yesterday we identified an issue caused by the change in state of call queue members.
In fact, in certain cases, some servers in the cluster were not reloading their cache and considered the member to always be in its former state.
The issue is now resolved. However, we're maintaining the developments identified last night.
Date: 2015-02-17 16:05:33 UTC
All the machines have been rebooted.
We're preparing to change the call queue infrastructure to prevent this type of issue in the future.
We will keep you updated on any implemented changes and our progress.
Date: 2015-02-17 11:53:57 UTC
Half of the machines have been rebooted.
Date: 2015-02-17 10:05:20 UTC
We're going to reboot the machines in the cluster.
Calls in progress won't be impacted.
Date: 2015-02-17 10:04:44 UTC
There are once again non-received calls in certain call queues.
We will investigate.
Date: 2015-02-16 14:19:49 UTC
The sensors are in place.
Date: 2015-02-16 11:10:41 UTC
Resynchronisation has patched the issues related to the availability of agents in certain call queues.
We're looking for the cause of the desynchronisation and adding sensors to monitor the consistency of data on this database.
Date: 2015-02-16 11:08:07 UTC
Resynchronisation complete.
Date: 2015-02-16 11:07:57 UTC
Certain agents in the call queues are not available. The root of the issue seems to be the desynchronisation of one of the databases.
Resynchronisation is in progress.