[jira] Resolved: (TS-156) Enabling serve_stale_for crashes traffic_server with SRV records enabled crashes

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

     [ https://issues.apache.org/jira/browse/TS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom resolved TS-156.
------------------------------

    Resolution: Invalid

I can't reproduce this now either, please reopen if needed.

> Enabling serve_stale_for crashes traffic_server with SRV records enabled crashes
> --------------------------------------------------------------------------------
>
>                 Key: TS-156
>                 URL: https://issues.apache.org/jira/browse/TS-156
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Leif Hedstrom
>            Priority: Critical
>             Fix For: 2.1.2
>
>
> (This is moved from Y! Bugzilla ticket 2561190, originally posted by Leif Hedstrom on 2009-02-25):
> We've been testing 1.17.13 on a production box, and activated the new features that we've been adding. This causes TS
> to crash fairly frequently, and I've tracked this down to this configuration:
>     CONFIG proxy.config.hostdb.serve_stale_for INT 60
> setting this back to 0 (which disabled this new feature) eliminates the crashes.
> Comment #5 (Leif Hedstrom):
> So, it seems this only triggers IF the SRV records feature is enabled as well. I.e. 
>    CONFIG proxy.config.srv_enabled INT 1
> I've examined the code for the serve_stale_for feature, and it seems good. However, the SRV records feature is all
> brand new code, and rather untested.
> Comment #4 (Leif Hedstrom):
> This is a more likely stack trace (thanks Bryan for reminding me about our fantastic stack trace feature that logs the
> traces into traffic.log):
> 0x083BCD02:bin/traffic_server:ink_atomiclist_push
> 0x082D158E:bin/traffic_server:probe(ProxyMutex*, INK_MD5&, char*, int, int, int, void*, bool, bool)
> 0x082D1597:bin/traffic_server:probe(ProxyMutex*, INK_MD5&, char*, int, int, int, void*, bool, bool)
> 0x081C9DD3:bin/traffic_server:HttpTransact::delete_srv_entry(HttpTransact::State*, int)
> 0x081CB363:bin/traffic_server:HttpTransact::handle_response_from_server(HttpTransact::State*)
> 0x081CB9CE:bin/traffic_server:HttpTransact::HandleResponse(HttpTransact::State*)
> 0x081DFF7B:bin/traffic_server:HttpSM::call_transact_and_set_next_state(void (*)(HttpTransact::State*))
> 0x081E3D57:bin/traffic_server:HttpSM::handle_server_setup_error(int, void*)
> 0x081E721A:bin/traffic_server:HttpSM::state_read_server_response_header(int, void*)
> 0x081E69A2:bin/traffic_server:HttpSM::main_handler(int, void*)
> 0x0832B69F:bin/traffic_server:UnixNetVConnection::net_read_io(NetHandler*, EThread*)
> 0x08330AB5:bin/traffic_server:NetHandler::mainNetEvent(int, Event*)
> 0x0834B9C2:bin/traffic_server:EThread::process_event(Event*, int)
> 0x0834CAFE:bin/traffic_server:EThread::execute()
> 0x0812CB83:bin/traffic_server:main
> 0x00418DE3:/lib/tls/libc.so.6:__libc_start_main
> 0x080D6CA1:bin/traffic_server:__gxx_personality_v0
> 0x080D6CA1:bin/traffic_server:__gxx_personality_v0
> 0x080D6CA1:bin/traffic_server:__gxx_personality_v0
> 0x080D6CA1:bin/traffic_server:__gxx_personality_v0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.