You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2013/03/15 19:28:14 UTC

[jira] [Resolved] (TS-1505) traffic server crash

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

James Peach resolved TS-1505.
-----------------------------

       Resolution: Not A Problem
    Fix Version/s:     (was: 3.3.4)

Closing as a configuration issue as per Uri's analysis.
                
> traffic server crash
> --------------------
>
>                 Key: TS-1505
>                 URL: https://issues.apache.org/jira/browse/TS-1505
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.4
>         Environment: os: centos 6.2 x64
>            Reporter: lingjie.zhou
>            Priority: Critical
>
> I have 12's ats server has run 3 month is very well, but in the past week 2 ats server have been crashd, crash reason log is:
> [Sep 26 21:32:49.846] Manager {139893959927776} NOTE: [LocalManager::pollMgmtProcessServer] New process connecting fd '10'
> [Sep 26 21:32:49.846] Manager {139893959927776} NOTE: [Alarms::signalAlarm] Server Process born
> [Sep 26 21:32:50.859] {47599477855840} STATUS: opened /usr/local/ats/var/log/trafficserver/diags.log
> [Sep 26 21:32:50.859] {47599477855840} NOTE: updated diags config
> [Sep 26 21:32:50.861] Server {47599477855840} NOTE: cache clustering disabled
> [Sep 26 21:32:50.879] Server {47599477855840} NOTE: cache clustering disabled
> [Sep 26 21:32:50.908] Server {47599477855840} NOTE: logging initialized[7], logging_mode = 3
> [Sep 26 21:32:50.909] Server {47599477855840} ERROR: Cannot insert duplicate!
> [Sep 26 21:32:50.909] Server {47599477855840} ERROR: Couldn't insert into trie!
> [Sep 26 21:32:50.909] Server {47599477855840} WARNING: Could not insert new mapping
> [Sep 26 21:32:50.909] Server {47599477855840} WARNING: Could not add rule at line #8; Aborting!
> [Sep 26 21:32:50.909] Server {47599477855840} WARNING: [ReverseProxy] Unable to add mapping rule to lookup table at line 8
> [Sep 26 21:32:50.909] Server {47599477855840} WARNING: something failed during BuildTable() -- check your remap plugins!
> [Sep 26 21:32:50.909] Server {47599477855840} WARNING: Can not load the remap table, exiting out!
> [Sep 26 21:32:50.916] Manager {139893959927776} ERROR: [Alarms::signalAlarm] Server Process was reset
> [Sep 26 21:32:50.916] Manager {139893959927776} ERROR:  (last system error 2: No such file or directory)
> [TrafficManager] ==> Cleaning up and reissuing signal #15
> [Sep 26 21:32:51.713] Manager {139893959927776} ERROR: [TrafficManager] ==> Cleaning up and reissuing signal #15
> [Sep 26 21:32:51.713] Manager {139893959927776} ERROR:  (last system error 2: No such file or directory)
> [TrafficManager] ==> signal #15
> [Sep 26 21:32:51.713] Manager {139893959927776} ERROR: [TrafficManager] ==> signal #15
> [Sep 26 21:32:51.713] Manager {139893959927776} ERROR:  (last system error 2: No such file or directory)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira