Page 1 of 1

vicidial migration problems

PostPosted: Tue Feb 26, 2013 4:25 am
by bcddd214
in a rescue situation, I am trying to transfer vici dial to another server.
I downloaded the latest iso, got vicidial up and running and even logged in, copied the mysql database and replace the asterisk and mysql tables with the old tables, copied the asterisk config files and replaced those. I should be good to go but I get this error now ->

MySQL connect ERROR: mysqlnd cannot connect to MySQL 4.1+ using the old insecure authentication. Please use an administration tool to reset your password with the command SET PASSWORD = PASSWORD('your_existing_password'). This will store a new, and more secure, hash value in mysql.user. If this user is used in other scripts executed by PHP 5.2 or earlier you might need to remove the old-passwords flag from your my.cnf file

I can log into mysql as root and see all the data just fine.
what/where password would it be choking on?

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 5:31 am
by Vince-0
Please post your system vitals/versions as per this thread:
http://vicidial.org/VICIDIALforum/viewtopic.php?f=4&t=443

You can't just move an old database into a new installation. There will be vicidial database (asterisk) schema incompatibilities and you should upgrade your existing schema (taking backups) before copying it to a new install. I also suggest that you only copy the asterisk database folder and not the mysql database folder because that will also have incompatibilities with a newer version of MySQL server. What versions of MySQL are you using?

--
Vincent

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 11:11 am
by bcddd214
Server version: 5.5.28-log Source distribution
VICIbox 64-bit Standard
Linux li592-167 3.7.5-x86_64-linode29 #1 SMP Thu Jan 31 14:42:22 EST 2013 x86_64 x86_64 x86_64 GNU/Linux


1) Version of VICIDIAL -(what ever comes on the disk, can't get to it.
2) loadavg -0%$
3) Server Specs -VPS tiny menmory but burstable
4) Codecs used -none
5) VOIP or PSTN -pure SIP
6) OS -check your disk

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 11:12 am
by bcddd214
How do I get the version of the old if I only have the database?
How do I upgrade just the database scheme?
Can it be done manually?

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 11:20 am
by Vince-0
Let me Google that for you:
http://wiki.vicidial.org/index.php/SVN:howto

Link at the bottom of the page has clear instructions. See docs contained in the docs folder.

Depending on your database ?version? you execute database schema changes EG:
/usr/src/astguiclient/trunk/extras/upgrade_2.6.sql

--
Vin

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 4:16 pm
by bcddd214
li592-167:~ # mysql -u root -p'duck' asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.6.sql
ERROR 1054 (42S22) at line 34: Unknown column 'is_webphone' in 'phones'

any thoughts?

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 4:18 pm
by bcddd214
my previous version was 2.2.1-237
build 100510-2015

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 4:25 pm
by Vince-0
You need to do the 2.2 to 2.4 upgrade then from 2.4. to 2.6 .

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 8:58 pm
by williamconley
there is a document called UPGRADE that you should be reading, with explicit instructions in the downloaded code as well. it describes the upgrade from any prior version. remember that the sql database is all that is really being "upgraded", the vicidial code itself is ReInstalled over top of the old code.

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 9:10 pm
by bcddd214
Is there an easier way to pull the old data and configuration into a new vicidial installation?
Plugging in the old database is just not working out.

Re: vicidial migration problems

PostPosted: Tue Feb 26, 2013 9:51 pm
by williamconley
you could mysqldump your old leads and re-import them with the command line lead loader. but you'll lose all linked data with all leads unless you DROP the database, CREATE the database (asterisk), then mysql in the old DB (this means the entire DB is now just OLD data, nothing from the newer install to interfere ...). Then you follow the directions to upgrade that data to the latest version and Bob's your uncle. We don't do this for free for clients, because it does take some time, but we don't charge a lot because it's not that much time and it never fails unless your DB is corrupt or has been Customized (which means: broken).