En el bash de postgres ejecuté:
Primero
# ulimit -c unlimited
Luego
# /usr/bin/postmaster -p '5432' -D '/BASEDATO' & >>
/var/lib/pgsql/pgstartup.log 2>&1 < /dev/null
Donde se supone que debiera quedar el archivo core?
Estoy en Centos 5 64 bits.
Atte,
Ernesto del Campo C.
Ernesto Esteban del Campo Cárcamo escribió:
> Muchas Gracias Alvaro,
>
> En este momento estoy haciendo las pruebas que me comentaste y les
> cuento como me va.
>
> Atte,
> Ernesto del Campo C.
>
> Alvaro Herrera escribió:
>> Ernesto Esteban del Campo Cárcamo escribió:
>>> Estimados listeros,
>>>
>>> Tengo un problema mas o menos grave:
>>>
>>> Para que esten en el contexto en que me encuentro, instalé Centos 5.0
>>> + un sistema de Cluster con HeartBeat y DRBD que hace un raid 1 por
>>> red con la carpeta /BASEDATO que contiene el directorio data de
>>> PostgreSQL.
>>
>> Una señal 11 es sintoma de problemas serios ... lo mas probable es que
>> se trate de un problema de hardware. Haz hecho correr memtest sobre la
>> maquina en cuestion? Hay algun otro proceso corriendo en la maquina y
>> que tambien se muera inesperadamente?
>>
>> Tambien es posible que sea un bug de Postgres. Ideal seria que pudieras
>> capturar el backtrace. Para esto, tienes que iniciar postmaster en un
>> shell donde hayas hecho
>> ulimit -c unlimited
>> y luego guardas el archivo core que se genere cuando el proceso se
>> caiga. A continuacion, haces
>> gdb postmaster /path/al/core
>> y en gdb le das "bt". Luego pegas la salida aca y comentamos.
>>
>> Ojo, para que esto funcione tiene que ser un Postgres que este compilado
>> con simbolos de depuracion. Entiendo que algunas distros tienen los
>> simbolos en paquetes separados, por ej. podrias buscar si hay un paquete
>> postgresql-dbg o -debug algo por el estilo.
>>
From [EMAIL PROTECTED] Thu Jun 14 17:23:44 2007
From: [EMAIL PROTECTED] (Alvaro Herrera)
Date: Thu Jun 14 17:25:49 2007
Subject: Cae postgres de forma inesperada
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Ernesto Esteban del Campo Cárcamo escribió:
> En el bash de postgres ejecuté:
> Primero
> # ulimit -c unlimited
> Luego
> # /usr/bin/postmaster -p '5432' -D '/BASEDATO' & >>
> /var/lib/pgsql/pgstartup.log 2>&1 < /dev/null
>
> Donde se supone que debiera quedar el archivo core?
Depende de la version, pero empieza buscandolo en /BASEDATO.
--
Alvaro Herrera http://www.PlanetPostgreSQL.org/
Si no sabes adonde vas, es muy probable que acabes en otra parte.
From [EMAIL PROTECTED] Thu Jun 14 17:43:23 2007
From: [EMAIL PROTECTED] (=?ISO-8859-1?Q?Ernesto_Esteban_del_Campo_C=E1rcamo?=)
Date: Thu Jun 14 17:45:17 2007
Subject: Cae postgres de forma inesperada
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Estimaods,
Me dio:
GNU gdb Red Hat Linux (6.5-16.el5rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...(no debugging
symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
Reading symbols from /lib64/libpam.so.0...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libpam.so.0
Reading symbols from /lib64/libssl.so.6...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libssl.so.6
Reading symbols from /lib64/libcrypto.so.6...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libcrypto.so.6
Reading symbols from /usr/lib64/libkrb5.so.3...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib64/libkrb5.so.3
Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libcrypt.so.1
Reading symbols from /lib64/libdl.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib64/libdl.so.2
Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib64/libm.so.6
Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libcom_err.so.2
Reading symbols from /lib64/libaudit.so.0...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libaudit.so.0
Reading symbols from /usr/lib64/libgssapi_krb5.so.2...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib64/libgssapi_krb5.so.2
Reading symbols from /usr/lib64/libk5crypto.so.3...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib64/libk5crypto.so.3
Reading symbols from /usr/lib64/libz.so.1...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib64/libz.so.1
Reading symbols from /usr/lib64/libkrb5support.so.0...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib64/libkrb5support.so.0
Reading symbols from /lib64/libresolv.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libresolv.so.2
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libnss_files.so.2
Reading symbols from /usr/lib64/gconv/ISO8859-1.so...(no debugging
symbols found)...done.
Loaded symbols for /usr/lib64/gconv/ISO8859-1.so
Reading symbols from /lib64/libnss_dns.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libnss_dns.so.2
Reading symbols from /usr/lib64/pgsql/plpgsql.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib64/pgsql/plpgsql.so
Reading symbols from /pgdte/pgdte.so...
(no debugging symbols found)...done.
Loaded symbols for /pgdte/pgdte.so
Core was generated by `postgres: ernesto axiomaintegracion 192.1'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000502cc6 in ExecMakeFunctionResult ()
(gdb) bt
#0 0x0000000000502cc6 in ExecMakeFunctionResult ()
#1 0x0000000000500a23 in ExecProject ()
#2 0x0000000000510803 in ExecResult ()
#3 0x0000000000500226 in ExecProcNode ()
#4 0x0000000000513137 in ExecSetParamPlan ()
#5 0x0000000000502681 in GetAttributeByNum ()
#6 0x0000000000500a23 in ExecProject ()
#7 0x0000000000510803 in ExecResult ()
#8 0x0000000000500226 in ExecProcNode ()
#9 0x00000000004ff51a in ExecutorRun ()
#10 0x000000000051636b in SPI_copytuple ()
#11 0x0000000000516599 in SPI_execute_plan ()
#12 0x00002aaab7d39f61 in plpgsql_subxact_cb () from
/usr/lib64/pgsql/plpgsql.so
#13 0x00002aaab7d391ca in plpgsql_subxact_cb () from
/usr/lib64/pgsql/plpgsql.so
#14 0x00002aaab7d3b0a3 in plpgsql_subxact_cb () from
/usr/lib64/pgsql/plpgsql.so
#15 0x00002aaab7d3c2c3 in plpgsql_subxact_cb () from
/usr/lib64/pgsql/plpgsql.so
#16 0x00002aaab7d3dcef in plpgsql_subxact_cb () from
/usr/lib64/pgsql/plpgsql.so
#17 0x00002aaab7d3c2d3 in plpgsql_subxact_cb () from
/usr/lib64/pgsql/plpgsql.so
#18 0x00002aaab7d3c0ca in plpgsql_subxact_cb () from
/usr/lib64/pgsql/plpgsql.so
#19 0x00002aaab7d3e5f3 in plpgsql_exec_function () from
/usr/lib64/pgsql/plpgsql.so
#20 0x00002aaab7d3548e in plpgsql_call_handler () from
/usr/lib64/pgsql/plpgsql.so
#21 0x0000000000502cbe in ExecMakeFunctionResult ()
#22 0x0000000000500a23 in ExecProject ()
#23 0x0000000000510803 in ExecResult ()
#24 0x0000000000500226 in ExecProcNode ()
#25 0x00000000004ff51a in ExecutorRun ()
#26 0x00000000005862d1 in PostgresMain ()
#27 0x0000000000587306 in PortalRun ()
#28 0x00000000005833df in pg_parse_query ()
#29 0x0000000000584862 in PostgresMain ()
#30 0x000000000055dfd7 in ClosePostmasterPorts ()
#31 0x000000000055ebea in PostmasterMain ()
#32 0x000000000051fe23 in main ()
Atte,
Ernesto del Campo C.
Alvaro Herrera escribió:
> Ernesto Esteban del Campo Cárcamo escribió:
>> En el bash de postgres ejecuté:
>> Primero
>> # ulimit -c unlimited
>> Luego
>> # /usr/bin/postmaster -p '5432' -D '/BASEDATO' & >>
>> /var/lib/pgsql/pgstartup.log 2>&1 < /dev/null
>>
>> Donde se supone que debiera quedar el archivo core?
>
> Depende de la version, pero empieza buscandolo en /BASEDATO.
>
From [EMAIL PROTECTED] Thu Jun 14 18:13:46 2007
From: [EMAIL PROTECTED] (=?ISO-8859-1?Q?Ernesto_Esteban_del_Campo_C=E1rcamo?=)
Date: Thu Jun 14 18:15:47 2007
Subject: Cae postgres de forma inesperada
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Alvaro,
Gracias a lo que me dijiste encontré el error.
Te cuento que las bd de datos al ingresar un nuevo registro, ejecutan un
compilado de C que reporta algo a otra aplicación... es una funcion onda
llamaC('basedato'), y el problema se generaba al generar un string mas
largo ej, llamaC('12345678900000000000').
Esto generaba el kernel: postmaster[9435]: segfault at 00000000006e6f69
rip 0000000000502cc6 rsp 00007fff0de659c0 error 6
Muchas gracias por tu ayuda!!!
Ernesto del Campo C.
Ernesto Esteban del Campo Cárcamo escribió:
> Estimaods,
>
> Me dio:
>
> GNU gdb Red Hat Linux (6.5-16.el5rh)
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu"...(no debugging
> symbols found)
> Using host libthread_db library "/lib64/libthread_db.so.1".
>
> Reading symbols from /lib64/libpam.so.0...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libpam.so.0
> Reading symbols from /lib64/libssl.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libssl.so.6
> Reading symbols from /lib64/libcrypto.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libcrypto.so.6
> Reading symbols from /usr/lib64/libkrb5.so.3...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib64/libkrb5.so.3
> Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libcrypt.so.1
> Reading symbols from /lib64/libdl.so.2...
> (no debugging symbols found)...done.
> Loaded symbols for /lib64/libdl.so.2
> Reading symbols from /lib64/libm.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libm.so.6
> Reading symbols from /lib64/libc.so.6...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libc.so.6
> Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libcom_err.so.2
> Reading symbols from /lib64/libaudit.so.0...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libaudit.so.0
> Reading symbols from /usr/lib64/libgssapi_krb5.so.2...
> (no debugging symbols found)...done.
> Loaded symbols for /usr/lib64/libgssapi_krb5.so.2
> Reading symbols from /usr/lib64/libk5crypto.so.3...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib64/libk5crypto.so.3
> Reading symbols from /usr/lib64/libz.so.1...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib64/libz.so.1
> Reading symbols from /usr/lib64/libkrb5support.so.0...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/lib64/libkrb5support.so.0
> Reading symbols from /lib64/libresolv.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libresolv.so.2
> Reading symbols from /lib64/ld-linux-x86-64.so.2...
> (no debugging symbols found)...done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libnss_files.so.2
> Reading symbols from /usr/lib64/gconv/ISO8859-1.so...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/lib64/gconv/ISO8859-1.so
> Reading symbols from /lib64/libnss_dns.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libnss_dns.so.2
> Reading symbols from /usr/lib64/pgsql/plpgsql.so...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib64/pgsql/plpgsql.so
> Reading symbols from /pgdte/pgdte.so...
> (no debugging symbols found)...done.
> Loaded symbols for /pgdte/pgdte.so
> Core was generated by `postgres: ernesto axiomaintegracion 192.1'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x0000000000502cc6 in ExecMakeFunctionResult ()
> (gdb) bt
>
> #0 0x0000000000502cc6 in ExecMakeFunctionResult ()
> #1 0x0000000000500a23 in ExecProject ()
> #2 0x0000000000510803 in ExecResult ()
> #3 0x0000000000500226 in ExecProcNode ()
> #4 0x0000000000513137 in ExecSetParamPlan ()
> #5 0x0000000000502681 in GetAttributeByNum ()
> #6 0x0000000000500a23 in ExecProject ()
> #7 0x0000000000510803 in ExecResult ()
> #8 0x0000000000500226 in ExecProcNode ()
> #9 0x00000000004ff51a in ExecutorRun ()
> #10 0x000000000051636b in SPI_copytuple ()
> #11 0x0000000000516599 in SPI_execute_plan ()
> #12 0x00002aaab7d39f61 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #13 0x00002aaab7d391ca in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #14 0x00002aaab7d3b0a3 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #15 0x00002aaab7d3c2c3 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #16 0x00002aaab7d3dcef in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #17 0x00002aaab7d3c2d3 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #18 0x00002aaab7d3c0ca in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #19 0x00002aaab7d3e5f3 in plpgsql_exec_function () from
> /usr/lib64/pgsql/plpgsql.so
> #20 0x00002aaab7d3548e in plpgsql_call_handler () from
> /usr/lib64/pgsql/plpgsql.so
> #21 0x0000000000502cbe in ExecMakeFunctionResult ()
> #22 0x0000000000500a23 in ExecProject ()
> #23 0x0000000000510803 in ExecResult ()
> #24 0x0000000000500226 in ExecProcNode ()
> #25 0x00000000004ff51a in ExecutorRun ()
> #26 0x00000000005862d1 in PostgresMain ()
> #27 0x0000000000587306 in PortalRun ()
> #28 0x00000000005833df in pg_parse_query ()
> #29 0x0000000000584862 in PostgresMain ()
> #30 0x000000000055dfd7 in ClosePostmasterPorts ()
> #31 0x000000000055ebea in PostmasterMain ()
> #32 0x000000000051fe23 in main ()
>
> Atte,
> Ernesto del Campo C.
>
> Alvaro Herrera escribió:
>> Ernesto Esteban del Campo Cárcamo escribió:
>>> En el bash de postgres ejecuté:
>>> Primero
>>> # ulimit -c unlimited
>>> Luego
>>> # /usr/bin/postmaster -p '5432' -D '/BASEDATO' & >>
>>> /var/lib/pgsql/pgstartup.log 2>&1 < /dev/null
>>>
>>> Donde se supone que debiera quedar el archivo core?
>>
>> Depende de la version, pero empieza buscandolo en /BASEDATO.
>>
From [EMAIL PROTECTED] Thu Jun 14 18:17:49 2007
From: [EMAIL PROTECTED] (Alvaro Herrera)
Date: Thu Jun 14 18:19:43 2007
Subject: Cae postgres de forma inesperada
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Ernesto Esteban del Campo Cárcamo escribió:
> Reading symbols from /usr/lib64/pgsql/plpgsql.so...(no debugging symbols
> found)...done.
> Loaded symbols for /usr/lib64/pgsql/plpgsql.so
Hmm, ojo con eso de "no debugging symbols found"! Y observa esta parte
del backtrace:
> #11 0x0000000000516599 in SPI_execute_plan ()
> #12 0x00002aaab7d39f61 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #13 0x00002aaab7d391ca in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #14 0x00002aaab7d3b0a3 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #15 0x00002aaab7d3c2c3 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #16 0x00002aaab7d3dcef in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #17 0x00002aaab7d3c2d3 in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #18 0x00002aaab7d3c0ca in plpgsql_subxact_cb () from
> /usr/lib64/pgsql/plpgsql.so
> #19 0x00002aaab7d3e5f3 in plpgsql_exec_function () from
> /usr/lib64/pgsql/plpgsql.so
> #20 0x00002aaab7d3548e in plpgsql_call_handler () from
> /usr/lib64/pgsql/plpgsql.so
> #21 0x0000000000502cbe in ExecMakeFunctionResult ()
Esto es muy poco creible, primero porque plpgsql_subxact_cb nunca llama
a SPI_execute_plan, y segundo porque tampoco se llama a si mismo
recursivamente.
Mas arriba vemos que SPI_execute_plan esta invocando a SPI_copytuple,
cosa que es imposible. Y este invoca ExecutorRun; mas imposible aun.
> #9 0x00000000004ff51a in ExecutorRun ()
> #10 0x000000000051636b in SPI_copytuple ()
> #11 0x0000000000516599 in SPI_execute_plan ()
En fin, creo que este backtrace no representa ninguna realidad (en este
universo al menos). Tengo la sensacion de que los simbolos de
depuracion que conseguiste no coinciden con el ejecutable que esta
realmente corriendo.
Te recomiendo que recompiles tu mismo un ejecutable nuevo, con
--enable-debug, y luego reintentess todo el proceso.
--
Alvaro Herrera Valdivia, Chile ICBM: S 39º 49' 18.1", W 73º 13' 56.4"
"El Maquinismo fue proscrito so pena de cosquilleo hasta la muerte"
(Ijon Tichy en Viajes, Stanislaw Lem)
From [EMAIL PROTECTED] Thu Jun 14 19:20:02 2007
From: [EMAIL PROTECTED] (Luis Alejandro Aguilera Pascual)
Date: Thu Jun 14 20:20:23 2007
Subject: Edicion de video
Message-ID: <[EMAIL PROTECTED]>
Hola
Estoy incursionando en el mundo de la edicion de video y hasta ahora solo
conocia la posibilidad de editar bajo W.
Hace unos dias me estuvieron comentando la posibilidad que existe de
hacerlo bajo L, entre otras cosas me dijeron que Holliwod actualmente todo
el trabajo de postproduccion lo hace bajo software libre, ademas de que
existen herramientas tan poderosas como las bajo W e incluso mas potentes,
lo cual me impresiono ya que yo al maencionar Adobe Premier y Avid Xpress
como referencia internacional la persona que me hizo el comentario se
mantuvo en su posicion en cuanto al software libre.
Les agradeceria cualquier comentario sobre el tema y si me pueden dar
algunos consejos para comenzar en el mundo de la edicion de video bajo
software libre, sobre todo nombres de programas y paginas.
salu2
luisito
