Reinicio Asterisk

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#1
miren tengo este problema mi servicio asterisk se reinicia sin ningún aviso previo o problema.

Y reviso con core show uptime y me muestra el tiempo que esta arriba mi asterisk a veces varia puede estar un dia bien o media hora bien.


[Mar 24 09:28:57] VERBOSE[28106] pbx.c: -- Executing [s@macro-dial-one:31] ExecIf("DAHDI/38-1", "0?SIPAddHeader(Alert-Info: )") in new$
[Mar 24 09:28:57] VERBOSE[28106] pbx.c: -- Executing [s@macro-dial-one:32] ExecIf("DAHDI/38-1", "0?SIPAddHeader()") in new stack
[Mar 24 09:28:57] VERBOSE[28106] pbx.c: -- Executing [s@macro-dial-one:33] ExecIf("DAHDI/38-1", "0?Set(CHANNEL(musicclass)=)") in new $
[Mar 24 09:28:57] VERBOSE[28106] pbx.c: -- Executing [s@macro-dial-one:34] GosubIf("DAHDI/38-1", "0?qwait,1") in new stack
[Mar 24 09:28:57] VERBOSE[28106] pbx.c: -- Executing [s@macro-dial-one:35] Set("DAHDI/38-1", "__CWIGNORE=") in new stack
[Mar 24 09:28:57] VERBOSE[28106] pbx.c: -- Executing [s@macro-dial-one:36] Set("DAHDI/38-1", "__KEEPCID=TRUE") in new stack
[Mar 24 09:28:57] VERBOSE[28106] pbx.c: -- Executing [s@macro-dial-one:37] Dial("DAHDI/38-1", "SIP/1341,,tr") in new stack
[Mar 24 09:28:57] VERBOSE[28106] netsock.c: == Using SIP RTP TOS bits 184
[Mar 24 09:28:57] VERBOSE[28106] netsock.c: == Using SIP RTP CoS mark 5
[Mar 24 09:28:57] VERBOSE[28106] netsock.c: == Using SIP VRTP TOS bits 136
[Mar 24 09:28:57] VERBOSE[28106] netsock.c: == Using SIP VRTP CoS mark 6
[Mar 24 09:28:57] VERBOSE[28106] netsock.c: == Using UDPTL TOS bits 184
[Mar 24 09:28:57] VERBOSE[28106] netsock.c: == Using UDPTL CoS mark 5
[Mar 24 09:28:57] VERBOSE[28106] app_dial.c: -- Called 1341
[Mar 24 09:29:02] VERBOSE[28127] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log
[Mar 24 09:29:02] VERBOSE[28127] config.c: == Parsing '/etc/asterisk/asterisk.conf': [Mar 24 09:29:02] VERBOSE[28127] config.c: == Fou$
[Mar 24 09:29:02] VERBOSE[28127] loader.c: Asterisk Dynamic Loader Starting:
[Mar 24 09:29:02] VERBOSE[28127] config.c: == Parsing '/etc/asterisk/modules.conf': [Mar 24 09:29:02] VERBOSE[28127] config.c: == Found
[Mar 24 09:29:02] NOTICE[28127] loader.c: 2 modules will be loaded.
[Mar 24 09:29:02] VERBOSE[28127] config.c: == Parsing '/etc/asterisk/extensions.conf': [Mar 24 09:29:02] VERBOSE[28127] config.c: == F$
[Mar 24 09:29:02] VERBOSE[28127] config.c: == Parsing '/etc/asterisk/extensions_override_freepbx.conf': [Mar 24 09:29:02] VERBOSE[28127]$
[Mar 24 09:29:02] VERBOSE[28127] config.c: == Parsing '/etc/asterisk/extensions_additional.conf': [Mar 24 09:29:02] VERBOSE[28127] confi$
[Mar 24 09:29:02] VERBOSE[28127] config.c: == Parsing '/etc/asterisk/globals_custom.conf': [Mar 24 09:29:02] VERBOSE[28127] config.c: $
[Mar 24 09:29:02] VERBOSE[28127] config.c: == Parsing '/etc/asterisk/extensions_custom.conf': [Mar 24 09:29:02] VERBOSE[28127] config.c:$

[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'FMDEVSTATE' to 'TRUE'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'DNDDEVSTATE' to 'TRUE'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'QUEDEVSTATE' to 'TRUE'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'CFDEVSTATE' to 'TRUE'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'INTERCOMCODE' to '*80'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'CFDEVSTATE' to 'TRUE'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'INTERCOMCODE' to '*80'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'CALLFILENAME' to '""'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'DIAL_OPTIONS' to 'tr'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'TRUNK_OPTIONS' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'DIAL_OUT' to '9'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'FAX' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'FAX_RX' to 'system'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'FAX_RX_EMAIL' to 'fax@mydomain.com'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'FAX_RX_FROM' to 'freepbx@gmail.com'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'INCOMING' to 'group-all'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'NULL' to '""'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'OPERATOR' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'OPERATOR_XTN' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'PARKNOTIFY' to 'SIP/200'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'RECORDEXTEN' to '""'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'RINGTIMER' to '30'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'DIRECTORY' to 'both'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'AFTER_INCOMING' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'IN_OVERRIDE' to 'forcereghours'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'REGTIME' to '7:55-17:05'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'REGDAYS' to 'mon-fri'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'DIRECTORY_OPTS' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'DIALOUTIDS' to '1'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'VM_PREFIX' to '*'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'VM_OPTS' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'VM_GAIN' to ''
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'VM_DDTYPE' to 'u'
[Mar 24 09:29:02] VERBOSE[28127] pbx.c: == Setting global variable 'TIMEFORMAT' to 'kM'
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#2
hoy te toca castigoooooooooooooo por marmota
y somos magos para saber que version tenes????? sin es un bug reportado o que
fijaet en /tmp a ver si tenes files coredump si es asi son segmentation faults de asterisk o deadlocks...toca ercompilar versiones mas nuevas porque esta erpleto la 1.6
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#3
Uy lo siento la emoción de postear :). Revise los bugs y no encontre nada parecido mi version es Asterisk 1.6.2.13.

Y lo peor viste que no me muestre ni un warning ni nada.
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#4
Fernando si tengo archivos core, y a que te refieres con que esta repleto 1.6??? Entonces me tocara recompilar a mano o como se dice reinstalar nativamente???
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#5
sep porque claramenet tenes algo o de hard o de soft que hace segmentation faults...basicamente lo que te pasa es la pantalla azul de windows en asterisk
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#6
Y alguna recomendacion? a que puedo pasarme, quiero decir que le instalo ahora nunca me paso este problema.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#7
1.6.2.17 o probate asterisk 1.8
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#8
Me late mas la 1.6.2.17 que la 1.8 es que la 1.8 tienes mas bugs con la interface de elastix.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#9
quien te dijo eso??? que bugs....estas habalndo con quien invento el termino deselastixar y con 1.8.-....
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#10
Haber vamos a probar la 1.8 haber k onda. Gracias por la recomendación.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#11
el que no testea no aprendeeeee
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#12
y opne vos tambien karma positivooosss
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#13
jajajajaj Listo ya te puse :) mira ya estas llegando a 100 y yo recien ando recuperándome del negativo, mas bn dame tu msn haber si algún otro momento conversamos.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#14
podes fijarte en mis datos de perfil y listo ahi tenes mi msn etc
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#15
Fernando te cuento que segui tu guia de deselastixando y tuve muchos problemas,

s i n o l o g i c /blog/2010-12/como-deselastixar-elastixr-parte-1-o-como-lograr-que-nuestra-distro-sea-mucho-mas-estable-y-segura/

y

s i n o l o g i c /blog/2011-01/como-deselastixar-elastixr-parte-2-y-final-o-como-lograr-que-nuestra-distro-sea-mucho-mas-estable-y-segura/

y en la parte uno dice :
Ahora con todo upgradeado rebooteamos el sistema con cuidado de al bootear elegir el Nuevo kernel 2.6.18-194.26.1.el5…

y en la parte 2 dice:
1) Con el comando #uname –a vemos que tengamos booteado el sistema con nuestro kernel 2.6.18-194.32.1…

Que kernel uso y a que version de asterisk actualizo????

y cuando le doy la parte de ./configure && make menuselect && make && make install me bota varios errores.

Haber voy a volver a intentar en una de prueba y te digo como va, haber para que me saques las dudas del deselastixando porfa :)
 

Luis Diego

Joined
Nov 1, 2010
Messages
237
Likes
0
Points
0
#16
Fernando te comento que encontre el problema es mira:
Loaded symbols for /lib/libnss_dns.so.2
Core was generated by `/usr/sbin/asterisk -f -U asterisk -G asterisk -vvvvvvvvvvg -c'.
Program terminated with signal 11, Segmentation fault.
#0 0x00e0c660 in ExitMP3 () from /usr/lib/asterisk/modules/format_mp3.so

si un bug que tiene y aunque haya actualizado hubiera tenido este problemita pk en asterisk 1.8 tmb siguen con el mismo bug.
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#17
vamos por partes....ahora el kernel 26 ya es viejos el ultimo es el 32.1 y las versiones de asterisk dahdi etc ya cambiaron todas....hay mucho mas nuevas ejemplo 1.8.3.2
si el configuire et da errores es que faltaron librerias o estan mal copiadas...hayq que validar eso...
 

fmvillares

Joined
Sep 8, 2007
Messages
1,785
Likes
0
Points
0
#18
no es un bug...a mi me anda perfecto en als installs...quizas no brraste toda la acrpeta anterior del asterisk 1.6 y et trata de levantar el del 1.6 en 1.8
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,902
Messages
130,887
Members
17,565
Latest member
omarmenichetti
Top