Vicibox 11 - Slave Install breaks at DB Dump stage

[rustynail]

Hi,

While installing - ViciBox v.11.0.1 230806 - cluster, when I installed slave server, all goes fine till the stage where it says "Beginning database load into slave, this may take a while..." and starts dumping data from master to /tmp/vicimaster.sql.

After a while (depending on DB size) it crashes with below error:

Doing Slave-specific MySQL setup...

Beginning database dump from master, this may take a while...

Info: Using unique option prefix 'all-database' is error-prone and can break in the future. Please use the full name 'all-databases' instead.
mysqldump: Couldn't execute 'show create table `user`': SHOW VIEW command denied to user 'slave'@'xx.xx.xx.xx' for table `mysql`.`user` (1142)
Could not get database dump from master: 512 at /usr/local/bin/vicibox-install line 280, <STDIN> line 16.

Can someone please guide if there is any patch to fix this or if I can do some modification in script so that it go smoothly.

Thanks.

[carpenox]

Just add the slave user to the asterisk database and it should work. I am not sure the exact user its asking for but you should have it on your error logs of mysql, add that user, search google if you need to, to find out how to do it. Good luck, youcan also message me directly through any method below.

[rustynail]

Just add the slave user to the asterisk database and it should work. I am not sure the exact user its asking for but you should have it on your error logs of mysql, add that user, search google if you need to, to find out how to do it. Good luck, youcan also message me directly through any method below.

Thanks, So you mean to add this user on master db server or the slave one that I am installing? It's the 'slave' user for which the command is getting denied.. and I can see this user exists on master DB... as you see below...

| cron | *A4B61573190FG57F932C8886EBFCF | % |
| cron | *A4B6157319074F7F932C8886EBFCF | localhost |
| custom | *39798AA2596A7702568384D8C5AC3 | localhost |
| custom | *39798AA2596A7702568384D8C5AC3 | % |
| slave | *DAE180E1578479C7060AC1198C2F5 | % |

The actual issue seems this user doesn't have access on mysql.user table for SHOW VIEW....

Any further suggestions..

[carpenox]

search google or chatgpt/bing how to add "show view" permissions to mysql

[rustynail]

search google or chatgpt/bing how to add "show view" permissions to mysql

permission on Master DB ,,,right?
Yes, that can be done and I have done it previously on one of my clusters. But I am looking for a method so I do not have to do it manually before installing slave. a patch or some modification in install.pl before starting vicibox-install ?

Thanks.

[rustynail]

Has anyone figured out what is the issue and how it can be solved before installing slave. Should we correct permissions on master DB before installing slave?

[carpenox]

maybe this article i wrote a few years ago can help you out

https://dialer.one/how-to-setup-a-slave ... -vicidial/

[williamconley]

Has anyone figured out what is the issue and how it can be solved before installing slave. Should we correct permissions on master DB before installing slave?

At the top of this page is a link for "Vicidial Issue Tracker".

If you post the details well enough and describe the situation carefully you should get the issue fixed eventually. That's what the Issue Tracker is specifically for.

Also, if you post the line in the install.pl where it dies, it's very likely we can generate a sql command that could be placed one line before that to allow success (in future installs). In fact, if you can do that in a test install and place that line in your Isue tracker as a comment after the fact, it may well get used temporarily until they find the earlier problem that caused this hiccup.

And it'll help everyone who's installing