Possible workaround – I will test it with the next update again:
– deactivate fusion core and fusion builder
– update both
– activate them again
The issue seems to be that after updating fusion core it connects to the database without closing the processes again and again. 1&1 obviously has a restiction to 18 connections per user, so the database blocks all additional tries.
After boths parts are updated, those requests are closed or not started at all.
I have just updated Avada and have the same issue again. When I log on to the webinterface of the database, I get the following message: “already has more than ‘max_user_connections’ active connections”
Following that, there is a correlation between the update process and the error message. Cound you check, how many time the update process connects to the database?
Is it neccesary to connect that many times?