[jira] [Commented] (TS-807) Crash when clustering is enabled

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040312#comment-13040312 ] 

Leif Hedstrom commented on TS-807:
----------------------------------

Well, I'm unable to reproduce this now. Maybe it's because I've nuked my entire installation on both nodes in the cluster several times. I'm wondering if I had some lingering stuff hanging around (e.g. in host.db) on one of the nodes.

ming_zym: can you verify if nuking the entire installation on all nodes helps?

> Crash when clustering is enabled
> --------------------------------
>
>                 Key: TS-807
>                 URL: https://issues.apache.org/jira/browse/TS-807
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Leif Hedstrom
>             Fix For: 2.1.9
>
>
> There's a crasher when enabling clustering, it triggers almost immediately:
> {code}
> gdb) bt
> #0  0x4001f416 in __kernel_vsyscall ()
> #1  0x405592f1 in raise () from /lib/libc.so.6
> #2  0x4055ad5e in abort () from /lib/libc.so.6
> #3  0x082c85f3 in ink_die_die_die (retval=1) at ink_error.cc:43
> #4  0x082c868f in ink_fatal_va (return_code=1, message_format=0x45d0aae0 "ClusterRPC.cc:219: failed assert `!\"set_channel_data_ClusterFunction bad CacheDataType\"`", ap=0x45d0aad8 "") at ink_error.cc:65
> #5  0x082c86b2 in ink_fatal (return_code=1, message_format=0x45d0aae0 "ClusterRPC.cc:219: failed assert `!\"set_channel_data_ClusterFunction bad CacheDataType\"`") at ink_error.cc:73
> #6  0x082c7fcc in _ink_assert (a=0x832790c "!\"set_channel_data_ClusterFunction bad CacheDataType\"", f=0x83277eb "ClusterRPC.cc", l=219) at ink_assert.cc:44
> #7  0x082520ff in set_channel_data_ClusterFunction (from=0x41900468, tdata=0x44bd4018, tlen=1920) at ClusterRPC.cc:219
> #8  0x0823dda7 in ClusterHandler::process_set_data_msgs (this=0xbe53c78) at ClusterHandler.cc:898
> #9  0x0823e61d in ClusterHandler::update_channels_read (this=0xbe53c78) at ClusterHandler.cc:1100
> #10 0x0824398e in ClusterHandler::process_read (this=0xbe53c78, now=1306467979880346000) at ClusterHandler.cc:2807
> #11 0x08242dec in ClusterHandler::mainClusterEvent (this=0xbe53c78, event=1, e=0x0) at ClusterHandler.cc:2486
> #12 0x08107ca1 in Continuation::handleEvent (this=0xbe53c78, event=1, data=0x0) at ../iocore/eventsystem/I_Continuation.h:146
> #13 0x08248102 in ClusterState::IOComplete (this=0xbe53ed0) at ClusterHandlerBase.cc:588
> #14 0x08247e6d in ClusterState::doIO_read_event (this=0xbe53ed0, event=102, d=0x44c2329c) at ClusterHandlerBase.cc:486
> #15 0x08107ca1 in Continuation::handleEvent (this=0xbe53ed0, event=102, data=0x44c2329c) at ../iocore/eventsystem/I_Continuation.h:146
> #16 0x082a180b in read_signal_and_update (event=102, vc=0x44c23120) at UnixNetVConnection.cc:136
> #17 0x082a1981 in read_signal_done (event=102, nh=0x45b0d528, vc=0x44c23120) at UnixNetVConnection.cc:166
> #18 0x082a211f in read_from_net (nh=0x45b0d528, vc=0x44c23120, thread=0x45b0c008) at UnixNetVConnection.cc:314
> #19 0x082a3d61 in UnixNetVConnection::net_read_io (this=0x44c23120, nh=0x45b0d528, lthread=0x45b0c008) at UnixNetVConnection.cc:791
> #20 0x0829e6a4 in NetHandler::mainNetEvent (this=0x45b0d528, event=5, e=0xbe52480) at UnixNet.cc:397
> #21 0x08107ca1 in Continuation::handleEvent (this=0x45b0d528, event=5, data=0xbe52480) at ../iocore/eventsystem/I_Continuation.h:146
> #22 0x082c1852 in EThread::process_event (this=0x45b0c008, e=0xbe52480, calling_code=5) at UnixEThread.cc:140
> #23 0x082c1e0c in EThread::execute (this=0x45b0c008) at UnixEThread.cc:262
> #24 0x082c0911 in spawn_thread_internal (a=0xbd31930) at Thread.cc:88
> #25 0x4002de99 in start_thread () from /lib/libpthread.so.0
> #26 0x40605d2e in clone () from /lib/libc.so.6
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira