You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2022/12/29 16:46:02 UTC

[GitHub] [trafficserver] paulo opened a new issue, #9279: Failed assertion when `proxy.config.http.cache.open_write_fail_action` set to 5

paulo opened a new issue, #9279:
URL: https://github.com/apache/trafficserver/issues/9279

   I've been pretty easily able to reproduce the following trace when `proxy.config.http.cache.open_write_fail_action` is set to 5 (with r[ead while writer](https://docs.trafficserver.apache.org/en/9.1.x/admin-guide/configuration/cache-basics.en.html#read-while-writer) enabled as well).
   
   ```
   Fatal: HttpCacheSM.cc:101: failed assertion `captive_action.cancelled == 0`
   traffic_server: received signal 6 (Abort trap: 6)
   traffic_server - STACK TRACE:
   0   traffic_server                      0x00000000061d1cc0 _Z19crash_logger_invokeiP9__siginfoPv + 128
   1   libsystem_platform.dylib            0x00007ff81304cdfd _sigtramp + 29
   2   ???                                 0x0000000000000002 0x0 + 2
   3   libsystem_c.dylib                   0x00007ff812f82d24 abort + 123
   4   libtscore.9.dylib                   0x0000000007c0c49a _Z9ink_abortPKcz + 154
   5   libtscore.9.dylib                   0x0000000007c0999c _ink_assert + 44
   6   traffic_server                      0x0000000006280ea1 _ZN11HttpCacheSM21state_cache_open_readEiPv + 321
   7   traffic_server                      0x00000000061d4afe _ZN12Continuation11handleEventEiPv + 238
   8   traffic_server                      0x0000000006571b5e _ZN7CacheVC8callcontEi + 174
   9   traffic_server                      0x0000000006555a68 _ZN7CacheVC17openReadStartHeadEiP5Event + 5912
   10  traffic_server                      0x00000000061d4afe _ZN12Continuation11handleEventEiPv + 238
   11  traffic_server                      0x0000000006558460 _ZN5Cache9open_readEP12ContinuationPKN3ats10CryptoHashEP7HTTPHdrPK27OverridableHttpConfigParams13CacheFragTypePKci + 1776
   12  traffic_server                      0x000000000651ef26 _ZN14CacheProcessor9open_readEP12ContinuationPK12HttpCacheKeyP7HTTPHdrPK27OverridableHttpConfigParamsl13CacheFragType + 102
   13  traffic_server                      0x000000000628135a _ZN11HttpCacheSM18do_cache_open_readERK12HttpCacheKey + 250
   14  traffic_server                      0x0000000006282059 _ZN11HttpCacheSM9open_readEPK12HttpCacheKeyP3URLP7HTTPHdrPK27OverridableHttpConfigParamsl + 265
   15  traffic_server                      0x00000000062ec975 _ZN6HttpSM24do_cache_lookup_and_readEv + 789
   16  traffic_server                      0x00000000062f1e3b _ZN6HttpSM14set_next_stateEv + 3051
   17  traffic_server                      0x00000000062d0875 _ZN6HttpSM32call_transact_and_set_next_stateEPFvPN12HttpTransact5StateEE + 485
   18  traffic_server                      0x00000000062e32d6 _ZN6HttpSM22state_cache_open_writeEiPv + 2086
   19  traffic_server                      0x00000000062cc8e4 _ZN6HttpSM12main_handlerEiPv + 980
   20  traffic_server                      0x00000000061d4afe _ZN12Continuation11handleEventEiPv + 238
   21  traffic_server                      0x0000000006281a05 _ZN11HttpCacheSM22state_cache_open_writeEiPv + 1509 
   22  traffic_server                      0x00000000061d4afe _ZN12Continuation11handleEventEiPv + 238
   23  traffic_server                      0x00000000066ee644 _ZN7EThread13process_eventEP5Eventi + 404
   24  traffic_server                      0x00000000066eeed9 _ZN7EThread15execute_regularEv + 665
   25  traffic_server                      0x00000000066ef495 _ZN7EThread7executeEv + 245
   26  traffic_server                      0x00000000066ed5d0 _ZL21spawn_thread_internalPv + 96
   27  libsystem_pthread.dylib             0x00007ff8130374e1 _pthread_start + 125
   28  libsystem_pthread.dylib             0x00007ff813032f6b thread_start + 15
   ```
   
   Can reproduce it in both 9.1.3 and 9.1.4 with the following scenario:
   - Client that can make up to 20 parallel HTTP/1.1 GET requests.
   - Client requests get cancelled after writing the headers.
   - Slow origin (can take up to 5 seconds to stream the entire payload, which in my tests is just 20 bytes).
   
   Can't reproduce it with any other `proxy.config.http.cache.open_write_fail_action` setting.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [trafficserver] traeak commented on issue #9279: Failed assertion when `proxy.config.http.cache.open_write_fail_action` set to 5

Posted by "traeak (via GitHub)" <gi...@apache.org>.
traeak commented on issue #9279:
URL: https://github.com/apache/trafficserver/issues/9279#issuecomment-1706902442

   I got this to show up during testing august 2023 in ats master.  Was getting crashes with simulating thundering herd with simulated manifest, max-age=0 provided the best way to recreate the crash.  Definitely related to stale assets.  Unfortunately the crash just cleared up while I was working on it, trying to recreate it again.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [trafficserver] bryancall commented on issue #9279: Failed assertion when `proxy.config.http.cache.open_write_fail_action` set to 5

Posted by GitBox <gi...@apache.org>.
bryancall commented on issue #9279:
URL: https://github.com/apache/trafficserver/issues/9279#issuecomment-1376557191

   #7092 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org