How do you get around errors where the website is trying to write to the db on start up. But it's from a read only load balanced server that shouldn't have write access to the database. Is it a case of temporarily allowing access for them to complete there task?
Errors include:
ERROR Umbraco.Core.Persistence.UmbracoDatabase - Exception (99054426).
System.Data.SqlClient.SqlException (0x80131904): The UPDATE permission was denied on the object 'cmsMacro', database
'livedb'
ERROR Umbraco.Forms.Web.Migrations.MigrationEvents - Error running Umbraco Forms migration
System.Data.SqlClient.SqlException (0x80131904): The UPDATE permission was denied on the object 'cmsMacro', database 'livedb'
Thanks for your prompt reply. I have done the upgrade already on our read/write server and it seems to have worked correctly. Could this be an over hang and temporarily granting access might resolve the errors?
Yes correct version number, not sure about the forms. I noticed another forms error in the read only logs.
Surely it's not a requirement that they have write access to the db?
ERROR Umbraco.Web.Strategies.ServerRegistrationEventHandler - Failed to update server record in database.
System.Data.SqlClient.SqlException (0x80131904): The UPDATE permission was denied on the object 'umbracoLock', database 'livedb'
I am getting the Scheduling.KeepAlive error on my slave servers. When you say it was a poorly implemented load balancer solution that was the underlying cause, what do you mean? Was there a specific configuration setting that was wrong?
Errors on website start up (read only server)
Hi,
Version 7.11.1
How do you get around errors where the website is trying to write to the db on start up. But it's from a read only load balanced server that shouldn't have write access to the database. Is it a case of temporarily allowing access for them to complete there task?
Errors include:
Thanks
Hi Jon,
It seems you are trying to do a upgrade. An upgrade should always be done from a server that has write access to the db
Dave
Hi Dave,
Thanks for your prompt reply. I have done the upgrade already on our read/write server and it seems to have worked correctly. Could this be an over hang and temporarily granting access might resolve the errors?
Thanks
So probalby something is triggering the upgrade.
Does your web.config on have the correct version number in it ?
Dave
Yes correct version number, not sure about the forms. I noticed another forms error in the read only logs.
Surely it's not a requirement that they have write access to the db?
Hi Jon,
Did you have this error before the upgrade to 7.11.1 ? What version were you running before this.
I see only one place in the code where this error is logged : https://github.com/umbraco/Umbraco-CMS/blob/7ee510ed386495120666a78c61497f58ff05de8f/src/Umbraco.Web/Strategies/ServerRegistrationEventHandler.cs#L143
I assume you use this to make your server run as a slave servere : https://our.umbraco.com/documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/flexible-advanced#explicit-master-scheduling-server
Dave
Hi Dave,
Yes had the issue with 7.5.11 when I joined the company.
Yes we do want to run it as a slave, will check the link out.
Thanks
Edit: looking at the link it looks like this hasn't been implemented so I'm going to try it. thanks
Hi Jon,
Did you perhaps use a different db user for your slave servers that only has read access to the db ?
Dave
Yes the user for the db is different on the slave servers. It is read only.
I guess the question I should be asking is it possible to have slave servers running with read access only to the db?
Than that is the cause.
You can use the link I posted earlier to designate your servers as master/slave.
The slave servers will only write to tables they need access too.
Dave
First eyes over looks good following implementation however I did spot this in the logs for one of the read only slave servers.
I wouldn't have thought the slave server would want to access the master server?
Edit : Looks like the errors have gone though now so it was a poorly implemented load balancer solution that was the underlying cause. Thank you
Hi Jon,
I am getting the Scheduling.KeepAlive error on my slave servers. When you say it was a poorly implemented load balancer solution that was the underlying cause, what do you mean? Was there a specific configuration setting that was wrong?
Thanks
Tony
is working on a reply...