Cluster Setup- Install script assumes first dialer

[rustynail]

Hi,

I am adding new server in existing cluster which is based on vicibox-8.0.1 and svn 3114. The confusion is that it detects vicibox table and finds svn version to be installed fine. It also suggests to disable legacy mode which I do.
But then it always says its first dialer server when I press Y for Telephony server even its 10th server in cluster. Any idea why it happens and if its safe to ignore it and continue with install ?

Below is the log of install. Thanks in advance.


Do you want to continue with the ViciBox install? [y/N] : y
Do you want to enable expert installation? [y/N] : y
Do you want to enable legacy install support? [y/N] : y
The Internal IP address found was 185.x.x.x.
Do you want to use this IP address for ViciDial? [Y/n] : y
Will this server be used as the Database? [y/N] : n
Please input the master database IP address (185.x.x.x) : 185.x.x.x
IP Address checks good: 185.x.x.y
Do you want to connect using the default ViciDial DB settings? [Y/n] : y
Database Connectivity checks good
ViciBox table found
DB SVN rev : 3114
DB Slave user : slave
DB Slave pass : slave1234
ViciBox v.4.0+ cluster info found! Recommend disabling legacy mode.
If you do not have a strong reason for enabling legacy mode, disable it.
Would you like to disable legacy mode? [Y/n] : y

Will this server be used as a Web server? [y/N] : y
---> Install Redirect Page? [y/N] : n
---> Install phpMyAdmin ? [y/N] : n

Will this server be used as a Telephony server? [y/N] : y
We are the first dialer
No Archive server found in provisioning table

Will this server be used as an Archive server? [y/N] : n
The database SVN revision is 3114. This system will be updated to that revision

Do you want to disable the built-in firewall? [y/N] : y


--- ViciBox v.8.0 Install Summary ---

Expert : Yes
Legacy : No
Database : No
Web : Yes
Redirect : No
PMA : No
Telephony: Yes
Archive : No
Firewall : Disabled

--- Configuration Information ---
- Database -
SVN Rev : 3114
IP Addr : 185.x.x.y
Name : asterisk
User : cron
Password : 1234
Cust User: custom
Cust Pass: custom1234
Port : 3306

[rustynail]

Also I have noticed every new server added shows asterisk version as 1.4.21.2.

[williamconley]

Switch to 8.1.2. No reason to keep using the older version unless you have a need for an older version of Asterisk. Upgrade all the servers if that's the case, then you can use the latest version of asterisk.

Apparently the vicibox configuration table does not have an entry for a dialer as yet. You may want to look at the table and see why.

this is an installer question. Moving to the Vicibox (installer) board.

[rustynail]

Thanks for replying William,

Old version is being used because it was installed on this version previously and now client want to add more servers on same version. Can't update to new version for now due to some reasons. Also upgrading a production setup has its own risks involved.

The question is that :
1. Its ok to disable legacy mode or should I continue with forced legacy mode?
2. can I safely ignore the message "We are first dialer" and continue adding servers in same fashion?

So far I haven't received any complaint from customer for the newly added 5 servers in cluster. (except that when I mistakenly rebooted the previous server where 7 agents were dialing, instead of new one )

I can see entries for DB, WEB and TEL servers in vicibox table as below.

MariaDB [asterisk]> select * from vicibox\G
*************************** 1. row ***************************
server_id: 1
server: SERVER-DB
server_ip: 185.x.x.y
server_type: Database
field1: 0
field2: asterisk
field3: 3114
field4: cron
field5: 1234
field6: custom
field7: custom1234
field8: slave
field9: slave1234
*************************** 2. row ***************************
server_id: 2
server: SERVER-DB
server_ip: 185.x.x.y
server_type: Web
field1: 185.x.x.y
field2: oofcdPoFhGhWN1HJaigynQf6OzOQNSbT
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 3. row ***************************
server_id: 3
server: SERVER-WEB
server_ip: 185.x.x.y
server_type: Database
field1: 2
field2: asterisk
field3: 3114
field4: cron
field5: 1234
field6: custom
field7: custom1234
field8: slave
field9: slave1234
*************************** 4. row ***************************
server_id: 4
server: SERVER-WEB
server_ip: 185.x.x.x
server_type: Web
field1: 185.x.x.x
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 5. row ***************************
server_id: 5
server: SERVER-WEBS
server_ip: 185.x.x.a
server_type: Web
field1: 185.x.x.a
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 6. row ***************************
server_id: 6
server: SERVER-WEBS
server_ip: 185.x.x.a
server_type: Telephony
field1: 185.x.x.a
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 7. row ***************************
server_id: 7
server: SERVER-TEL2
server_ip: 185.x.x.b
server_type: Web
field1: 185.x.x.b
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 8. row ***************************
server_id: 8
server: SERVER-TEL2
server_ip: 185.x.x.b
server_type: Telephony
field1: 185.x.x.b
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 9. row ***************************
server_id: 9
server: SERVER-TEL3
server_ip: 185.x.x.c
server_type: Web
field1: 185.x.x.c
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 10. row ***************************
server_id: 10
server: SERVER-TEL3
server_ip: 185.x.x.c
server_type: Telephony
field1: 185.x.x.c
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 11. row ***************************
server_id: 11
server: SERVER-TEL4
server_ip: 185.x.x.d
server_type: Web
field1: 185.x.x.d
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 12. row ***************************
server_id: 12
server: SERVER-TEL4
server_ip: 185.x.x.d
server_type: Telephony
field1: 185.x.x.d
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 13. row ***************************
server_id: 13
server: SERVER-TEL6
server_ip: 185.x.x.f
server_type: Web
field1: 185.x.x.f
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 14. row ***************************
server_id: 14
server: SERVER-TEL6
server_ip: 185.x.x.f
server_type: Telephony
field1: 185.x.x.f
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 15. row ***************************
server_id: 15
server: SERVER-TEL7
server_ip: 185.x.x.g
server_type: Web
field1: 185.x.x.g
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 16. row ***************************
server_id: 16
server: SERVER-TEL7
server_ip: 185.x.x.g
server_type: Telephony
field1: 185.x.x.g
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 17. row ***************************
server_id: 17
server: SERVER-TEL5
server_ip: 185.x.x.e
server_type: Web
field1: 185.x.x.e
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 18. row ***************************
server_id: 18
server: SERVER-TEL5
server_ip: 185.x.x.e
server_type: Telephony
field1: 185.x.x.e
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 19. row ***************************
server_id: 19
server: SERVER-TEL8
server_ip: 185.x.x.h
server_type: Web
field1: 185.x.x.h
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 20. row ***************************
server_id: 20
server: SERVER-TEL8
server_ip: 185.x.x.h
server_type: Telephony
field1: 185.x.x.h
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 21. row ***************************
server_id: 21
server: SERVER-TEL9
server_ip: 185.x.x.i
server_type: Web
field1: 185.x.x.i
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 22. row ***************************
server_id: 22
server: SERVER-TEL9
server_ip: 185.x.x.i
server_type: Telephony
field1: 185.x.x.i
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 23. row ***************************
server_id: 23
server: SERVER-TEL10
server_ip: 185.x.x.j
server_type: Web
field1: 185.x.x.j
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 24. row ***************************
server_id: 24
server: SERVER-TEL10
server_ip: 185.x.x.j
server_type: Telephony
field1: 185.x.x.j
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 25. row ***************************
server_id: 25
server: SERVER-T11
server_ip: 185.x.x.k
server_type: Web
field1: 185.x.x.k
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 26. row ***************************
server_id: 26
server: SERVER-T11
server_ip: 185.x.x.k
server_type: Telephony
field1: 185.x.x.k
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 27. row ***************************
server_id: 27
server: SERVER-T12
server_ip: 185.x.x.l
server_type: Web
field1: 185.x.x.l
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 28. row ***************************
server_id: 28
server: SERVER-T12
server_ip: 185.x.x.l
server_type: Telephony
field1: 185.x.x.l
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 29. row ***************************
server_id: 29
server: SERVER-T13
server_ip: 185.x.x.m
server_type: Web
field1: 185.x.x.m
field2:
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
*************************** 30. row ***************************
server_id: 30
server: SERVER-T13
server_ip: 185.x.x.m
server_type: Telephony
field1: 185.x.x.m
field2: NULL
field3: NULL
field4: NULL
field5: NULL
field6: NULL
field7: NULL
field8: NULL
field9: NULL
30 rows in set (0.00 sec)

Thanks for moving post in proper board

[rustynail]

Also I have noticed that "vicibox-install.pl" script uses below query to check for TEL servers when we press Y for prompt "Will this server be used as a Telephony server?"

$stmtVBOXtelct = "select server from vicibox where server_type='Dialer';";

But there is no such type set in db fields, instead there server_type is always 'Telephony' for TEL servers hence script assumes there are no existing TEL servers and displays message that its first server. Now when I changed 'Dialer' to 'Telephony' and re-run the vicibox-install --debug then after pressing Y for prompt "Will this server be used as a Telephony server?" this time it detects all telephony servers fine and gives correct output as below:

Will this server be used as a Telephony server? [y/N] : y
We are not the first dialer, there are 13 others

Hope it helps anyone else facing this issue with this version. Also I hope it will work fine after making this change....

Other option I used is to force continue with legacy and input all info manually. This way it asks if its first server in cluster.

By the way what difference does it actually make if server is first or not ?

Cheers!

UPDATE: Another thing noticed that by forcing legacy mode and entering details manually, that server is not inserted in vicibox table

[williamconley]

The question is that :
1. Its ok to disable legacy mode or should I continue with forced legacy mode?
2. can I safely ignore the message "We are first dialer" and continue adding servers in same fashion?

So far I haven't received any complaint from customer for the newly added 5 servers in cluster.

I'm confused. You asked and then answered your own question.

Can't update to new version for now due to some reasons.

I'll bite: What Reasons?

Code: Select all

$stmtVBOXtelct = "select server from vicibox where server_type='Dialer';";

But there is no such type set in db fields, instead there server_type is always 'Telephony' for TEL servers hence script assumes there are no existing TEL servers and displays message that its first server. Now when I changed 'Dialer' to 'Telephony' and re-run the vicibox-install --debug then after pressing Y for prompt "Will this server be used as a Telephony server?" this time it detects all telephony servers fine and gives correct output as below:

This sounds like it should be put into the Vicidial Issue Tracker directly, then put a link here. Although it's possible Kumba will see it here in this post, of course.

[rustynail]

I'm confused. You asked and then answered your own question.

Just wanted to confirm as haven't received any complain yet because customer hasn't started using new servers and I do not see any abnormality.

I'll bite: What Reasons?

oops! To be honest main reason is the fear of tempering a production server as client is big and can't afford to upset him. Further they are satisfied with current version and asked to remain on same version.

This sounds like it should be put into the Vicidial Issue Tracker directly, then put a link here. Although it's possible Kumba will see it here in this post, of course.

Ok, can I put it there? haven't used issue tracker yet.
However as mentioned, I replaced 'Dialer' with 'Telephony' in script and it worked as expected. Now going to add another server in it following same pattern.

Thanks!

[carpenox]

Yu can follow my latest article for setting up a cluster here:

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


Chris

[williamconley]

This sounds like it should be put into the Vicidial Issue Tracker directly, then put a link here. Although it's possible Kumba will see it here in this post, of course.

Ok, can I put it there? haven't used issue tracker yet.
However as mentioned, I replaced 'Dialer' with 'Telephony' in script and it worked as expected. Now going to add another server in it following same pattern.

Vicidial Issue Tracker is for "this is wrong, here's a fix, please include in next build". This forum is where you go for help with YOUR problems. That tracker is where you get a BUG fixed when you find one.

[carpenox]

lol too funny