Slave Replication Stops

[jordanm]

Hi All,

I hope you all can assist me with a problem I have having. I am trying to set up replication between a Master and a Slave DB.

Server Specs:
Main:

HP DL380P Gen8
16Gb RAM
4x 15K SAS drives in RAID 10
MariaDB - 5.5.33

Slave DB:

HP DL380P Gen8
16Gb RAM
2x 15K SAS drives in RAID 1 with a hot spare
MySQL 5.1.68

From Home Page:

VERSION: 2.10-451a
BUILD: 140902-0816

From System Settings:

Version: 2.10b0.5
SVN Version: 2005
DB Schema Version: 1386

Installed via Vicibox 6.0.2

I have used a guide from plus bryan for replication

I have tried this several times but each time I get error 1032 or 1062 and the replication stops. I can skip the errors but obviously I am not too happy about that.

We have tried to set up another server for replication. This also runs MariaDB - 5.5.33. I have had the same problems with this server as with the current slave.

The machines are running on the same LAN.

I would really appreciate any and all assistance with this

Kind Regards,

Jordan

[williamconley]

While I would love to help, I have to say that this is in no way related to Vicidial or Vicibox or Vici ... anything. LOL

MySQL replication is complex but does work. My advice would be to attempt a textbook replication scenario on a sample DB unrelated to Vicidial (possibly even on another system) first. After you get that operational you can bring that experience to your Vicidial system one step at a time. Don't just jump in head first and hope everything works, since this will obviously have a learning curve for you. Take some baby steps.

That being said; "i get error 1032 ..." is not likely to get anything other than "you should probably google that" since we don't have the configuration steps and file nor do we have the error log text. But as I said, a mysql support forum would be a much better place to start for good help on this topic.

[okli]

You should take a look which query exactly breaks the replication and figure out why, this can be seen from 'show slave status' run on the Slave.
If you are using reports off the slave server, it's most likely a report attempting to write to the slave, instead to the master.

I strongly suggest you to take a look at this thread and set read-only on the slave:
viewtopic.php?f=7&t=33944

[williamconley]

You should take a look which query exactly breaks the replication and figure out why, this can be seen from 'slave show status' run on the Slave.
If you are using reports off the slave server, it's most likely a report attempting to write to the slave, instead to the master.

I strongly suggest you to take a look at this thread and set read-only on the slave:
viewtopic.php?f=7&t=33944

Cool. I'd not seen that post.