Beiträge durchsuchen

[Asterisk] – I/O Error – Leitungen unregestriert

Es kann in extrem seltenen Fällen vorkommen, dass in der Log-Datei ein I/O Error auftaucht. In diesem Fall (siehe unten) ist die Asterisk Datenbank deffekt.

Alle Leitungen lassen sich von heute auf morgen nicht mehr regestrieren.

Es erscheinen in der PBX-Log folgende Einträge:

Nov 6 14:09:33] VERBOSE[16775] chan_iax2.c: — Unregistered IAX2 ‘ttyIAX2’ (AU[Nov 6 14:10:40] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 14:10:40] VERBOSE[2158] config.c: == Parsing ‘/etc/asterisk/logger.conf’: Found
[Nov 6 14:10:40] VERBOSE[2158] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 14:10:40] WARNING[2158] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 14:10:40] WARNING[2158] db.c: Couldn’t create astdb table: disk I/O error
[Nov 6 14:13:46] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 14:13:46] VERBOSE[4102] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 14:13:46] WARNING[4102] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 14:13:46] WARNING[4102] db.c: Couldn’t create astdb table: disk I/O error
[Nov 6 14:19:46] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 14:19:46] VERBOSE[4403] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 14:19:46] WARNING[4403] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 14:19:46] WARNING[4403] db.c: Couldn’t create astdb table: disk I/O error
[Nov 6 14:29:25] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 14:29:25] VERBOSE[2129] config.c: == Parsing ‘/etc/asterisk/logger.conf’: Found
[Nov 6 14:29:25] VERBOSE[2129] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 14:29:25] WARNING[2129] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 14:29:25] WARNING[2129] db.c: Couldn’t create astdb table: disk I/O error
[Nov 6 14:32:31] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 14:32:31] VERBOSE[4108] config.c: == Parsing ‘/etc/asterisk/logger.conf’: Found
[Nov 6 14:32:31] VERBOSE[4108] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 14:32:32] WARNING[4108] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 14:32:32] WARNING[4108] db.c: Couldn’t create astdb table: disk I/O error
[Nov 6 14:38:31] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 14:38:31] VERBOSE[4394] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 14:38:31] WARNING[4394] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 14:38:31] WARNING[4394] db.c: Couldn’t create astdb table: disk I/O error
[Nov 6 14:50:31] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 14:50:32] VERBOSE[4873] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 14:50:32] WARNING[4873] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 14:50:32] WARNING[4873] db.c: Couldn’t create astdb table: disk I/O error
[Nov 6 15:14:32] Asterisk 11.25.1 built by tyskieplusplus @ buildsys on a x86_64 running Linux on 2017-03-08 15:39:03 UTC
[Nov 6 15:14:32] VERBOSE[5799] config.c: == Parsing ‘/etc/asterisk/logger.conf’: Found
[Nov 6 15:14:32] VERBOSE[5799] config.c: == Parsing ‘/etc/asterisk/asterisk.conf’: Found
[Nov 6 15:14:32] WARNING[5799] db.c: Couldn’t prepare statement ‘CREATE TABLE IF NOT EXISTS astdb(key VARCHAR(256), value VARCHAR(256), PRIMARY KEY(key))’: disk I/O error
[Nov 6 15:14:32] WARNING[5799] db.c: Couldn’t create astdb table: disk I/O error

In diesem Fall ist die Datenbank des Asterisk defekt.

  1. In /var/lib/asterisk/ die Datenbank-Files umbenennen:[root@pbx ~]# cd /var/lib/asterisk/
    [root@pbx asterisk]# mv astdb astdb.old
    [root@pbx asterisk]# mv astdb.sqlite3 astdb.sqlite3.old
    [root@pbx asterisk]# mv astdb.sqlite3-journal astdb.sqlite3-journal.oldDanach sieht der Verzeichnisinhalt wie folgt aus:

    [root@pbx asterisk]# ll
    total 80
    drwxr-xr-x. 2 asterisk asterisk 4096 Mar 8 2017 agi-bin
    -rw-r–r– 1 asterisk asterisk 16384 Feb 23 2015 astdb.old
    -rw-r–r– 1 asterisk asterisk 6704 Nov 6 14:09 astdb.sqlite3-journal.old
    -rw-r–r– 1 asterisk asterisk 29696 Nov 6 17:30 astdb.sqlite3.old
    drwxr-xr-x 2 asterisk asterisk 4096 May 26 15:44 documentation
    drwxr-xr-x. 3 root root 4096 May 26 15:44 firmware
    drwxr-xr-x. 2 asterisk asterisk 4096 Mar 8 2017 keys
    drwxr-xr-x. 5 root root 4096 Jan 13 2016 sounds

  2. Asterisk neu gestartet:[root@pbx asterisk]# service asterisk restart
    Shutting down Asterisk PBX: [FAILED]
    Starting Asterisk PBX: [ OK ]
  3. Datenbank wurde neu angelegt:

[root@pbx asterisk]# ll
total 84
drwxr-xr-x. 2 asterisk asterisk 4096 Mar 8 2017 agi-bin
-rw-r–r– 1 asterisk asterisk 16384 Feb 23 2015 astdb.old
-rw-r–r– 1 asterisk asterisk 3072 Nov 6 17:32 astdb.sqlite3
-rw-r–r– 1 asterisk asterisk 6704 Nov 6 14:09 astdb.sqlite3-journal.old
-rw-r–r– 1 asterisk asterisk 29696 Nov 6 17:30 astdb.sqlite3.old
drwxr-xr-x 2 asterisk asterisk 4096 May 26 15:44 documentation
drwxr-xr-x. 3 root root 4096 May 26 15:44 firmware
drwxr-xr-x. 2 asterisk asterisk 4096 Mar 8 2017 keys
drwxr-xr-x. 5 root root 4096 Jan 13 2016 sounds

Alle Leitungen sollten sich jetzt wieder regestrieren lassen.

Schreibe einen Kommentar