Urgent - Connection to cache service failed

[KonsultVn]

Hi,

We currently have major problems in our integrations where we get the following response: 

"Connection to cache service failed" from the API.

Can you please look into this as soon as possible, thanks!

[Yıldırım]

Hello, 

the error was related to the load balancing and how the requests get distributed when one of the servers have been heavily loaded. We have increased the number of servers, aiming that load will be more evenly distributed. We're currently monitoring the status, and it seems that action helped to resolve the issue. Please let us know if you still receive the error. We're sorry for the standstill this may have caused in your integrations. 

[Roland van Belle - Consolit]

Thanks for the update. Till now we did not have this error anymore.

[Yıldırım]

Thanks for the info Roland 

[Jeroen Bijl]

I have encountered the error again a few times the last 30 min or so

[ErikLevin]

We are looking at this. We have one machine that are not responsive. Will recycle that machine now

[Steinar Møller]

The issue lasted until 04:00 this morning, same as the incendent last friday. Hope you will look into this iin order to avoid this happening again.

[Yıldırım]

Hello, are you permanently receiving the error ? We're currently investigating it. 

[Olivia Jansson]

@yildirim do you have any updates or an ETA?

[jnemo]

This is only from one of our clients, but seems very intermittent

[andreasaulin]

Same again today:

{"message":"Connection to cache service failed"}

[AliMKhan · Accepted solution]

The issue seems to have been on one of the IIS server that was handling API calls.
For some reason it was not able to connect to the cache, whilst other servers were able to connect at the same time.
We suspect that there were too many connections open on that server for some reason.
At the moment everything is looking normal and we will monitor the status closely.

Sorry for the inconvenience.

[andreasaulin]

Still an issue. 6 hours. No feedback, no fix ...

[andreasaulin]

At excactly 04:00 we received the last error. 12 hours and 30 minutes with errors - and no update at status.visma.com. This is not good at all.

[Magnus Johnsen]

Hi, we are looking in to the root cause of the issue and will release a small fix during the day and keep monitoring the issue.

The issue seems to be with our load balancer, we are looking in to this further and will provide more information and a post mortem as soon as possible.

We are sorry for any inconveniance this has caused you. 

[Magnus Johnsen]

We are still monitoring this issue. Since the fix yesterday, It does not seem like the issue has reoccurred.

For now we will continue to monitor this, please let us know if you are having any issue.

Thank you. 

[KonsultVn]

The problem is back since about 15 minutes ago...

Can you look into it as soon as possible?

[JoLu]

We also get these errors, have seen it since about 14 and it still is an issue 6 hours later.

[Roland van Belle - Consolit]

Our customer had this message too at the same time till now!

We want to know if this problem will be solved on short term.

[erik-kle]

"Connection to cache service failed" 14:30 and 15:30 today

controller/api/v1/inventory

[KonsultVn]

The above problem has reappeared since about 20 minutes ago. 
Can you look into this further?

Thanks!