trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alan Carroll <solidwallofc...@yahoo-inc.com>
Subject Re: Defaulting in records.config
Date Thu, 25 May 2017 18:17:05 GMT
See if doing "traffic_ctl config reload" triggers this (or whatever replaced traffic_line -x)


> p.s. Sorry for all the newbie questions lately.  There’ll be less as we get more experience
:)
Haha, sadly no. That's just not how it works here at Traffic Server :-P.
On Thursday, May 25, 2017, 1:05:33 PM CDT, Dunkin, Nick <Nick.Dunkin@ccur.com> wrote:Hi
We’ve come across some behavior from Traffic Server (7.0.0) that we’re struggling to understand.
At certain points in time, we don’t know if it’s around crashes, or restarts, or just
randomly, we are finding extra entries in our records.config.  These entries set certain
parameters to their default values.  It’s always to the default values.  We can’t pinpoint
an exact triggering factor because at the moment we are always finding them after the act.
For example the most recent addition was the following:

CONFIG proxy.config.cache.control.filename STRING cache.config
 
CONFIG proxy.config.cache.ip_allow.filename STRING ip_allow.config
 
CONFIG proxy.config.log.config.filename STRING logging.config
 
CONFIG proxy.config.url_remap.filename STRING remap.config




Is this known behavior? and we are causing it some way that we’re not aware of.




As far as I know these files aren’t being altered manually, or through traffic_ctl set.




Thanks,




Nick




p.s. Sorry for all the newbie questions lately.  There’ll be less as we get more experience
:)



 <!--#yiv6199080026 _filtered #yiv6199080026 {font-family:"Cambria Math";panose-1:0 0 0
0 0 0 0 0 0 0;} _filtered #yiv6199080026 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2
4;}#yiv6199080026 #yiv6199080026 p.yiv6199080026MsoNormal, #yiv6199080026 li.yiv6199080026MsoNormal,
#yiv6199080026 div.yiv6199080026MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times
New Roman";}#yiv6199080026 a:link, #yiv6199080026 span.yiv6199080026MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv6199080026
a:visited, #yiv6199080026 span.yiv6199080026MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv6199080026
span.yiv6199080026EmailStyle17 {font-family:Calibri;color:windowtext;}#yiv6199080026 span.yiv6199080026EmailStyle18
{font-family:Calibri;color:windowtext;}#yiv6199080026 span.yiv6199080026EmailStyle19 {font-family:Calibri;color:windowtext;}#yiv6199080026
span.yiv6199080026msoIns {text-decoration:underline;color:teal;}#yiv6199080026 .yiv6199080026MsoChpDefault
{font-size:10.0pt;} _filtered #yiv6199080026 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv6199080026
div.yiv6199080026WordSection1 {}-->
Nick Dunkin
 
Principal Engineer
 
o:   678.258.4071
 
e:   Nick.Dunkin@curr.com 
 
4375 River Green Pkwy # 100, Duluth, GA 30096, USA
 

 
Mime
  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message