Page 1 of 1

Vicidial Update (SVN)

PostPosted: Wed Jan 11, 2017 5:16 pm
by gequiros
As some you can read by my profile, i have a MultiServer Setup i got (right now is for testing and learning)

1 DB
1 WEB
4 Asterisk

I have read that as a suggestion i must keep it updated

I have been doing zypper updates and all so far great, but i was told, the updates to the VICIDIAL is thry SVN

Can you please guide me how to do updates?

My Install was VICIBOX from scratch 7.0.3

Thanks for your help, hope i can learn and as well help others

Thanks !!!

Ps: I have seen some tutorials, but they are VERY old... ancient technology i may say, so, i don't want to break anything !!!

Re: Vicidial Update (SVN)

PostPosted: Wed Jan 11, 2017 5:37 pm
by mflorell
FIRST, you should update your database schema(see instructions below).

Then, on each server, run the following:
- mkdir /usr/src/astguiclient
- cd /usr/src/astguiclient
- svn checkout svn://svn.eflo.net:3690/agc_2-X/trunk
- cd trunk
- perl install.pl

You will also need to separately update the Database Schema, this is done using the sql upgrade files found in the "extras" directory depending on the version you are upgrading from.(this is basically the instructions from the UPGRADE document)
mysql
use asterisk
\. /path/from/root/extras/upgrade_2.8.sql
\. /path/from/root/extras/upgrade_2.10.sql
\. /path/from/root/extras/upgrade_2.12.sql
\. /path/from/root/extras/upgrade_2.14.sql
quit

Re: Vicidial Update (SVN)

PostPosted: Wed Jan 11, 2017 7:43 pm
by gequiros
Thanks so much for your help...

Re: Vicidial Update (SVN)

PostPosted: Wed Jan 11, 2017 9:29 pm
by ambiorixg12
Matt I remember I did an upgrade doing the following steps and it works fine

1) cd /usr/src/astguiclient/trunk

2) svn up

3) Going into mysql and executing the upgrade sql file:
a) mysql
b) use asterisk
c) \. /usr/src/astguiclient/trunk/extras/upgrade_2.12.sql
d) quit

it is pretty much the same, with some variations, my question are these step still valid ?

Re: Vicidial Update (SVN)

PostPosted: Wed Jan 11, 2017 9:58 pm
by mflorell
Yes, that will work, just make sure you svn up and install.pl on each server in the cluster.

Re: Vicidial Update (SVN)

PostPosted: Sat Jun 09, 2018 3:53 pm
by VFRDavid
Matt (or anyone who may want to weigh in): This question is more out of curiosity than due to a problem I am having...

The most recent SVN update performed was on a 4 server cluster (1 DB/Web, 3 Asterisk/Web) that was originally installed in April 2011 using a v6.x ISO that gave them a v2.10 system (sorry, I am not sure of the starting SVN/DB Schema/v2.10 suffix version numbers). During the upgrade, I followed the order I found in these forums, which was essentially:

1) backup (and verify the backup)
2) SVN up (or checkout) on each server (which just downloaded the latest version, but did not change the actual running code / SVN version).
3) Multiple MySQL upgrade(s) on the DB server (check the schema version, find the proper starting point of the appropriate upgrade.sql script, and run from there on).
4) Run install.pl on each server (DB Server last, if I am not mistaken).

However, in your reply (quoted below), do you seem to be saying I can run the the "perl install.pl" command first and the MySQL upgrades after? Does the order of operations matter? Doesn't some of the features brought in with the later SVN versions depend on db schema updates in the MySQL upgrade scripts? Extra fields / tables / indexes in the DB schema would probably be ignored by the old code - but - won't the new code fail until the db schema has the columns that code is expecting to be there? The order that I followed worked perfectly, starting at a 2.10 version from an older 6.x ISO - it's now running v2.14b0.5 / SVN 2971 / DB Schema 1541. Anyway - just curious - thanks for any response...




mflorell wrote:On each server, run the following:
- mkdir /usr/src/astguiclient
- cd /usr/src/astguiclient
- svn checkout svn://svn.eflo.net:3690/agc_2-X/trunk
- cd trunk
- perl install.pl

Although, you will also need to separately update the Database Schema, this is done using the sql upgrade files found in the "extras" directory depending on the version you are upgrading from.(this is basically the instructions from the UPGRADE document)
mysql
use asterisk
\. /path/from/root/extras/upgrade_2.8.sql
\. /path/from/root/extras/upgrade_2.10.sql
\. /path/from/root/extras/upgrade_2.12.sql
\. /path/from/root/extras/upgrade_2.14.sql
quit

Re: Vicidial Update (SVN)

PostPosted: Sun Jun 10, 2018 8:16 am
by mflorell
Yes, you should always upgrade the database first. I'll make sure I edit my post above and add that note.