[XiVO] Salle de conférence

[poukill]

Bonjour à tous,

Je suis récemment reparti d'une installation fraîche 13.13 de XiVO, sur laquelle j'ai restauré mes backups (db et data) comme indiqué dans la doc.
La salle de conférence qui fonctionnait très bien ces derniers mois ne fonctionne plus depuis la réinstallation de XiVO.
WARNING[2744][C-00000001]: app_meetme.c:1285 build_conf: Unable to open DAHDI pseudo device

[Jul 10 11:43:49]     -- Executing [51@default:1] Set("SIP/xxxxxx-00000001", "XIVO_BASE_CONTEXT=default") in new stack
[Jul 10 11:43:49]     -- Executing [51@default:2] Set("SIP/xxxxxx-00000001", "XIVO_BASE_EXTEN=51") in new stack
[Jul 10 11:43:49]   == Extension Changed 20[default] new state InUse for Notify User ignkxw
[Jul 10 11:43:49]     -- Executing [51@default:3] Gosub("SIP/xxxxxx-00000001", "meetme,s,1(1)") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:1] Set("SIP/xxxxxx-00000001", "XIVO_DSTID=1") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:2] Set("SIP/xxxxxx-00000001", "XIVO_PRESUBR_GLOBAL_NAME=MEETME") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:3] UserEvent("SIP/xxxxxx-00000001", "Meetme,CHANNEL: SIP/xxxxxx-00000001,XIVO_USERID: 1,XIVO_DSTID: 1") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:4] Set("SIP/xxxxxx-00000001", "XIVO_SRCNUM=20") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:5] Set("SIP/xxxxxx-00000001", "XIVO_DSTNUM=51") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:6] Set("SIP/xxxxxx-00000001", "XIVO_CONTEXT=default") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:7] AGI("SIP/xxxxxx-00000001", "agi://127.0.0.1/incoming_meetme_set_features") in new stack
[Jul 10 11:43:49]     -- AGI Script Executing Application: (Answer) Options: ()
[Jul 10 11:43:49]        > 0xb49055c0 -- Probation passed - setting RTP source address to 192.168.1.93:56354
[Jul 10 11:43:49]  agi://127.0.0.1/incoming_meetme_set_features: AGI handler 'incoming_meetme_set_features' successfully executed
[Jul 10 11:43:49]     -- <SIP/xxxxxx-00000001>AGI Script agi://127.0.0.1/incoming_meetme_set_features completed, returning 0
[Jul 10 11:43:49]     -- Executing [s@meetme:8] Gosub("SIP/xxxxxx-00000001", "xivo-subroutine,s,1()") in new stack
[Jul 10 11:43:49]     -- Executing [s@xivo-subroutine:1] GotoIf("SIP/xxxxxx-00000001", "?:nosubroutine") in new stack
[Jul 10 11:43:49]     -- Goto (xivo-subroutine,s,4)
[Jul 10 11:43:49]     -- Executing [s@xivo-subroutine:4] Return("SIP/xxxxxx-00000001", "") in new stack
[Jul 10 11:43:49]     -- Executing [s@meetme:9] Gosub("SIP/xxxxxx-00000001", "xivo-pickup,0,1") in new stack
[Jul 10 11:43:49]     -- Executing [0@xivo-pickup:1] Goto("SIP/xxxxxx-00000001", "s,1") in new stack
[Jul 10 11:43:49]     -- Goto (xivo-pickup,s,1)
[Jul 10 11:43:49]     -- Executing [s@xivo-pickup:1] Set("SIP/xxxxxx-00000001", "WAITSEC=1") in new stack
[Jul 10 11:43:49]     -- Executing [s@xivo-pickup:2] Goto("SIP/xxxxxx-00000001", "pickup,1") in new stack
[Jul 10 11:43:49]     -- Goto (xivo-pickup,pickup,1)
[Jul 10 11:43:49]     -- Executing [pickup@xivo-pickup:1] GotoIf("SIP/xxxxxx-00000001", "?return") in new stack
[Jul 10 11:43:49]     -- Executing [pickup@xivo-pickup:2] Answer("SIP/xxxxxx-00000001", "") in new stack
[Jul 10 11:43:49]     -- Executing [pickup@xivo-pickup:3] Wait("SIP/xxxxxx-00000001", "1") in new stack
[Jul 10 11:43:50]     -- Executing [pickup@xivo-pickup:4] Set("SIP/xxxxxx-00000001", "XIVO_PICKEDUP=1") in new stack
[Jul 10 11:43:50]     -- Executing [pickup@xivo-pickup:5] Return("SIP/xxxxxx-00000001", "") in new stack
[Jul 10 11:43:50]     -- Executing [s@meetme:10] Gosub("SIP/xxxxxx-00000001", "xivo-global-subroutine,s,1") in new stack
[Jul 10 11:43:50]     -- Executing [s@xivo-global-subroutine:1] GotoIf("SIP/xxxxxx-00000001", "1?:return") in new stack
[Jul 10 11:43:50]     -- Executing [s@xivo-global-subroutine:2] GotoIf("SIP/xxxxxx-00000001", "MEETME?:return") in new stack
[Jul 10 11:43:50]     -- Executing [s@xivo-global-subroutine:3] GotoIf("SIP/xxxxxx-00000001", "xivo-subrgbl-meetme?:return") in new stack
[Jul 10 11:43:50]     -- Executing [s@xivo-global-subroutine:4] GotoIf("SIP/xxxxxx-00000001", "0?:return") in new stack
[Jul 10 11:43:50]     -- Goto (xivo-global-subroutine,s,6)
[Jul 10 11:43:50]     -- Executing [s@xivo-global-subroutine:6] Return("SIP/xxxxxx-00000001", "") in new stack
[Jul 10 11:43:50]     -- Executing [s@meetme:11] Gosub("SIP/xxxxxx-00000001", "originate-caller-id,s,1") in new stack
[Jul 10 11:43:50]     -- Executing [s@originate-caller-id:1] GotoIf("SIP/xxxxxx-00000001", "0?:name") in new stack
[Jul 10 11:43:50]     -- Goto (originate-caller-id,s,3)
[Jul 10 11:43:50]     -- Executing [s@originate-caller-id:3] GotoIf("SIP/xxxxxx-00000001", "0?:end") in new stack
[Jul 10 11:43:50]     -- Goto (originate-caller-id,s,5)
[Jul 10 11:43:50]     -- Executing [s@originate-caller-id:5] Return("SIP/xxxxxx-00000001", "") in new stack
[Jul 10 11:43:50]     -- Executing [s@meetme:12] MeetMe("SIP/xxxxxx-00000001", "51,cM,") in new stack
[Jul 10 11:43:50]   == Parsing '/etc/asterisk/meetme.conf': Found
[Jul 10 11:43:50]   == Parsing '/var/tmp/exec.137344943071932.-1263649936': Found
[Jul 10 11:43:50] WARNING[2744][C-00000001]: app_meetme.c:1285 build_conf: Unable to open DAHDI pseudo device
[Jul 10 11:43:50]   == Spawn extension (meetme, s, 12) exited non-zero on 'SIP/xxxxxx-00000001'

Ça sent un problème avec DAHDI, mais ça marchait très bien avant. C'est la restauration des backups ?

[poukill]

effectivement, DAHDI est pas vivant...

root@xivo:~# xivo-service status
Checking databases...
        OK              asterisk db
        OK              xivo db
Checking services...
        stopped         dahdi
        running         rabbitmq-server
        running         xivo-sysconfd
        running         xivo-confgend
        running         xivo-dxtora
        running         xivo-provd
        running         xivo-agid
        running         asterisk
        running         xivo-agent
        running         xivo-ctid
        running         xivo-restapi

root@xivo:/etc/dahdi# /etc/init.d/dahdi start
No DAHDI modules on the system. Not starting

J'ai l'impression que DAHDI n'est pas installé. Comment faire ?

[poukill]

Bon, j'ai tout simplement fait l'installation du paquet dahdi-linux-modules-2.6.32-5-686 (qui correspond à mon noyau). Il avait dahdi-linux en dépendance.
Et ça marche.
Mais c'était pas supposé être installé par défaut ? Pour ma dernière installation je n'avais pas eu besoin de ça.

[quintana]

Si c'est installé par défaut normalement, tu as installé via l'ISO ?

[poukill]

Oui, je l'ai installé par l'ISO (13.13 en mode Guided LVM ).

[sduthil]

Tu pourrais regarder dans les fichiers de log /var/log/apt/term.log* s'il n'y a pas eu une erreur lors de l'installation de dahdi-linux-modules-2.6.32-5-686 ?

[poukill]

RAS

Log started: 2013-07-10  15:39:17
Selecting previously deselected package dahdi-linux.^M
(Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 40062 files and directories currently installed.)^M
Unpacking dahdi-linux (from .../dahdi-linux_2%3a2.7.0+pf.xivo.13.13~20130625.133816.231444d-1_all.deb) ...^M
Selecting previously deselected package dahdi-linux-modules-2.6.32-5-686.^M
Unpacking dahdi-linux-modules-2.6.32-5-686 (from .../dahdi-linux-modules-2.6.32-5-686_2%3a2.7.0+pf.xivo.13.12~20130611.141319.2de1580-1+2.6.32-48squeeze3_i386.deb) ...^M
Setting up dahdi-linux (2:2.7.0+pf.xivo.13.13~20130625.133816.231444d-1) ...^M
Setting up dahdi-linux-modules-2.6.32-5-686 (2:2.7.0+pf.xivo.13.12~20130611.141319.2de1580-1+2.6.32-48squeeze3) ...^M
Log ended: 2013-07-10  15:39:21

[sduthil]

Tu pourrais essayer de retrouver, dans le même fichier/archives du fichier, les messages de l'installation de XiVO et voir si l'installation de dahdi-linux-modules a échoué à ce moment là ?

[poukill]

J'ai rien trouvé.
Dans dpkg.log, tout devrait s'être bien passé.

2013-07-08 17:10:43 install perl <none> 5.10.1-17squeeze6
2013-07-08 17:10:43 status half-installed perl 5.10.1-17squeeze6
2013-07-08 17:10:44 status half-installed perl 5.10.1-17squeeze6
2013-07-08 17:10:45 status unpacked perl 5.10.1-17squeeze6
2013-07-08 17:10:45 status unpacked perl 5.10.1-17squeeze6
2013-07-08 17:10:45 install dahdi <none> 12:2.7.0+pf.xivo.13.13~20130625.133816.231444d-1
2013-07-08 17:10:45 status half-installed dahdi 12:2.7.0+pf.xivo.13.13~20130625.133816.231444d-1
2013-07-08 17:10:45 status half-installed dahdi 12:2.7.0+pf.xivo.13.13~20130625.133816.231444d-1
2013-07-08 17:10:45 status unpacked dahdi 12:2.7.0+pf.xivo.13.13~20130625.133816.231444d-1
2013-07-08 17:10:45 status unpacked dahdi 12:2.7.0+pf.xivo.13.13~20130625.133816.231444d-1
// La suite plus loin

/var/log/history.log :

Install: python-crypto:i386 (2.1.0-2+squeeze1, automatic), python-twisted-names:i386 (10.1.0-1, automatic), libical0:i386 (0.44-3, automatic), python-pyasn1:i386 (0.0.11a-1, automatic), ttf-dejavu-core:i386 (2.31-1, automatic), xivo-libdao:i386 (13.13~20130704.201407.76b7ceb-1, automatic), hdparm:i386 (9.32-1, automatic), libjs-jquery-ui:i386 (1.8.dgsf.11+pf-backport-1, automatic), python-twisted-core:i386 (10.1.0-3, automatic), python-ldap:i386 (2.3.11-1, automatic), munin-common:i386 (1.4.5-3, automatic), xivo-agent:i386 (13.13~20130514.151055.c1c242b-1, automatic), libpth20:i386 (2.0.7-16, automatic), libxcb-render-util0:i386 (0.3.6-1, automatic), python-support:i386 (1.0.10, automatic), libneon27:i386 (0.29.3-3, automatic), python2.6-minimal:i386 (2.6.6-8+b1, automatic), erlang-erl-docgen:i386 (14.a-dfsg-3squeeze1, automatic), libiksemel3:i386 (1.2-4, automatic), munin:i386 (1.4.5-3, automatic), mime-support:i386 (3.48-1, automatic), libcurses-perl:i386 (1.28-1, automatic), libidn11:i386 (1.15-2, automatic), erlang-inets:i386 (14.a-dfsg-3squeeze1, automatic), erlang-asn1:i386 (14.a-dfsg-3squeeze1, automatic), libsensors4:i386 (3.1.2-6, automatic), erlang-webtool:i386 (14.a-dfsg-3squeeze1, automatic), python-zope.interface:i386 (3.5.3-1+b1, automatic), libsnmp15:i386 (5.4.3~dfsg-2, automatic), libyaml-syck-perl:i386 (1.12-1, automatic), dahdi:i386 (2.7.0+pf.xivo.13.13~20130625.133816.231444d-1, automatic), libnet-netmask-perl:i386 (1.9015-4, automatic), libsrtp0:i386 (1.4.4~dfsg-6, automatic), libcrypt-ssleay-perl:i386 (0.57-2, automatic),

Je vois rien de bizarre...