[ 
https://issues.apache.org/jira/browse/TC-546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135933#comment-16135933
 ] 

Steve Malenfant commented on TC-546:
------------------------------------

Trafficserver diags.log :

{code:java}
[Aug 21 21:51:26.160] Server {0x2b624f6b9dc0} ERROR: [ReverseProxy] failed to 
add remap rule at /opt/trafficserver/etc/trafficserver/remap.config line 30: 
Failed to create instance for plugin 
"/opt/trafficserver/libexec/trafficserver/url_sig.so": [TSRemapNewInstance] - 
Error opening file 
/opt/trafficserver/etc/trafficserver//opt/trafficserver/etc/trafficserver/url_sig_example.config.
[Aug 21 21:51:26.160] Server {0x2b624f6b9dc0} WARNING: something failed during 
BuildTable() -- check your remap plugins!
[Aug 21 21:51:26.160] Server {0x2b624f6b9dc0} WARNING: Can not load the remap 
table, exiting out!
[Aug 21 21:51:44.488] {0x2b8f5afe1dc0} STATUS: opened 
/opt/trafficserver/var/log/trafficserver/diags.log
[Aug 21 21:51:44.488] {0x2b8f5afe1dc0} NOTE: updated diags config

{code}


> error_url required in the url_sig file
> --------------------------------------
>
>                 Key: TC-546
>                 URL: https://issues.apache.org/jira/browse/TC-546
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: Traffic Ops 2.1
>            Reporter: Steve Malenfant
>
> The error_url parameter in the URL signature file is required, if not present 
> trafficserver doesn't start. 
> Seems like TO handles generating the proper location of for the url_sig in 
> the the database to all servers assigned, although the error_url is not.
> - I tried to put the parameter in the DS profile parameter, but it didn't get 
> generated on disk.
> - Thinking that a default of `error_url = 403` should be dynamic generated if 
> not present to prevent trafficserver from starting. This could have other 
> implication.
> - Other suggestions?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to