[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[ https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795054#comment-13795054 ] Zhao Yongming commented on TS-2138: --- I think that clear issue is already fixed in 4.0.2 and later > Using linux native-AIO, restarting ATS causes complete cache data loss > -- > > Key: TS-2138 > URL: https://issues.apache.org/jira/browse/TS-2138 > Project: Traffic Server > Issue Type: Bug > Components: Cache >Reporter: bettydramit >Assignee: weijin > Fix For: sometime > > Attachments: ts-3.3.5-40.spec > > > ENV: centos 6 x86_64 gitmaster and > http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2 > ./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver > --enable-linux-native-aio --enable-reclaimable-freelist > > when restart ats ,my all hit data will be lost. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2216) Custom Log % not always initialized properly.
[ https://issues.apache.org/jira/browse/TS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795269#comment-13795269 ] Adam Twardowski commented on TS-2216: - The patch from TS-1988 had no effect, but I did notice that to trigger the issue all I need to do is telnet to the ATS port and disconnect without sending a request. There will be about a 20% chance of corruption at the end of the log line. My latest testing is against 4.0.2 > Custom Log % not always initialized properly. > > > Key: TS-2216 > URL: https://issues.apache.org/jira/browse/TS-2216 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Adam Twardowski > Fix For: 4.1.0 > > > Noticed this in my log output, it appears that the % log variable is > now always initialized properly. > {code} > > >"\"%\",\"%\",\"%<{X-Forwarded-For}cqh>\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\""/> > > "12/Sep/2013:17:48:16 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","à" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","1" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","±" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","·" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¤62R" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","r/player.swf" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","!" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:22 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¦62R" > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (TS-2216) Custom Log % not always initialized properly.
[ https://issues.apache.org/jira/browse/TS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795269#comment-13795269 ] Adam Twardowski edited comment on TS-2216 at 10/15/13 3:04 PM: --- The patch from TS-1988 had no effect, but I did notice that to trigger the issue all I need to do is telnet to the ATS port and disconnect without sending a request. There will be about a 20% chance of corruption at the end of the log line. My latest testing is against 4.0.2. Also, it's not specific to cquup, I tried removing that from the end of the format string and the issue still persists. was (Author: adam.twardowski): The patch from TS-1988 had no effect, but I did notice that to trigger the issue all I need to do is telnet to the ATS port and disconnect without sending a request. There will be about a 20% chance of corruption at the end of the log line. My latest testing is against 4.0.2 > Custom Log % not always initialized properly. > > > Key: TS-2216 > URL: https://issues.apache.org/jira/browse/TS-2216 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Adam Twardowski > Fix For: 4.1.0 > > > Noticed this in my log output, it appears that the % log variable is > now always initialized properly. > {code} > > >"\"%\",\"%\",\"%<{X-Forwarded-For}cqh>\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\""/> > > "12/Sep/2013:17:48:16 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","à" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","1" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","±" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","·" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¤62R" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","r/player.swf" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","!" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:22 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¦62R" > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2216) Custom Log % not always initialized properly.
[ https://issues.apache.org/jira/browse/TS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795326#comment-13795326 ] Adam Twardowski commented on TS-2216: - The problem appears to be using cquup after cquuh in the format line. Using the 2 format lines below, test4 exhibits the issue, test5 works fine. {code} %"/> %"/> {code} > Custom Log % not always initialized properly. > > > Key: TS-2216 > URL: https://issues.apache.org/jira/browse/TS-2216 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Adam Twardowski > Fix For: 4.1.0 > > > Noticed this in my log output, it appears that the % log variable is > now always initialized properly. > {code} > > >"\"%\",\"%\",\"%<{X-Forwarded-For}cqh>\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\""/> > > "12/Sep/2013:17:48:16 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","à" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","1" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","±" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","·" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¤62R" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","r/player.swf" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","!" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:22 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¦62R" > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2216) Custom Log % not always initialized properly.
[ https://issues.apache.org/jira/browse/TS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795332#comment-13795332 ] Adam Twardowski commented on TS-2216: - Test6 below also causes the problem, so it appears that the actual issue is in cquuh. {code} %"/> {code} > Custom Log % not always initialized properly. > > > Key: TS-2216 > URL: https://issues.apache.org/jira/browse/TS-2216 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Adam Twardowski > Fix For: 4.1.0 > > > Noticed this in my log output, it appears that the % log variable is > now always initialized properly. > {code} > > >"\"%\",\"%\",\"%<{X-Forwarded-For}cqh>\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\""/> > > "12/Sep/2013:17:48:16 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","à" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","1" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","±" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","·" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¤62R" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","r/player.swf" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","!" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:22 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¦62R" > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[ https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13795722#comment-13795722 ] Scott Harris commented on TS-2138: -- Have tested with 4.0.2 and see the same result with aio enabled [Oct 16 09:06:19.588] Server {0x7f12e09407e0} NOTE: Clearing Cache [Oct 16 09:06:19.598] Server {0x7f12df992700} NOTE: Clearing Disk: /dev/sdd [Oct 16 09:06:19.598] Server {0x7f12df992700} NOTE: Clearing Disk: /dev/sdd [Oct 16 09:06:19.604] Server {0x7f12df992700} NOTE: clearing cache directory '/dev/sdd 16384:5242878' [Oct 16 09:06:19.606] Server {0x7f12dfa93700} NOTE: clearing cache directory '/dev/sdd 16384:5242878' > Using linux native-AIO, restarting ATS causes complete cache data loss > -- > > Key: TS-2138 > URL: https://issues.apache.org/jira/browse/TS-2138 > Project: Traffic Server > Issue Type: Bug > Components: Cache >Reporter: bettydramit >Assignee: weijin > Fix For: sometime > > Attachments: ts-3.3.5-40.spec > > > ENV: centos 6 x86_64 gitmaster and > http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2 > ./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver > --enable-linux-native-aio --enable-reclaimable-freelist > > when restart ats ,my all hit data will be lost. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-1545) possible crash in records stat snap
[ https://issues.apache.org/jira/browse/TS-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796272#comment-13796272 ] William Bardwell commented on TS-1545: -- We saw a crash similar to this (although due to bad start/end values in an entry causing a crash when it tried to allocate too much memory.) Either there is some basic issue that causes corruption in that file, or it was due to traffic_server restarting at inopportune times, and that file needs a check sum to make detecting corruption easier. Worst of all, re-starting didn't fix the bad file, it just crashed again and again. > possible crash in records stat snap > --- > > Key: TS-1545 > URL: https://issues.apache.org/jira/browse/TS-1545 > Project: Traffic Server > Issue Type: Bug > Components: Core, Stats >Affects Versions: 3.3.0 > Environment: debug build, long time regression testing >Reporter: Zhao Yongming > Fix For: 5.0.0 > > Attachments: records.snap, stats.snap > > > when I running regression testing in the loop script, we come to fail to > start the server. well, the codes may handle the issue when we build without > --enable-debug, but that looks like we have something may break records snap. > open this issue in case someone need it. > {code} > [TrafficServer] using root directory '/opt/ats' > FATAL: RecMessage.cc:426: failed assert `eh->magic == REC_MESSAGE_ELE_MAGIC` > /opt/ats/bin/traffic_server - STACK TRACE: > /opt/ats/lib/libtsutil.so.3(ink_fatal_die+0x0)[0x77baeca1] > /opt/ats/lib/libtsutil.so.3(_Z12ink_get_randv+0x0)[0x77badbb8] > /opt/ats/bin/traffic_server(_Z23RecMessageUnmarshalNextP13RecMessageHdrP13RecMessageItrPP9RecRecord+0xbf)[0x6ed860] > /opt/ats/bin/traffic_server(_Z16RecReadStatsFilev+0xc1)[0x6e5e36] > /opt/ats/bin/traffic_server(_Z11RecCoreInit8RecModeTP5Diags+0xec)[0x6e254b] > /opt/ats/bin/traffic_server(_Z14RecProcessInit8RecModeTP5Diags+0x3b)[0x6e7769] > /opt/ats/bin/traffic_server[0x51d4a5] > /opt/ats/bin/traffic_server(main+0x1df)[0x51ee39] > /lib64/libc.so.6(__libc_start_main+0xed)[0x7515b60d] > /opt/ats/bin/traffic_server[0x4d8f99] > Program received signal SIGABRT, Aborted. > 0x7516ec15 in raise () from /lib64/libc.so.6 > (gdb) bt > #0 0x7516ec15 in raise () from /lib64/libc.so.6 > #1 0x7517008b in abort () from /lib64/libc.so.6 > #2 0x77baeb2c in ink_die_die_die (retval=1) at ink_error.cc:43 > #3 0x77baebfe in ink_fatal_va(int, const char *, typedef > __va_list_tag __va_list_tag *) (return_code=1, > message_format=0x77bca3e0 "%s:%d: failed assert `%s`", > ap=0x7fffc8b8) at ink_error.cc:65 > #4 0x77baeca1 in ink_fatal (return_code=1, > message_format=0x77bca3e0 "%s:%d: failed assert `%s`") at ink_error.cc:73 > #5 0x77badbb8 in _ink_assert (expression=0x76ffa0 "eh->magic == > REC_MESSAGE_ELE_MAGIC", file=0x76fe40 "RecMessage.cc", line=426) > at ink_assert.cc:38 > #6 0x006ed860 in RecMessageUnmarshalNext (msg=0xfe6110, > itr=0x7fffca00, record=0x7fffca10) at RecMessage.cc:426 > #7 0x006e5e36 in RecReadStatsFile () at P_RecCore.i:569 > #8 0x006e254b in RecCoreInit (mode_type=RECM_STAND_ALONE, > _diags=0xfe5f70) at RecCore.cc:209 > #9 0x006e7769 in RecProcessInit (mode_type=RECM_STAND_ALONE, > _diags=0xfe5f70) at RecProcess.cc:313 > #10 0x0051d4a5 in initialize_process_manager () at Main.cc:413 > #11 0x0051ee39 in main (argc=1, argv=0x7fffdd08) at Main.cc:1409 > (gdb) f 6 > #6 0x006ed860 in RecMessageUnmarshalNext (msg=0xfe6110, > itr=0x7fffca00, record=0x7fffca10) at RecMessage.cc:426 > 426 ink_debug_assert(eh->magic == REC_MESSAGE_ELE_MAGIC); > (gdb) l > 421 itr->ele_hdr = (RecMessageEleHdr *) ((char *) (msg) + > itr->ele_hdr->o_next); > 422 itr->next += 1; > 423 eh = itr->ele_hdr; > 424 } > 425 > 426 ink_debug_assert(eh->magic == REC_MESSAGE_ELE_MAGIC); > 427 > 428 // If the file is corrupt, ignore the the rest of the file. > 429 if (eh->magic != REC_MESSAGE_ELE_MAGIC) { > 430 Warning("Persistent statistics file records.stat is corrupted. > Ignoring the rest of the file\n"); > (gdb) p eh->magic > $1 = 0 > (gdb) p REC_MESSAGE_ELE_MAGIC > $2 = 4027445261 > (gdb) p eh > $3 = (RecMessageEleHdr *) 0xff4138 > (gdb) p *eh > $4 = {magic = 0, o_next = 0} > (gdb) f 7 > #7 0x006e5e36 in RecReadStatsFile () at P_RecCore.i:569 > 569 } while (RecMessageUnmarshalNext(m, &itr, &r) != REC_ERR_FAIL); > (gdb) l > 564 if (RecMessageUnmarshalFirst(m, &itr, &r) != REC_ERR_FAIL) { > 565 do { > 566 if ((r->name == NULL) || (!strlen(r->name))) > 567 continue; > 568 RecSetRecord(r->rec
[jira] [Created] (TS-2272) cache init is too slow
Zhao Yongming created TS-2272: - Summary: cache init is too slow Key: TS-2272 URL: https://issues.apache.org/jira/browse/TS-2272 Project: Traffic Server Issue Type: Bug Components: Cache, Core Reporter: Zhao Yongming from the log, that each disk is wasting about 1-3s to get initialized, looks that is working in serial way, may need more work to get all disk done in 1-3s {code} [Oct 15 18:16:52.352] Server {0x2b77c9a19700} WARNING: disk header different for disk /dev/sdd: clearing the disk [Oct 15 18:16:52.359] Server {0x2b77c9413700} WARNING: disk header different for disk /dev/sde: clearing the disk [Oct 15 18:16:52.364] Server {0x2b77c9a19700} WARNING: disk header different for disk /dev/sdf: clearing the disk [Oct 15 18:16:52.369] Server {0x2b77c9413700} WARNING: disk header different for disk /dev/sdg: clearing the disk [Oct 15 18:16:52.375] Server {0x2b77c9c1b700} WARNING: disk header different for disk /dev/sdh: clearing the disk [Oct 15 18:16:52.382] Server {0x2b77c28c1e40} NOTE: traffic server running [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdb [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdc [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdd [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sde [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdf [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdg [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdh [Oct 15 18:16:52.474] Server {0x2b77c9918700} NOTE: clearing cache directory '/dev/sdb 122880:73257708' [Oct 15 18:16:53.637] Server {0x2b77c9918700} NOTE: clearing cache directory '/dev/sdc 122880:73257708' [Oct 15 18:16:54.797] Server {0x2b77c9918700} NOTE: clearing cache directory '/dev/sdd 122880:73257708' [Oct 15 18:16:55.961] Server {0x2b77c9918700} NOTE: clearing cache directory '/dev/sde 122880:73257708' [Oct 15 18:16:57.089] Server {0x2b77c9918700} NOTE: clearing cache directory '/dev/sdf 122880:73257708' [Oct 15 18:16:58.216] Server {0x2b77c9918700} NOTE: clearing cache directory '/dev/sdg 122880:73257708' [Oct 15 18:16:59.326] Server {0x2b77c9918700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 15 18:17:05.417] Server {0x2b77c9f1e700} NOTE: cache enabled [Oct 15 18:17:16.811] {0x7f40b73847e0} STATUS: opened /var/log/trafficserver/diags.log [Oct 15 18:17:16.811] {0x7f40b73847e0} NOTE: updated diags config [Oct 15 18:17:16.814] Server {0x7f40b73847e0} NOTE: cache clustering disabled [Oct 15 18:17:16.840] Server {0x7f40b73847e0} NOTE: CLEAR [Oct 15 18:17:16.840] Server {0x7f40b73847e0} NOTE: Clearing Configuration [Oct 15 18:17:16.840] Server {0x7f40b73847e0} NOTE: Clearing Host Database [Oct 15 18:17:16.858] Server {0x7f40b73847e0} NOTE: Clearing Cache [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdb [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdc [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdd [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sde [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdf [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdg [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdh [Oct 15 18:17:16.903] Server {0x7f40b40da700} NOTE: clearing cache directory '/dev/sdb 122880:73257708' [Oct 15 18:17:18.162] Server {0x7f40b40da700} NOTE: clearing cache directory '/dev/sdc 122880:73257708' [Oct 15 18:17:19.391] Server {0x7f40b40da700} NOTE: clearing cache directory '/dev/sdd 122880:73257708' [Oct 15 18:17:20.608] Server {0x7f40b40da700} NOTE: clearing cache directory '/dev/sde 122880:73257708' [Oct 15 18:17:21.837] Server {0x7f40b40da700} NOTE: clearing cache directory '/dev/sdf 122880:73257708' [Oct 15 18:17:23.083] Server {0x7f40b40da700} NOTE: clearing cache directory '/dev/sdg 122880:73257708' [Oct 15 18:17:24.387] Server {0x7f40b40da700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 15 18:17:30.790] Server {0x7f40b3ad4700} NOTE: cache enabled [Oct 15 18:17:30.956] Server {0x7f40b41db700} NOTE: CLEAR, succeeded {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (TS-2272) cache init is too slow
[ https://issues.apache.org/jira/browse/TS-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhao Yongming updated TS-2272: -- Priority: Minor (was: Major) Affects Version/s: 4.1.0 Assignee: weijin Issue Type: Improvement (was: Bug) > cache init is too slow > -- > > Key: TS-2272 > URL: https://issues.apache.org/jira/browse/TS-2272 > Project: Traffic Server > Issue Type: Improvement > Components: Cache, Core >Affects Versions: 4.1.0 >Reporter: Zhao Yongming >Assignee: weijin >Priority: Minor > > from the log, that each disk is wasting about 1-3s to get initialized, looks > that is working in serial way, may need more work to get all disk done in 1-3s > {code} > [Oct 15 18:16:52.352] Server {0x2b77c9a19700} WARNING: disk header different > for disk /dev/sdd: clearing the disk > [Oct 15 18:16:52.359] Server {0x2b77c9413700} WARNING: disk header different > for disk /dev/sde: clearing the disk > [Oct 15 18:16:52.364] Server {0x2b77c9a19700} WARNING: disk header different > for disk /dev/sdf: clearing the disk > [Oct 15 18:16:52.369] Server {0x2b77c9413700} WARNING: disk header different > for disk /dev/sdg: clearing the disk > [Oct 15 18:16:52.375] Server {0x2b77c9c1b700} WARNING: disk header different > for disk /dev/sdh: clearing the disk > [Oct 15 18:16:52.382] Server {0x2b77c28c1e40} NOTE: traffic server running > [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdb > [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdc > [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdd > [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sde > [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdf > [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdg > [Oct 15 18:16:52.469] Server {0x2b77c9918700} NOTE: Clearing Disk: /dev/sdh > [Oct 15 18:16:52.474] Server {0x2b77c9918700} NOTE: clearing cache directory > '/dev/sdb 122880:73257708' > [Oct 15 18:16:53.637] Server {0x2b77c9918700} NOTE: clearing cache directory > '/dev/sdc 122880:73257708' > [Oct 15 18:16:54.797] Server {0x2b77c9918700} NOTE: clearing cache directory > '/dev/sdd 122880:73257708' > [Oct 15 18:16:55.961] Server {0x2b77c9918700} NOTE: clearing cache directory > '/dev/sde 122880:73257708' > [Oct 15 18:16:57.089] Server {0x2b77c9918700} NOTE: clearing cache directory > '/dev/sdf 122880:73257708' > [Oct 15 18:16:58.216] Server {0x2b77c9918700} NOTE: clearing cache directory > '/dev/sdg 122880:73257708' > [Oct 15 18:16:59.326] Server {0x2b77c9918700} NOTE: clearing cache directory > '/dev/sdh 122880:73257708' > [Oct 15 18:17:05.417] Server {0x2b77c9f1e700} NOTE: cache enabled > [Oct 15 18:17:16.811] {0x7f40b73847e0} STATUS: opened > /var/log/trafficserver/diags.log > [Oct 15 18:17:16.811] {0x7f40b73847e0} NOTE: updated diags config > [Oct 15 18:17:16.814] Server {0x7f40b73847e0} NOTE: cache clustering disabled > [Oct 15 18:17:16.840] Server {0x7f40b73847e0} NOTE: CLEAR > [Oct 15 18:17:16.840] Server {0x7f40b73847e0} NOTE: Clearing Configuration > [Oct 15 18:17:16.840] Server {0x7f40b73847e0} NOTE: Clearing Host Database > [Oct 15 18:17:16.858] Server {0x7f40b73847e0} NOTE: Clearing Cache > [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdb > [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdc > [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdd > [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sde > [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdf > [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdg > [Oct 15 18:17:16.898] Server {0x7f40b40da700} NOTE: Clearing Disk: /dev/sdh > [Oct 15 18:17:16.903] Server {0x7f40b40da700} NOTE: clearing cache directory > '/dev/sdb 122880:73257708' > [Oct 15 18:17:18.162] Server {0x7f40b40da700} NOTE: clearing cache directory > '/dev/sdc 122880:73257708' > [Oct 15 18:17:19.391] Server {0x7f40b40da700} NOTE: clearing cache directory > '/dev/sdd 122880:73257708' > [Oct 15 18:17:20.608] Server {0x7f40b40da700} NOTE: clearing cache directory > '/dev/sde 122880:73257708' > [Oct 15 18:17:21.837] Server {0x7f40b40da700} NOTE: clearing cache directory > '/dev/sdf 122880:73257708' > [Oct 15 18:17:23.083] Server {0x7f40b40da700} NOTE: clearing cache directory > '/dev/sdg 122880:73257708' > [Oct 15 18:17:24.387] Server {0x7f40b40da700} NOTE: clearing cache directory > '/dev/sdh 122880:73257708' > [Oct 15 18:17:30.790] Server {0x7f40b3ad4700} NOTE: cache enabled > [Oct 15 18:17:30.956] Server {0x7f40b41db700} NOTE: CLEAR, succeeded > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2216) Custom Log % not always initialized properly.
[ https://issues.apache.org/jira/browse/TS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796379#comment-13796379 ] Zhao Yongming commented on TS-2216: --- when you telnet in do nothing and quit, that is a empty request, which does not valid in the request. the unmaped request is empty. we may need to check that case. > Custom Log % not always initialized properly. > > > Key: TS-2216 > URL: https://issues.apache.org/jira/browse/TS-2216 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Adam Twardowski > Fix For: 4.1.0 > > > Noticed this in my log output, it appears that the % log variable is > now always initialized properly. > {code} > > >"\"%\",\"%\",\"%<{X-Forwarded-For}cqh>\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\""/> > > "12/Sep/2013:17:48:16 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","à" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","1" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","±" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","·" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¤62R" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","r/player.swf" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","!" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:22 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¦62R" > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[ https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796387#comment-13796387 ] Zhao Yongming commented on TS-2138: --- yeah, confirmed: {code} [Oct 16 11:54:15.228] Server {0x7f300baba7e0} NOTE: cache clustering disabled [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: CLEAR [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: Clearing Configuration [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: Clearing Host Database [Oct 16 11:54:15.271] Server {0x7f300baba7e0} NOTE: Clearing Cache [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.369] Server {0x7f3008109700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.394] Server {0x7f3008008700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.410] Server {0x7f3007f07700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.460] Server {0x7f3007d05700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.460] Server {0x7f3007c04700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.491] Server {0x7f3007e06700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.492] Server {0x7f3007b03700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:25.084] Server {0x7f3007b03700} NOTE: cache enabled [Oct 16 11:54:25.265] Server {0x7f300820a700} NOTE: CLEAR, succeeded {ode} > Using linux native-AIO, restarting ATS causes complete cache data loss > -- > > Key: TS-2138 > URL: https://issues.apache.org/jira/browse/TS-2138 > Project: Traffic Server > Issue Type: Bug > Components: Cache >Reporter: bettydramit >Assignee: weijin > Fix For: sometime > > Attachments: ts-3.3.5-40.spec > > > ENV: centos 6 x86_64 gitmaster and > http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2 > ./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver > --enable-linux-native-aio --enable-reclaimable-freelist > > when restart ats ,my all hit data will be lost. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (TS-2216) Custom Log % not always initialized properly.
[ https://issues.apache.org/jira/browse/TS-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796388#comment-13796388 ] Leif Hedstrom commented on TS-2216: --- Yeah it sounds like cquuh is foobared , it's an addition done a while back. > Custom Log % not always initialized properly. > > > Key: TS-2216 > URL: https://issues.apache.org/jira/browse/TS-2216 > Project: Traffic Server > Issue Type: Bug > Components: Logging >Reporter: Adam Twardowski > Fix For: 4.1.0 > > > Noticed this in my log output, it appears that the % log variable is > now always initialized properly. > {code} > > >"\"%\",\"%\",\"%<{X-Forwarded-For}cqh>\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\",\"%\""/> > > "12/Sep/2013:17:48:16 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","à" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","1" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","±" > "12/Sep/2013:17:48:17 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:18 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¢62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","£62R" > "12/Sep/2013:17:48:19 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","·" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¤62R" > "12/Sep/2013:17:48:20 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","r/player.swf" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¡" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","!" > "12/Sep/2013:17:48:21 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¥62R" > "12/Sep/2013:17:48:22 > -0500","0.000","-","ERROR_UNKNOWN(90)","000","15","0","-","-","-","¦62R" > {code} -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (TS-2138) Using linux native-AIO, restarting ATS causes complete cache data loss
[ https://issues.apache.org/jira/browse/TS-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796387#comment-13796387 ] Zhao Yongming edited comment on TS-2138 at 10/16/13 3:59 AM: - yeah, confirmed: {code} [Oct 16 11:54:15.228] Server {0x7f300baba7e0} NOTE: cache clustering disabled [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: CLEAR [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: Clearing Configuration [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: Clearing Host Database [Oct 16 11:54:15.271] Server {0x7f300baba7e0} NOTE: Clearing Cache [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.369] Server {0x7f3008109700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.394] Server {0x7f3008008700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.410] Server {0x7f3007f07700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.460] Server {0x7f3007d05700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.460] Server {0x7f3007c04700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.491] Server {0x7f3007e06700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.492] Server {0x7f3007b03700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:25.084] Server {0x7f3007b03700} NOTE: cache enabled [Oct 16 11:54:25.265] Server {0x7f300820a700} NOTE: CLEAR, succeeded {code} was (Author: zym): yeah, confirmed: {code} [Oct 16 11:54:15.228] Server {0x7f300baba7e0} NOTE: cache clustering disabled [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: CLEAR [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: Clearing Configuration [Oct 16 11:54:15.253] Server {0x7f300baba7e0} NOTE: Clearing Host Database [Oct 16 11:54:15.271] Server {0x7f300baba7e0} NOTE: Clearing Cache [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.363] Server {0x7f300860e700} NOTE: Clearing Disk: /dev/sdh [Oct 16 11:54:15.369] Server {0x7f3008109700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.394] Server {0x7f3008008700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.410] Server {0x7f3007f07700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.460] Server {0x7f3007d05700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.460] Server {0x7f3007c04700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.491] Server {0x7f3007e06700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:15.492] Server {0x7f3007b03700} NOTE: clearing cache directory '/dev/sdh 122880:73257708' [Oct 16 11:54:25.084] Server {0x7f3007b03700} NOTE: cache enabled [Oct 16 11:54:25.265] Server {0x7f300820a700} NOTE: CLEAR, succeeded {ode} > Using linux native-AIO, restarting ATS causes complete cache data loss > -- > > Key: TS-2138 > URL: https://issues.apache.org/jira/browse/TS-2138 > Project: Traffic Server > Issue Type: Bug > Components: Cache >Reporter: bettydramit >Assignee: weijin > Fix For: sometime > > Attachments: ts-3.3.5-40.spec > > > ENV: centos 6 x86_64 gitmaster and > http://people.apache.org/~zwoop/rel-candidates/trafficserver-3.3.5-dev.tar.bz2 > ./configure --enable-layout=Gentoo --libdir=%{_libdir}/trafficserver > --enable-linux-native-aio --enable-reclaimable-freelist > > when restart ats ,my all hit data will be lost. -- This message was sent by Atlassian JIRA (v6.1#6144)