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

Leif Hedstrom updated TS-4690:
------------------------------
    Backport to Version: 6.2.1

> Logging to ascii_pipe fails in 6.2.x
> ------------------------------------
>
>                 Key: TS-4690
>                 URL: https://issues.apache.org/jira/browse/TS-4690
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Haritha Haridas
>              Labels: regression
>             Fix For: 7.0.0
>
>
> Seeing the following stack trace when trying to log to an ascii_pipe in the 
> new code :
> {code}
> /lib64/libpthread.so.0(+0xf7e0)[0x2ba4ab4f97e0]
> /lib64/libc.so.6(gsignal+0x35)[0x2ba4ac134625]
> /lib64/libc.so.6(abort+0x175)[0x2ba4ac135e05]
> ..//lib64/libtsutil.so.6(signal_crash_handler(int, siginfo*, 
> void*)+0x54)[0x2ba4aa053184]
> ../bin/traffic_server(crash_logger_invoke(int, siginfo*, 
> void*)+0x8e)[0x4af11e]
> /lib64/libpthread.so.0(+0xf7e0)[0x2ba4ab4f97e0]
> ../bin/traffic_server(LogFile::preproc_and_try_delete(LogBuffer*)+0x3f)[0x5cbeef]
> ../bin/traffic_server(LogBufferManager::preproc_buffers(LogBufferSink*)+0xb3)[0x5d5ba3]
> ../bin/traffic_server(LogObjectManager::preproc_buffers(int)+0x53)[0x5d7a33]
> ../bin/traffic_server(Log::preproc_thread_main(void*)+0x8f)[0x5b644f]
> ../bin/traffic_server(LoggingPreprocContinuation::mainEvent(int, 
> void*)+0xd)[0x5bb4cd]
> ../bin/traffic_server(EThread::execute()+0x83)[0x6fc4c3]
> ../bin/traffic_server[0x6fb9ea]
> /lib64/libpthread.so.0(+0x7aa1)[0x2ba4ab4f1aa1]
> /lib64/libc.so.6(clone+0x6d)[0x2ba4ac1ea93d]
> traffic_server - STACK TRACE:
> {code}
> seems to crash at the line   if (!m_log->m_start_time) and from the 
> constructor looks like it will be NULL for the pipes:
> {code}
>  if (m_file_format != LOG_FILE_PIPE) {
>     m_log = new BaseLogFile(name, m_signature);
>     m_log->set_hostname(Machine::instance()->hostname);
>   } else {
>     m_log = NULL;
>   }
> {code}
> im still unsure how this wasn in a problem in 5.3.x, but im seeing this only 
> in the newest code 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to