Skip to content

GS 5.2-beta4-develop: Datenbankschema unvollständig #330

@ip6li

Description

@ip6li

Nach Installation von GS 5.2-beta4-develop und Import eines Backups erscheinen folgende Fehlermeldungen bei Auf- bzw. Abbau einer Verbindung:

2014-05-30 09:41:45.014649 [ERR] switch_odbc.c:514 ERR: [INSERT INTO call_histories (callee_account_id, callee_id_name, caller_id_number, caller_id_name, forwarding_service, call_historyable_id, result, entry_type, auth_account_id, updated_at, caller_account_id, caller_account_type, created_at, clir, call_historyable_type, destination_number, duration, callee_id_number, start_stamp, callee_account_type, auth_account_type, caller_channel_uuid) VALUES ("1", "520", "_", "", NULL, 1, "NORMAL_CLEARING", "received", NULL, NOW(), NULL, NULL, NOW(), FALSE, "SipAccount", "+**", "8", "+_", FROM_UNIXTIME(1401435692), "SipAccount", NULL, "ca5273c1-eb39-46cd-9856-e217240b2bee")]
[STATE: 42S22 CODE 1054 ERROR: [unixODBC][MySQL][ODBC 5.1 Driver][mysqld-5.5.37-0+wheezy1]Unknown column 'clir' in 'field list'
]
2014-05-30 09:41:45.014649 [ERR] switch_core_sqldb.c:586 ODBC SQL ERR [STATE: 42S22 CODE 1054 ERROR: [unixODBC][MySQL][ODBC 5.1 Driver][mysqld-5.5.37-0+wheezy1]Unknown column 'clir' in 'field list'
]
INSERT INTO call_histories (callee_account_id, callee_id_name, caller_id_number, caller_id_name, forwarding_service, call_historyable_id, result, entry_type, auth_account_id, updated_at, caller_account_id, caller_account_type, created_at, clir, call_historyable_type, destination_number, duration, callee_id_number, start_stamp, callee_account_type, auth_account_type, caller_channel_uuid) VALUES ("1", "520", "
", "**", NULL, 1, "NORMAL_CLEARING", "received", NULL, NOW(), NULL, NULL, NOW(), FALSE, "SipAccount", "+_", "8", "+", FROM_UNIXTIME(1401435692), "SipAccount", NULL, "ca5273c1-eb39-46cd-9856-e217240b2bee")
2014-05-30 09:41:45.014649 [ERR] freeswitch_lua.cpp:446 DBH NOT Connected.
2014-05-30 09:41:45.014649 [ERR] switch_cpp.cpp:1288 #E# ["ca5273c1-eb39-46cd-9856-e217240b2bee"] CALL_HISTORY_SAVE - SQL: INSERT INTO call_histories (callee_account_id, callee_id_name, caller_id_number, caller_id_name, forwarding_service, call_historyable_id, result, entry_type, auth_account_id, updated_at, caller_account_id, caller_account_type, created_at, clir, call_historyable_type, destination_number, duration, callee_id_number, start_stamp, callee_account_type, auth_account_type, caller_channel_uuid) VALUES ("1", "520", "**
", "_", NULL, 1, "NORMAL_CLEARING", "received", NULL, NOW(), NULL, NULL, NOW(), FALSE, "SipAccount", "+", "8", "+**", FROM_UNIXTIME(1401435692), "SipAccount", NULL, "ca5273c1-eb39-46cd-9856-e217240b2bee")

Workaround:

mysql --password=$(cat /root/.mysql_root_password)
mysql> use gemeinschaft;
mysql> ALTER TABLE cdrs ADD forwarding_path varchar(256);
mysql> ALTER TABLE call_histories ADD clir boolean;

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions