F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

cjunior_138458's avatar
cjunior_138458
Icon for Altostratus rankAltostratus
Dec 09, 2015

APM + SPDY = core dump

I was looking for some similar issue here, but I had no lucky.

 

When combines access profile and spdy profile, the system simply falls down and generates core dump when in the first traffic request.

 

I reproduce this issue in lab, just by setting a simple VS:443 with a blank access policy and defaults rewrite, connectivity and spdy profile.

 

I can see some data arriving in spdy profile for a moment, but the browser can't go on and system restarts daemons.

 

Has spdy some incompatibility regarding access profile, rewrite or connectivity?

 

Has someone faced this problem before?

 

BIG-IP VE v.12.0.0

 

SPDY 3.1

 

Thank you so much!

 

2 Replies

  • Lucas_Thompson_'s avatar
    Lucas_Thompson_
    Historic F5 Account

    Please open a support case right away so we can take a look at this problem. With a core file (tmm in /shared/core) can be used along with a qkview configuration snapshot to do RCA rapidly.

     

    I did a quick scan of the defect database and couldn't find anything similar in v12.0.0.

     

  • Hi,

    This problem is related to a new bug 553688, so F5 sent me a ENG HFX to fix it. Now clearly no longer generated core dump, but still can not open the APM portal. It just does not do anything and does not respond.

    The strange thing is that when removing the SPDY profile, another problem begins to occur. The connection is terminated with RST and something like this appears in the ltm log:

    [0x2023f71:1924] No local listener

    I tested and found that is related to VLANs and fix it by switching to "All VLANs" and then returning my specific VLANs in VS. (no sure if is just it, but doing that, it comes back to live) I did tests in lab, so, to open a new ticket it would be fixed in production, but I'm not comfortable to do that yet.

    Does anyone have suggestions on troubleshooting for this communication type?