You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Zhao Yongming (JIRA)" <ji...@apache.org> on 2011/07/29 18:44:09 UTC
[jira] [Commented] (TS-896) log collation reporting Host down
[ https://issues.apache.org/jira/browse/TS-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072907#comment-13072907 ]
Zhao Yongming commented on TS-896:
----------------------------------
ok, here is some information that maybe interesting for this bug.
when I setup 2 custom log object, and enable remote log collation, the default is setup 2 tcp connection to remote logging host port 8085, and if we enable the squid.log, it will goes to 3 connections.
but if I disable and re-enable one of the logging object, TS will bring up anther connections, here is my result after some testing:
{code}
tcp 0 0 10.62.163.237:43672 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:49950 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:49849 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:59239 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:38348 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:33589 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:34519 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:47381 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:50863 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
tcp 0 0 10.62.163.237:58987 10.62.163.181:8085 ESTABLISHED 31926/traffic_serve
{code}
> log collation reporting Host down
> ---------------------------------
>
> Key: TS-896
> URL: https://issues.apache.org/jira/browse/TS-896
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging
> Affects Versions: 3.0.1
> Reporter: Zhao Yongming
>
> In my production, the server reporting something very strange regard to logging collation:
> {code}
> [Jul 29 18:58:27.665] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:27.665] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:29.793] Server {47330630715728} NOTE: [log-coll] host down [133.0.0.0:0]
> [Jul 29 18:58:30.491] Server {1106377024} NOTE: [log-coll] host down [50.52.120.55:1953855031]
> [Jul 29 18:58:31.419] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:31.681] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:58:31.739] Server {1104271680} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:58:31.811] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:31.872] Server {1106377024} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:31.899] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:32.666] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:32.666] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:36.419] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:36.679] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:58:36.738] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:58:36.810] Server {1104271680} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:36.870] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:36.899] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:37.668] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:37.668] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:37.668] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:39.569] Server {1106377024} NOTE: [log-coll] host down [115.113.108.44:745436017]
> [Jul 29 18:58:39.585] Server {47330630715728} NOTE: [log-coll] host down [208.151.89.0:0]
> [Jul 29 18:58:39.588] Server {1107429696} NOTE: [log-coll] host down [60.99.114.99:1835561315]
> [Jul 29 18:58:39.872] Server {1105324352} NOTE: [log-coll] host down [196.0.58.16:100667653]
> [Jul 29 18:58:41.420] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:41.679] Server {1106377024} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:58:41.740] Server {47330630715728} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:58:41.814] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:41.874] Server {1104271680} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:41.904] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:42.669] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:42.669] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:44.862] Server {1106377024} NOTE: [log-coll] host down [128.81.1.0:0]
> [Jul 29 18:58:46.420] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:46.678] Server {47330630715728} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:58:46.740] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:58:46.818] Server {1104271680} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:46.874] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:46.899] Server {1106377024} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:47.670] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:47.670] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:48.765] Server {1107429696} NOTE: [log-coll] host down [73.26.0.0:-1]
> [Jul 29 18:58:51.421] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:51.678] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:58:51.739] Server {1106377024} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:58:51.816] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:51.877] Server {47330630715728} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:51.900] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:52.672] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:52.672] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:52.954] Server {47330630715728} NOTE: [log-coll] host down [176.73.63.174:0]
> [Jul 29 18:58:55.794] Server {47330630715728} NOTE: [log-coll] host down [133.0.0.0:0]
> [Jul 29 18:58:56.420] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:56.495] Server {1099974976} NOTE: [log-coll] host down [49.51.38.114:1095453254]
> [Jul 29 18:58:56.680] Server {1104271680} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:58:56.742] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:58:56.815] Server {1106377024} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:56.881] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:56.901] Server {47330630715728} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:58:57.673] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:58:57.673] Manager {140453854168864} NOTE: [Alarms::signalAlarm] Skipping Alarm: 'Collation host 0.0.0.0:0 down'
> [Jul 29 18:59:00.707] Manager {140453854168864} NOTE: [LocalManager::mgmtShutdown] Executing shutdown request.
> [Jul 29 18:59:00.707] Manager {140453854168864} NOTE: [LocalManager::processShutdown] Executing process shutdown request.
> [Jul 29 18:59:01.422] Server {47330630715728} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:01.680] Server {1107429696} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:59:01.741] Server {47330630715728} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:59:01.817] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:01.879] Server {1104271680} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:01.897] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:05.566] Server {1106377024} NOTE: [log-coll] host down [115.113.108.44:745436017]
> [Jul 29 18:59:05.582] Server {1107429696} NOTE: [log-coll] host down [208.151.89.0:0]
> [Jul 29 18:59:05.589] Server {47330630715728} NOTE: [log-coll] host down [60.99.114.99:1835561315]
> [Jul 29 18:59:05.866] Server {1105324352} NOTE: [log-coll] host down [196.0.58.16:100667653]
> [Jul 29 18:59:06.420] Server {1106377024} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:06.680] Server {1099974976} NOTE: [log-coll] host down [0.0.0.0:1]
> [Jul 29 18:59:06.743] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:-1390111168]
> [Jul 29 18:59:06.814] Server {47330630715728} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:06.875] Server {1104271680} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:07.286] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> [Jul 29 18:59:10.859] Server {47330630715728} NOTE: [log-coll] host down [128.81.1.0:0]
> [Jul 29 18:59:11.420] Server {1105324352} NOTE: [log-coll] host down [0.0.0.0:0]
> {code}
> all those random ip and port make me worry about the logging system, and I am afraid of that traffic.out will fill up the whole dist too.
> it may or may not be caused by the enable and disable the logging in squid.log and custom logging. I will do more testing and find out the key point.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira