[Gluster-devel] Smoke build failing because mountpoint doesn't exist?

Kaleb S. KEITHLEY kkeithle at redhat.com
Fri Feb 14 14:58:22 UTC 2014

On 02/14/2014 09:33 AM, Kaleb S. KEITHLEY wrote:
> I've retriggered the smoke build. Let's see what happens with it.
> transport endpoint not connected sounds like glusterfsd crashed. I'm
> looking to see if there are any core files from that run.

Indeed, your glusterfsd is crashing.

Here's a bt from one of the core files:

Program terminated with signal 11, Segmentation fault.
#0  0x00007fcf0800cf67 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install 
glibc-2.12-1.80.el6_3.5.x86_64 keyutils-libs-1.4-4.el6.x86_64 
krb5-libs-1.10.3-10.el6_4.6.x86_64 libaio-0.3.107-10.el6.x86_64 
libcom_err-1.41.12-12.el6.x86_64 libgcc-4.4.7-3.el6.x86_64 
libselinux-2.0.94-5.3.el6.x86_64 openssl-libs-1.0.1e-4.el6.x86_64 
python-libs-2.6.6-36.el6.x86_64 zlib-1.2.3-29.el6.x86_64
(gdb) where
#0  0x00007fcf0800cf67 in fclose@@GLIBC_2.2.5 () from /lib64/libc.so.6
#1  0x000000000040d256 in mgmt_getspec_cbk (req=0x225119c, iov=0x22511dc,
     count=1, myframe=0x7fcf07018694)
#2  0x00007fcf097917dc in rpc_clnt_notify (trans=0x0, mydata=0x0,
     event=RPC_TRANSPORT_ACCEPT, data=0x0)
#3  0x00007fcf09791bff in rpc_clnt_new (options=0x2237480, ctx=0x22596e0,
     name=0x7fcf09df0800 "", reqpool_size=0)
#4  0x00007fcf0978dea3 in rpc_transport_unix_options_build (
     options=0x7fcf049ead2a, filepath=0x7fffb90821d0 
#5  0x00007fcf049ead9d in socket_connect_finish (this=0x7fcf049ead9d)
#6  0x00007fcf049eb258 in socket_poller (ctx=0x7fcf049eb258)
#7  0x00007fcf09a20b19 in yyunput (c=32719, yy_bp=0x0) at <stdout>:1269
#8  0x00007fcf09a20d08 in graphyyrestart (input_file=0x100000000)
     at <stdout>:1390
#9  0x00007fcf099ed4cb in mem_pool_new_fn (sizeof_type=4294967296,
     count=7399290016, name=0x22580e0 "\001")
#10 0x0000000000408fd0 in main (argc=19, argv=0x7fffb90834a8)
(gdb) up
(gdb) print tmpfp
$1 = (FILE *) 0x2259ef0

> On 02/14/2014 09:24 AM, Jose Rivera wrote:
>> Hey all,
>> I don't know if this got through or not, so I'm trying again. Sorry for
>> the spam, if any. :)
>> I'm baffled. Can someone have a look at this build[1] and let me know if
>> they see what could be going wrong? The change[2] its testing passes the
>> rh-bugid build fine. If it helps I have a build of another change of mine
>> that succeeded[3].
>> Thanks!
>> --Jose
>> [1] http://build.gluster.org/job/smoke/6455/console
>> [2] http://review.gluster.org/#/c/6910/
>> [3] http://build.gluster.org/job/smoke/6454/console
>> _______________________________________________
>> Gluster-devel mailing list
>> Gluster-devel at nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/gluster-devel



More information about the Gluster-devel mailing list