Mysql Replication issue

jaiswal · September 19, 2015, 11:05am

below are the error message showing in mysql slave server.

150919 10:56:13 [ERROR] Slave SQL: Error ‘Table ‘kaltura.scheduler_status’ doesn’t exist’ on query. Default database: ‘kaltura’. Query: ‘/* ip-172-31-5-197[1267114391][propel] */ INSERT INTO scheduler_status (ID,CREATED_AT,UPDATED_AT,SCHEDULER_ID,SCHEDULER_CONFIGURED_ID,TYPE,VALUE) VALUES (NULL,‘2015-09-19 16:26:13’,‘2015-09-19 16:26:13’,1,87535,7,1)’, Error_code: 1146
150919 10:56:13 [Warning] Slave: Table ‘kaltura.scheduler_status’ doesn’t exist Error_code: 1146
150919 10:56:13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and resta

jess · September 21, 2015, 8:42am

Hello,

kaltura.scheduler_status is used for the batching mechanism and should exist.
I’d suggest scratching the existing slave and redo the initial replication process.
There is an aiding script for setting up the replication, see here:

github.com

kaltura/platform-install-packages/blob/Jupiter-10.20.0/doc/rpm-cluster-deployment-instructions.md#mysql-replication-and-scaling

# Deploying Kaltura Clusters

Below are **RPM** based instructions for deploying Kaltura Clusters.    
Refer to the [All-In-One Kaltura Server Installation Guide](https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md) for more notes about deploying Kaltura in RPM supported environments.    
Refer to the [Deploying Kaltura Clusters Using Chef](https://github.com/kaltura/platform-install-packages/blob/master/doc/rpm-chef-cluster-deployment.md) for automated Chef based deployments.

### Instructions here are for a cluster with the following members:

* [Load Balancer](#apache-load-balancer)
* [NFS server](#the-nfs-server)
* [MySQL Database](#the-mysql-database)
* [Sphinx Indexing](#the-sphinx-indexing-server)
* [Front servers](#the-front)
* [Batch servers](#the-batch)
* [DWH server](#the-datawarehouse)
* [Nginx VOD server](#nginx-vod-server)
* [Streaming Server](#the-streaming-server)
* [Upgrade Kaltura](#upgrade-kaltura)
* [Platform Monitoring](#platform-monitoring)
* [Backup and Restore](#backup-and-restore-practices)

This file has been truncated. show original

jaiswal · September 21, 2015, 9:10am

Hello Jess,

Thanks for prompt action.

I have followed the suggested process 3 times but still getting same error in slave server.

github.com

kaltura/platform-install-packages/blob/Jupiter-10.20.0/doc/rpm-cluster-deployment-instructions.md#mysql-replication-and-scaling

# Deploying Kaltura Clusters

Below are **RPM** based instructions for deploying Kaltura Clusters.    
Refer to the [All-In-One Kaltura Server Installation Guide](https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md) for more notes about deploying Kaltura in RPM supported environments.    
Refer to the [Deploying Kaltura Clusters Using Chef](https://github.com/kaltura/platform-install-packages/blob/master/doc/rpm-chef-cluster-deployment.md) for automated Chef based deployments.

### Instructions here are for a cluster with the following members:

* [Load Balancer](#apache-load-balancer)
* [NFS server](#the-nfs-server)
* [MySQL Database](#the-mysql-database)
* [Sphinx Indexing](#the-sphinx-indexing-server)
* [Front servers](#the-front)
* [Batch servers](#the-batch)
* [DWH server](#the-datawarehouse)
* [Nginx VOD server](#nginx-vod-server)
* [Streaming Server](#the-streaming-server)
* [Upgrade Kaltura](#upgrade-kaltura)
* [Platform Monitoring](#platform-monitoring)
* [Backup and Restore](#backup-and-restore-practices)

This file has been truncated. show original

jaiswal · September 21, 2015, 11:47am

I have followed the suggested process 3 times but still getting same error in slave server.

jaiswal · September 22, 2015, 9:16am

Hi Jess,

Please update on below request.

jess · September 22, 2015, 9:48am

Hi,

Sorry but I have no idea why the replication does not create that table. I suggest you look at the logs when attempting the initial replication process and check for errors. Once we find one, we’ll be smarter.

jaiswal · September 22, 2015, 10:08am

Ok Jess I am working on this issue.