Different SVNs on same cluster

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Different SVNs on same cluster

Postby Chuckferd » Thu Feb 14, 2019 2:53 pm

Curious if anyone can answer this,

I have a cluster that we upgraded the DB Server SVN, but not Schema, all web servers, and all dialers.

We added a few dialers, however, since the vici install that we used was just a bit lower in SVN I ran "svn up" and install.pl. I don't have any obvious issues, however, I want to be sure that I shouldn't expect any in the future.

vicidial reports page is now showing that my dialers are mostly SVN: 3059, except 3. DB1 is 3059.

System Setting is shwoing that the current SVN Version is: 3063.

1) Will this cause an issue?
2) Is there a way to add a dialer and only update to a specific svn?

thanks so much for the assistance.
Chuck

Vicibox 8.0.1
Version: 2.14b0.5
SVN Version: 3063
DB Schema Version: 1562
Chuckferd
 
Posts: 12
Joined: Mon Jan 30, 2017 11:30 am

Re: Different SVNs on same cluster

Postby williamconley » Thu Feb 14, 2019 3:02 pm

SVN revision level is not always proof of installed Vicidial code. (LIkely, but not proof.) Since it's possible to copy using scp or rsync or other methods to the requisite live file locations, and the SVN folder is not used for anything directly except "storage". It's also possible to "svn up" without "install.pl", which would obviously mean the Live code was not yet installed. So "svn info" may, or may not, actually be an accurate representation of the code that is installed on the server.

However: The bottom left corner of the Admin.php page shows the Vicidial Version With Build.

Now that is out of the way: You MUST have the same Vicidial Version (With Build) installed on all servers in a cluster. You'll eventually have problems if you don't. Of course the easiest way to make that happen is to have the same SVN on all and use install.pl when at the same SVN revision level.

Additionally, the installed version of the code must match the DB Schema of the DB server. The easiest way to be sure that's done is to use the UPGRADE document instructions and use the upgrade .sql file from the same SVN revision level just installed.

Feel free to wander around the ledge on top of the skyscraper if you like, but when you fall we'll all say "yep, that was gonna happen". 8-)
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20018
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Different SVNs on same cluster

Postby jkidd » Tue Sep 01, 2020 5:47 am

WC what is wrong with you? What happened?
VERSION: 2.14-697a | BUILD: 190121-2019 Asterisk Version 13.21.1-vici | cluster 1 DB 4 web / diallers
jkidd
 
Posts: 83
Joined: Wed Apr 23, 2014 9:38 am


Return to Support

Who is online

Users browsing this forum: Bing [Bot], Majestic-12 [Bot] and 90 guests