instar4per
Programmer
Is this the right area for this? Regardless,
At work, we have multiple DB servers. A single master, and a single (soon to add more) slaves. Web front-ends load-balance between the slave servers.
As our users post forms, the post data is added to the master and allowed to propegate to the slaves. This works on every application except for one. This one is the source of this post:
In order to remove any possible problems with permissions, we've reverted our code to post as `root`. We are aware of the security implications of this move, and will change the user, as soon as the replication problem is fixed.
The code being executed is a simple INSERT statement.
* When run on the master from the mysql binary, it replicates.
* When run from a desktop posting to the master via MySQL Query Browser, it replicates.
* When run from a web-frontend's mysql binary, it replicates.
* When run from the PHP script, it doesn't replicate.
This would lead me, initially, to believe it was a PHP malfunction. However, if it was, then why would it post to the master and not replicate across? Using the same username, password, and query from the mysql binary replicates without flaw.
The error logs on both the master and the slave are blank, and the SHOW SLAVE STATUS command shows nothing out of the ordinary. It says the thread is running, with no errors reported.
Any suggestions or things to look at? The tables aren't locked, the file permissions are good, they've even been recreated under a different name and the same problem happens. Other tables in the same database replicate just fine, it's this one application.
-iNSTA
aim: instar4per
email: instar4per @ hotmail.com
At work, we have multiple DB servers. A single master, and a single (soon to add more) slaves. Web front-ends load-balance between the slave servers.
As our users post forms, the post data is added to the master and allowed to propegate to the slaves. This works on every application except for one. This one is the source of this post:
In order to remove any possible problems with permissions, we've reverted our code to post as `root`. We are aware of the security implications of this move, and will change the user, as soon as the replication problem is fixed.
The code being executed is a simple INSERT statement.
* When run on the master from the mysql binary, it replicates.
* When run from a desktop posting to the master via MySQL Query Browser, it replicates.
* When run from a web-frontend's mysql binary, it replicates.
* When run from the PHP script, it doesn't replicate.
This would lead me, initially, to believe it was a PHP malfunction. However, if it was, then why would it post to the master and not replicate across? Using the same username, password, and query from the mysql binary replicates without flaw.
The error logs on both the master and the slave are blank, and the SHOW SLAVE STATUS command shows nothing out of the ordinary. It says the thread is running, with no errors reported.
Any suggestions or things to look at? The tables aren't locked, the file permissions are good, they've even been recreated under a different name and the same problem happens. Other tables in the same database replicate just fine, it's this one application.
-iNSTA
aim: instar4per
email: instar4per @ hotmail.com