[
https://issues.apache.org/jira/browse/TS-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089998#comment-13089998
]
Zhao Yongming commented on TS-896:
----------------------------------
I have setup a testing env for enable/disable the logging objects, for 5000
times, with no connection waste anymore.
the codes may have some crashing issue in the other parts of the logging
system, we need more care of the logging issue. I have just got one crash
during my heavy testing, I will file another bug on it.
this patch will make the connection to collation server reconnected if you do
not remove the logging object, that may be reused if we can, hopes we can fix
it in TS-910
> 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
> Assignee: Zhao Yongming
> Fix For: 3.1.1
>
> Attachments: TS-896.patch
>
>
> 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
