Aha! Well, it was not that the server was i read-only mode. But that
did get me thinking about what user was actually being used and what
their permissions were, and I recalled reading something somewhere about
mysqldump and have a specific definer on things like triggers and
procedures causing an issue like this.
It was instead that when I dumped the database, it dumped a few
triggers, which had a definer that did not exist on the slave. I added
that user and gave it the correct permissions and the error has disappeared.
Thanks so much for the assistance.
On 9/29/2010 2:21 AM, a.smith@stripped wrote:
> Quoting aaron beverly <aaron.beverly@stripped>:
>> No, the error is on the slave. I am getting that error message by
>> running "show slave status". Queries on the master execute without
>> error. It is just the replication that is getting hung up.
>> I am actually following the howto that you recommended. That is where
>> I got the info to set up replication. And everything works, except for
>> this issue.
> So it wont be slave user privileges either, this is used to read from
> the master, not write to the slave.
> Have you tried updating the table on the slave using the command that
> is failing when connected locally to the DB on the slave? Worth
> checking the server isnt in read only mode, or that there arent file
> system permissions problems.