Page 1 of 1

Running reports on slave mysql replicated server

PostPosted: Wed Oct 30, 2013 6:44 pm
by zefk
Hi, I installed latest ViciBox5.0.3 x64 with updates to Rev: 2039 and it is working fine.
I configured realtime mysql replication with another debian 7 server and it is working fine also.
I configured in Sytem Settings the field "Slave Database Server" to point to the ip of slave server and I selected all the reports to run on slave.

The reports are still running on master because even with mysql shutted down on replicated server the reports continue to run. In system_settings table the field "slave_db_server" was changed to the ip address of the slave and "reports_use_slave_db" field was changed into a list of reports comma separated.

What should I check next?
Thank you!

Re: Running reports on slave mysql replicated server

PostPosted: Thu Oct 31, 2013 5:24 am
by mflorell
What report are you running?

We have several clients using this feature successfully, so I'm not sure what is not working on your setup.

Re: Running reports on slave mysql replicated server

PostPosted: Thu Oct 31, 2013 5:53 am
by zefk
I am running realtime reports, outbound reports but all reports are runing fine. With slave mysql shutted down I expect to receive an db connect error kind of message. But the reports run fine on master db.

Thank you.

Re: Running reports on slave mysql replicated server

PostPosted: Thu Oct 31, 2013 6:53 am
by zefk
I did a fresh install into a vm just to check. The same missfunctionality. There is a bug in 5.0.3?
If I remember well the feature worked fine in 4.X last year when I tested.
Regards

Re: Running reports on slave mysql replicated server

PostPosted: Fri Nov 01, 2013 6:17 am
by mflorell
You found a bug!

It's been fixed in svn/trunk. Just upgrade to the latest code and you're good to go.

Thanks!

Re: Running reports on slave mysql replicated server

PostPosted: Sat Nov 02, 2013 11:08 pm
by williamconley
zefk wrote:I did a fresh install into a vm just to check. The same missfunctionality. There is a bug in 5.0.3?
If I remember well the feature worked fine in 4.X last year when I tested.
Regards

Please note: 4.X and 5.0.3 are ViciBOX (INSTALLER!) versions. And this bug was not related to the installer, but to the core code of Vicidial which is presently in 2.8.X build XXXXX. Remember to reference the Vicidial Version with Build (available at the bottom left corner of the Admin screens) when asking questions about Vicidial and the ViciBOX version (name of the .iso is best) when discussing install related concerns. And there is even a board dedicated to the installer related questions as well.

But keep finding bugs. We love it when they get found and squished. :)