You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Francis David (JIRA)" <ji...@apache.org> on 2010/09/28 14:26:33 UTC
[jira] Created: (TS-472) Segmentation Fault in CacheWrite.cc
Segmentation Fault in CacheWrite.cc
-----------------------------------
Key: TS-472
URL: https://issues.apache.org/jira/browse/TS-472
Project: Traffic Server
Issue Type: Bug
Components: Logging
Environment: CentOS 4.x
Reporter: Francis David
We have been using traffic server in our product for several years and have seen this core many times. We are unable to reproduce it or know the issue. I have pasted the trace from the core. I am unaware of the version of TS and could see from the code ( Diags.h ) its version is 1.3.
Any pointers would be very helpful to us.
(gdb) where
#0 0x0841ff56 in CacheVC::updateVector (this=0x21, event=8894496, e=0x88f2408) at
../../../iocore/cache/CacheWrite.cc:65
#1 0x081298fc in __tcf_0 () at ../../iocore/hostdb/P_HostDBProcessor.h:374
#2 0x08138a40 in FtpSM::handle_abor_command (this=0xdb520e8, event=2, data=0x923efe0) at ../../proxy/FtpSM.cc:4716
#3 0x08411056 in ShowHostDB::showOne (this=0xb7cb1018, r=0x923efe0, rr=183, event=153350112, e=0xff76abc0) at
../../../iocore/hostdb/HostDB.cc:2022
#4 0x0841156b in CacheVC (this=0xb7cb1018) at ../../../iocore/cache/Cache.cc:181
#5 0x081b046b in RegressionTest_SDK_API_INKMimeHdrParse (test=0x3, atype=-1073742348, pstatus=0xbffffe04) at
../../proxy/InkAPITest.cc:5839
Thanks,
GG
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TS-472) Segmentation Fault in CacheWrite.cc
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919022#action_12919022 ]
Leif Hedstrom commented on TS-472:
----------------------------------
I honestly don't know what version that is. When you downloaded the source, it would say in the name of the download file what version it is. Also, ATS will report (by default, unless you have disabled it) what version it is running in every response, in the Server: header.
That much said, when I do the above, I get
root@loki 1500/0 # ./bin/traffic_manager -V
[E. Mgmt] log ==> [TrafficManager] using root directory '/opt/ats'
Apache Traffic Server - traffic_manager - 2.1.4-unstable - (build # 9611 on Oct 6 2010 at 11:01:21)
(which is trunk). I'd recommend you try at the latest developer release, v2.1.3, from our download site. Also, The above traceback looks like a regression test failing, which I'm not sure how it could happen in a normal run. Those would only run if you run with the "-R" option afaik.
> Segmentation Fault in CacheWrite.cc
> -----------------------------------
>
> Key: TS-472
> URL: https://issues.apache.org/jira/browse/TS-472
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Environment: CentOS 4.x
> Reporter: Francis David
>
> We have been using traffic server in our product for several years and have seen this core many times. We are unable to reproduce it or know the issue. I have pasted the trace from the core. I am unaware of the version of TS and could see from the code ( Diags.h ) its version is 1.3.
> Any pointers would be very helpful to us.
> (gdb) where
> #0 0x0841ff56 in CacheVC::updateVector (this=0x21, event=8894496, e=0x88f2408) at
> ../../../iocore/cache/CacheWrite.cc:65
> #1 0x081298fc in __tcf_0 () at ../../iocore/hostdb/P_HostDBProcessor.h:374
> #2 0x08138a40 in FtpSM::handle_abor_command (this=0xdb520e8, event=2, data=0x923efe0) at ../../proxy/FtpSM.cc:4716
> #3 0x08411056 in ShowHostDB::showOne (this=0xb7cb1018, r=0x923efe0, rr=183, event=153350112, e=0xff76abc0) at
> ../../../iocore/hostdb/HostDB.cc:2022
> #4 0x0841156b in CacheVC (this=0xb7cb1018) at ../../../iocore/cache/Cache.cc:181
> #5 0x081b046b in RegressionTest_SDK_API_INKMimeHdrParse (test=0x3, atype=-1073742348, pstatus=0xbffffe04) at
> ../../proxy/InkAPITest.cc:5839
> Thanks,
> GG
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TS-472) Segmentation Fault in
CacheWrite.cc
Posted by "Francis David (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916059#action_12916059 ]
Francis David edited comment on TS-472 at 10/7/10 2:51 AM:
-----------------------------------------------------------
When I say ./bin/traffic_manager -version, it gives me version 1.2.3.
Are there any connections that are timing out, but not being removed from Prism, could possibly be removed by Prism. My colleagues t theory is that there are too many connections dying but not being removed, causing memory issues when a new connection wants to use that Prism. This crash might be coz of that ??
was (Author: gfranc):
When I say ./bin/traffic_manager -version, it gives me version 1.2.3.
> Segmentation Fault in CacheWrite.cc
> -----------------------------------
>
> Key: TS-472
> URL: https://issues.apache.org/jira/browse/TS-472
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Environment: CentOS 4.x
> Reporter: Francis David
>
> We have been using traffic server in our product for several years and have seen this core many times. We are unable to reproduce it or know the issue. I have pasted the trace from the core. I am unaware of the version of TS and could see from the code ( Diags.h ) its version is 1.3.
> Any pointers would be very helpful to us.
> (gdb) where
> #0 0x0841ff56 in CacheVC::updateVector (this=0x21, event=8894496, e=0x88f2408) at
> ../../../iocore/cache/CacheWrite.cc:65
> #1 0x081298fc in __tcf_0 () at ../../iocore/hostdb/P_HostDBProcessor.h:374
> #2 0x08138a40 in FtpSM::handle_abor_command (this=0xdb520e8, event=2, data=0x923efe0) at ../../proxy/FtpSM.cc:4716
> #3 0x08411056 in ShowHostDB::showOne (this=0xb7cb1018, r=0x923efe0, rr=183, event=153350112, e=0xff76abc0) at
> ../../../iocore/hostdb/HostDB.cc:2022
> #4 0x0841156b in CacheVC (this=0xb7cb1018) at ../../../iocore/cache/Cache.cc:181
> #5 0x081b046b in RegressionTest_SDK_API_INKMimeHdrParse (test=0x3, atype=-1073742348, pstatus=0xbffffe04) at
> ../../proxy/InkAPITest.cc:5839
> Thanks,
> GG
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TS-472) Segmentation Fault in CacheWrite.cc
Posted by "Francis David (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916802#action_12916802 ]
Francis David commented on TS-472:
----------------------------------
Is it a very old version or is this version invalid. ? I had compared this particular file with the latest verion of ATS and found no difference? Should we migrate to the stable one?
> Segmentation Fault in CacheWrite.cc
> -----------------------------------
>
> Key: TS-472
> URL: https://issues.apache.org/jira/browse/TS-472
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Environment: CentOS 4.x
> Reporter: Francis David
>
> We have been using traffic server in our product for several years and have seen this core many times. We are unable to reproduce it or know the issue. I have pasted the trace from the core. I am unaware of the version of TS and could see from the code ( Diags.h ) its version is 1.3.
> Any pointers would be very helpful to us.
> (gdb) where
> #0 0x0841ff56 in CacheVC::updateVector (this=0x21, event=8894496, e=0x88f2408) at
> ../../../iocore/cache/CacheWrite.cc:65
> #1 0x081298fc in __tcf_0 () at ../../iocore/hostdb/P_HostDBProcessor.h:374
> #2 0x08138a40 in FtpSM::handle_abor_command (this=0xdb520e8, event=2, data=0x923efe0) at ../../proxy/FtpSM.cc:4716
> #3 0x08411056 in ShowHostDB::showOne (this=0xb7cb1018, r=0x923efe0, rr=183, event=153350112, e=0xff76abc0) at
> ../../../iocore/hostdb/HostDB.cc:2022
> #4 0x0841156b in CacheVC (this=0xb7cb1018) at ../../../iocore/cache/Cache.cc:181
> #5 0x081b046b in RegressionTest_SDK_API_INKMimeHdrParse (test=0x3, atype=-1073742348, pstatus=0xbffffe04) at
> ../../proxy/InkAPITest.cc:5839
> Thanks,
> GG
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TS-472) Segmentation Fault in CacheWrite.cc
Posted by "Francis David (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916059#action_12916059 ]
Francis David commented on TS-472:
----------------------------------
When I say ./bin/traffic_manager -version, it gives me version 1.2.3.
> Segmentation Fault in CacheWrite.cc
> -----------------------------------
>
> Key: TS-472
> URL: https://issues.apache.org/jira/browse/TS-472
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Environment: CentOS 4.x
> Reporter: Francis David
>
> We have been using traffic server in our product for several years and have seen this core many times. We are unable to reproduce it or know the issue. I have pasted the trace from the core. I am unaware of the version of TS and could see from the code ( Diags.h ) its version is 1.3.
> Any pointers would be very helpful to us.
> (gdb) where
> #0 0x0841ff56 in CacheVC::updateVector (this=0x21, event=8894496, e=0x88f2408) at
> ../../../iocore/cache/CacheWrite.cc:65
> #1 0x081298fc in __tcf_0 () at ../../iocore/hostdb/P_HostDBProcessor.h:374
> #2 0x08138a40 in FtpSM::handle_abor_command (this=0xdb520e8, event=2, data=0x923efe0) at ../../proxy/FtpSM.cc:4716
> #3 0x08411056 in ShowHostDB::showOne (this=0xb7cb1018, r=0x923efe0, rr=183, event=153350112, e=0xff76abc0) at
> ../../../iocore/hostdb/HostDB.cc:2022
> #4 0x0841156b in CacheVC (this=0xb7cb1018) at ../../../iocore/cache/Cache.cc:181
> #5 0x081b046b in RegressionTest_SDK_API_INKMimeHdrParse (test=0x3, atype=-1073742348, pstatus=0xbffffe04) at
> ../../proxy/InkAPITest.cc:5839
> Thanks,
> GG
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TS-472) Segmentation Fault in CacheWrite.cc
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915746#action_12915746 ]
Leif Hedstrom commented on TS-472:
----------------------------------
We'll need to know which version of ATS you have installed (e.g. 2.0.1, or 2.1.2 etc.). Also, if you can, please test v2.1.3, which was just recently pushed to the dist servers.
> Segmentation Fault in CacheWrite.cc
> -----------------------------------
>
> Key: TS-472
> URL: https://issues.apache.org/jira/browse/TS-472
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Environment: CentOS 4.x
> Reporter: Francis David
>
> We have been using traffic server in our product for several years and have seen this core many times. We are unable to reproduce it or know the issue. I have pasted the trace from the core. I am unaware of the version of TS and could see from the code ( Diags.h ) its version is 1.3.
> Any pointers would be very helpful to us.
> (gdb) where
> #0 0x0841ff56 in CacheVC::updateVector (this=0x21, event=8894496, e=0x88f2408) at
> ../../../iocore/cache/CacheWrite.cc:65
> #1 0x081298fc in __tcf_0 () at ../../iocore/hostdb/P_HostDBProcessor.h:374
> #2 0x08138a40 in FtpSM::handle_abor_command (this=0xdb520e8, event=2, data=0x923efe0) at ../../proxy/FtpSM.cc:4716
> #3 0x08411056 in ShowHostDB::showOne (this=0xb7cb1018, r=0x923efe0, rr=183, event=153350112, e=0xff76abc0) at
> ../../../iocore/hostdb/HostDB.cc:2022
> #4 0x0841156b in CacheVC (this=0xb7cb1018) at ../../../iocore/cache/Cache.cc:181
> #5 0x081b046b in RegressionTest_SDK_API_INKMimeHdrParse (test=0x3, atype=-1073742348, pstatus=0xbffffe04) at
> ../../proxy/InkAPITest.cc:5839
> Thanks,
> GG
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.