[jira] [Updated] (TS-858) traffic_server segmentation_fault when cache storage value is below 65M
[
https://issues.apache.org/jira/browse/TS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-858:
-
Fix Version/s: (was: 3.1.4)
3.3.0
traffic_server segmentation_fault when cache storage value is below 65M
---
Key: TS-858
URL: https://issues.apache.org/jira/browse/TS-858
Project: Traffic Server
Issue Type: Bug
Components: Cache
Affects Versions: 3.0.0
Environment: Fedora 14
Reporter: Kevin Giles
Priority: Minor
Fix For: 3.3.0
specify the storage as var/trafficserver 64M in the storage.conf,
traffic_server will core dump upon launch, the following is the stack trace:
{noformat}
FATAL: Cache.cc:2293: failed assert `dpb dpb-len == (uint64_t)b`
traffic_server - STACK TRACE:
traffic_server(ink_fatal_va+0x8e)[0x82ef221]
traffic_server(ink_fatal+0x1e)[0x82ef252]
traffic_server(_ink_assert+0x90)[0x82eeb6c]
traffic_server(cplist_reconfigure()+0x2fd)[0x8283054]
traffic_server(CacheProcessor::diskInitialized()+0x19b)[0x827b7d1]
traffic_server(CacheDisk::openDone(int, void*)+0x40)[0x8291142]
traffic_server(CacheDisk::clearDone(int, void*)+0xcc)[0x8290eb2]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(AIOCallbackInternal::io_complete(int, void*)+0x2c)[0x82862c8]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(EThread::process_event(Event*, int)+0x10e)[0x82e83f2]
traffic_server(EThread::execute()+0xa6)[0x82e862a]
traffic_server[0x82e74b1]
/lib/libpthread.so.0[0x658e99]
/lib/libc.so.6(clone+0x5e)[0x59ed2e]
{noformat}
It will core dump everytime, if the cache size is set to 65M, traffic_server
will launch fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-858) traffic_server segmentation_fault when cache storage value is below 65M
[
https://issues.apache.org/jira/browse/TS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-858:
-
Fix Version/s: (was: 3.1.2)
3.1.3
I'm moving all 3.1.2 bugs out to 3.1.3, and we can move some 3.1.1 bugs out to
3.1.2, to get some release action going.
traffic_server segmentation_fault when cache storage value is below 65M
---
Key: TS-858
URL: https://issues.apache.org/jira/browse/TS-858
Project: Traffic Server
Issue Type: Bug
Components: Cache
Affects Versions: 3.0.0
Environment: Fedora 14
Reporter: Kevin Giles
Priority: Minor
Fix For: 3.1.3
specify the storage as var/trafficserver 64M in the storage.conf,
traffic_server will core dump upon launch, the following is the stack trace:
{noformat}
FATAL: Cache.cc:2293: failed assert `dpb dpb-len == (uint64_t)b`
traffic_server - STACK TRACE:
traffic_server(ink_fatal_va+0x8e)[0x82ef221]
traffic_server(ink_fatal+0x1e)[0x82ef252]
traffic_server(_ink_assert+0x90)[0x82eeb6c]
traffic_server(cplist_reconfigure()+0x2fd)[0x8283054]
traffic_server(CacheProcessor::diskInitialized()+0x19b)[0x827b7d1]
traffic_server(CacheDisk::openDone(int, void*)+0x40)[0x8291142]
traffic_server(CacheDisk::clearDone(int, void*)+0xcc)[0x8290eb2]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(AIOCallbackInternal::io_complete(int, void*)+0x2c)[0x82862c8]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(EThread::process_event(Event*, int)+0x10e)[0x82e83f2]
traffic_server(EThread::execute()+0xa6)[0x82e862a]
traffic_server[0x82e74b1]
/lib/libpthread.so.0[0x658e99]
/lib/libc.so.6(clone+0x5e)[0x59ed2e]
{noformat}
It will core dump everytime, if the cache size is set to 65M, traffic_server
will launch fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-858) traffic_server segmentation_fault when cache storage value is below 65M
[
https://issues.apache.org/jira/browse/TS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Galić updated TS-858:
--
Description:
specify the storage as var/trafficserver 64M in the storage.conf,
traffic_server will core dump upon launch, the following is the stack trace:
{noformat}
FATAL: Cache.cc:2293: failed assert `dpb dpb-len == (uint64_t)b`
traffic_server - STACK TRACE:
traffic_server(ink_fatal_va+0x8e)[0x82ef221]
traffic_server(ink_fatal+0x1e)[0x82ef252]
traffic_server(_ink_assert+0x90)[0x82eeb6c]
traffic_server(cplist_reconfigure()+0x2fd)[0x8283054]
traffic_server(CacheProcessor::diskInitialized()+0x19b)[0x827b7d1]
traffic_server(CacheDisk::openDone(int, void*)+0x40)[0x8291142]
traffic_server(CacheDisk::clearDone(int, void*)+0xcc)[0x8290eb2]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(AIOCallbackInternal::io_complete(int, void*)+0x2c)[0x82862c8]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(EThread::process_event(Event*, int)+0x10e)[0x82e83f2]
traffic_server(EThread::execute()+0xa6)[0x82e862a]
traffic_server[0x82e74b1]
/lib/libpthread.so.0[0x658e99]
/lib/libc.so.6(clone+0x5e)[0x59ed2e]
{noformat}
It will core dump everytime, if the cache size is set to 65M, traffic_server
will launch fine.
was:
specify the storage as var/trafficserver 64M in the storage.conf,
traffic_server will core dump upon launch, the following is the stack trace:
FATAL: Cache.cc:2293: failed assert `dpb dpb-len == (uint64_t)b`
traffic_server - STACK TRACE:
traffic_server(ink_fatal_va+0x8e)[0x82ef221]
traffic_server(ink_fatal+0x1e)[0x82ef252]
traffic_server(_ink_assert+0x90)[0x82eeb6c]
traffic_server(_Z18cplist_reconfigurev+0x2fd)[0x8283054]
traffic_server(_ZN14CacheProcessor15diskInitializedEv+0x19b)[0x827b7d1]
traffic_server(_ZN9CacheDisk8openDoneEiPv+0x40)[0x8291142]
traffic_server(_ZN9CacheDisk9clearDoneEiPv+0xcc)[0x8290eb2]
traffic_server(_ZN12Continuation11handleEventEiPv+0x47)[0x810d871]
traffic_server(_ZN19AIOCallbackInternal11io_completeEiPv+0x2c)[0x82862c8]
traffic_server(_ZN12Continuation11handleEventEiPv+0x47)[0x810d871]
traffic_server(_ZN7EThread13process_eventEP5Eventi+0x10e)[0x82e83f2]
traffic_server(_ZN7EThread7executeEv+0xa6)[0x82e862a]
traffic_server[0x82e74b1]
/lib/libpthread.so.0[0x658e99]
/lib/libc.so.6(clone+0x5e)[0x59ed2e]
It will core dump everytime, if the cache size is set to 65M, traffic_server
will launch fine.
traffic_server segmentation_fault when cache storage value is below 65M
---
Key: TS-858
URL: https://issues.apache.org/jira/browse/TS-858
Project: Traffic Server
Issue Type: Bug
Components: Cache
Affects Versions: 3.0.0
Environment: Fedora 14
Reporter: Kevin Giles
Priority: Minor
Fix For: 3.1.0
specify the storage as var/trafficserver 64M in the storage.conf,
traffic_server will core dump upon launch, the following is the stack trace:
{noformat}
FATAL: Cache.cc:2293: failed assert `dpb dpb-len == (uint64_t)b`
traffic_server - STACK TRACE:
traffic_server(ink_fatal_va+0x8e)[0x82ef221]
traffic_server(ink_fatal+0x1e)[0x82ef252]
traffic_server(_ink_assert+0x90)[0x82eeb6c]
traffic_server(cplist_reconfigure()+0x2fd)[0x8283054]
traffic_server(CacheProcessor::diskInitialized()+0x19b)[0x827b7d1]
traffic_server(CacheDisk::openDone(int, void*)+0x40)[0x8291142]
traffic_server(CacheDisk::clearDone(int, void*)+0xcc)[0x8290eb2]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(AIOCallbackInternal::io_complete(int, void*)+0x2c)[0x82862c8]
traffic_server(Continuation::handleEvent(int, void*)+0x47)[0x810d871]
traffic_server(EThread::process_event(Event*, int)+0x10e)[0x82e83f2]
traffic_server(EThread::execute()+0xa6)[0x82e862a]
traffic_server[0x82e74b1]
/lib/libpthread.so.0[0x658e99]
/lib/libc.so.6(clone+0x5e)[0x59ed2e]
{noformat}
It will core dump everytime, if the cache size is set to 65M, traffic_server
will launch fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-858) traffic_server segmentation_fault when cache storage value is below 65M
[ https://issues.apache.org/jira/browse/TS-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-858: - Fix Version/s: 3.1.0 traffic_server segmentation_fault when cache storage value is below 65M --- Key: TS-858 URL: https://issues.apache.org/jira/browse/TS-858 Project: Traffic Server Issue Type: Bug Components: Cache Affects Versions: 3.0.0 Environment: Fedora 14 Reporter: Kevin Giles Priority: Minor Fix For: 3.1.0 specify the storage as var/trafficserver 64M in the storage.conf, traffic_server will core dump upon launch, the following is the stack trace: FATAL: Cache.cc:2293: failed assert `dpb dpb-len == (uint64_t)b` traffic_server - STACK TRACE: traffic_server(ink_fatal_va+0x8e)[0x82ef221] traffic_server(ink_fatal+0x1e)[0x82ef252] traffic_server(_ink_assert+0x90)[0x82eeb6c] traffic_server(_Z18cplist_reconfigurev+0x2fd)[0x8283054] traffic_server(_ZN14CacheProcessor15diskInitializedEv+0x19b)[0x827b7d1] traffic_server(_ZN9CacheDisk8openDoneEiPv+0x40)[0x8291142] traffic_server(_ZN9CacheDisk9clearDoneEiPv+0xcc)[0x8290eb2] traffic_server(_ZN12Continuation11handleEventEiPv+0x47)[0x810d871] traffic_server(_ZN19AIOCallbackInternal11io_completeEiPv+0x2c)[0x82862c8] traffic_server(_ZN12Continuation11handleEventEiPv+0x47)[0x810d871] traffic_server(_ZN7EThread13process_eventEP5Eventi+0x10e)[0x82e83f2] traffic_server(_ZN7EThread7executeEv+0xa6)[0x82e862a] traffic_server[0x82e74b1] /lib/libpthread.so.0[0x658e99] /lib/libc.so.6(clone+0x5e)[0x59ed2e] It will core dump everytime, if the cache size is set to 65M, traffic_server will launch fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
