vicidial upgrade , lists tab mysql error

[raloheni]

Hi

i have upgraded my vicidial to latest svn trunk version today

my old vicidial version 2.2-xxx | vicibox ubuntu version|single server |no extra softwares
after upgade its version is 2.4-272

once i click the lists tab i am getting the following error on top
mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /var/www/vicidial/admin.php on line 20344

if i click campaign following error on top
Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /var/www/vicidial/admin.php on line 17526

[okli]

Did you follow UPGRADE document?
What did you do exactly?

[williamconley]

did you follow the upgrade document and upgrade your SQL data in addition to your web files? (the install.pl script will update all your web files, but you must run the sql command as well).

and did you reboot afterwards! LOL

[raloheni]

hi
i have followed the upgrade doc

first i did the mysql script
and then the install.pl.

and also rebooted sevarel times.

but same error is displaying

[williamconley]

What did you do exactly?

I think he's right, we'll need the actual commands executed and the directories you were in when you executed them if they weren't using absolute paths.

use the history command if you need to

also, did you have any errors during this process?

[raloheni]

hi
i followed the same as in UPGRADE.txt
but one thing in first step if type only mysql , an error displayed permission denied for root with no password so typed like mysql -p and entered my root password.

1. upgrade the MySQL asterisk database:
mysql
use asterisk
\. /path/from/root/extras/upgrade_2.4.sql
quit

2. install new files:
perl ./install.pl
NOTES: If you have customized any scripts in the bin or agi folders,
then make sure you back them up before running the install.pl script.
This script will replace existing files in the astguiclient installation.

3. For each of your ViciDial servers, go the Admin -> Servers -> Modify Server
page and set each one to "Rebuild conf files = Y" and click submit.
This will rebuild the conf files to ensure any changes are updated.

[raloheni]

hi

because of this error i am not able to create the campaigns.
after submitting i am getting the same mysql error .

[williamconley]

\. /path/from/root/extras/upgrade_2.4.sql

is this what you actually entered?

[raloheni]

i entered right one

\. /usr/src/astguicllient/tunks/extras/upgrade-2.4.sql

it didnt give any error

[williamconley]

could you use the "history" command and copy/paste the actual commands? (just for the sake of argument ...)

all of them (skip anything not related to the upgrade, of course, but include "cd" and anything else that is necessary).

did you also tell it to copy .conf files?

do you have any modified .conf files that would cause you to "not" copy .conf files?

[raloheni]

474 svn checkout svn://svn.eflo.net:3690/agc_2-X/trunk
475 ls
476 cd trunk/
477 ls
478 vi UPGRADE
479 cd /usr/src/astguiclient/trunk/
480 /usr/share/astguiclient/ADMIN_update_server_ip.pl
481 mysql
482 mysql -p
483 perl ./install.pl
484 cd /usr/src/astguiclient/trunk/
485 ls
486 vi UPGRADE

[williamconley]

I note that you ran the IP update script before installing the new code (although if you had done this before, the new code may have been there already). which leads me to believe you may have had other things going on besides just an upgrade (unless you were just doing that because the system was broken from the upgrade and you were hoping it would help).

i'm not sure that script would cause dead database under any circumstances.

you may want to consider dumping your vicidial_list table into a .sql file (using mysqldump) and reloading everything else as "clean" database. then make sure everything is working and reload your "list". you may need to make structural changes to your list to be sure it matches the "stock" vicidial_list table structure from 2.4 (which you will have access to before you reload yours).

in fact, i'd recommend dumping the entire database as a quick backup into a sql file, and then again just dump the vicidial_list table into another file, so you have them both and seperate for testing. and get them off the box as well in case you have to "wipe it" (and it's a backup of your data!)

then load a fresh database and see if the system runs. if not, reinstall vicidial code AND the database again at the same time so they match. if that doesn't do it, you have either a fundamental understanding issue (something we think it obvious so we do not mention it) or there is something truly strange about your system. at that point, i'd reinstall from .iso just to be sure.

[okli]

...my old vicidial version 2.2-xxx ...

How did you install that one? Was it in SVN or where did you get the files from?

My point is that when upgrading from SVN versions you'd need to check db_schema_version in system_settings table and run only the SQL queries after it. If you didn't upgrade from a stable version, then you might have missed some queries or run them twice if you haven't run the rightt part of the upgradeXXX.sql files.

[raloheni]

Hi

this was my old vicibox running more than a year
in the begining it was 2.0.5
and 6 months before i upgraded to 2.2.1 .
and then now i tried to upgrade from 2.2.1 to 2.4 ,due to the need for the coustom agent fields.

@okli
" run only the SQL queries after it. If you didn't upgrade from a stable version, then you might have missed some queries or run them twice if you haven't run the rightt part of the upgradeXXX.sql files."

if i run only the sql queries shall i get that coustom field option for agents window.
any how i have acronis backup of my server so i will restore it and test only the sql queris.
thanks for your help

[/quote]

[okli]

When you restore from a backup go to ADMIN page-->ADMIN-->SYSTEM SETTINGS and post here the contents of Version and DB Schema Version values before proceeding with the upgrade.

[raloheni]

hi okli

i have resoted my backup

and this the details you asked
Version: 2.2.0b0.5
DB Schema Version: 1188

[okli]

From UPGRADE_2.2.0.sql you need to run only the commands BELOW this line:

Code: Select all

UPDATE system_settings SET db_schema_version='1188',db_schema_update_date=NOW();

in other words remove that line and everything ABOVE it and follow upgrade instructions.

Next is the whole file upgrade_2.4.sql.

[raloheni]

hi okli

as per you i run this cmd in mysql and i started the upgrade 2.4sql but same error

UPDATE system_settings SET db_schema_version='1188',db_schema_update_date=NO


i cant get you in this

"in other words remove that line and everything ABOVE it and follow upgrade instructions."

were to remove it


on thing i am confussed
in UPGRADE file
for 2.2.0 to 2.4 they give
first run this \. /usr/src/astguiclient/trunk/extras/upgrade.2.4.sql
and then run perl install.pl

but for for 2.0.5 to 2.2.0
they give it in reverse
which one is correct

[okli]

Edit /usr/src/astguiclient/trunk/extras/UPGRADE_2.2.0.sql and remove the lines mentioned, ABOVE and including this one

Code: Select all

UPDATE system_settings SET db_schema_version='1188',db_schema_update_date=NOW();

Next follow upgrade instructions.