Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
- Code: Select all
Unknown column 'na_call_url' in 'where clause' at /usr/share/astguiclient/AST_VDauto_dial.pl line 2772.
'' as fieldname
williamconley wrote:missing is an interesting description. you could restore a previous backup set (to a DB other than asterisk to avoid damage) and see if those fields WERE present. if you are using the stock vicidial backup, you can also check the backup copy of the autodial script and see if it's been changed.
Possibilities
* Code has been changed to "expect" that field
* that field has been deleted when it was once there
* that script has never actually run
* the server configuration has been altered in such a way that this line of the autodial script is now firing when it previously did not
As a "duct tape" measure, you could (make a backup copy and) change the line noted to remove the field in question. But that field will then be loaded into a variable, so you would then need to delete the creation and use of that variable OR just change the sql code to '' as fieldname (for each) so it would be there, have the same name, and be empty to avoid errors.
- Code: Select all
'' as fieldname
I will note, however, that this really does look like an upgrade. have you run "perl install.pl"? If so, that was the problem ... downgrade the scripts or upgrade the DB.
carpenox wrote:mysql -p -f --database=asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.14.sql
williamconley wrote:Best advice: full backup ... then upgrade. if it fails you can still revert. if it doesn't, you're likely "up" with very little effort.
note that upgrading the db requires running all the commands on the upgrade sql file that have NOT already run. we like to find the db_schema update command that matches the present db_schema (visible admin system settings) and delete all the lines above it (since they have obviously already run). then the rest of the commands should not have an error. if you run the commands that have already run, often there's a conflict (attempting to create an index that already exists, for instance, can stop the script from running).
carpenox wrote:if you go to system settings in admin, does it say anything about wrong DB schema?
tail /usr/src/astguiclient/trunk/extras/upgrade_2.14.sql | grep db_schema_version
mysql -u cron -p1234 asterisk -e "select * from system_settings\G" | grep schema
cd /usr/src/astguiclient/trunk
svn info | grep Revision
svn up -r 2946
cd /usr/src/astguiclient/trunk
perl install.pl --copy_sample_conf_files
Users browsing this forum: No registered users and 167 guests