Page History

...

1. What Platforms does Traffic Server support
2. 'sudo make install' fails with '/usr/bin/install: invalid group nobody'
3. How do I enable forward proxy mode?
4. How do I access POST data in a Traffic Server plugin
5. How do I enable DNS lookups?
6. How do I enable SSL between Client/ATS/Origin end points?
7. What happens if Traffic Server crashes?
8. Do you have any sample configuration files?
9. How do I profile Traffic Server's performance?
10. How do get detailed logs for particular requests served by Traffic Server?
11. How to enable cache inspector and others in http_ui?
12. How do I setup a RAW disk cache?
13. How do I know what debug tags are available?
14. More questions?

...

• Linux is the primary platform supported.
• For other distributions such as FreeBSD, Mac OSX and OpenSolaris see http://svn.apache.org/repos/asf/trafficserver/traffic/trunk/ README

'sudo make install' fails with '/usr/bin/install: invalid group nobody'

...

• You use a transformation plugin. Details are available by visiting the Traffic Server SDK guide

How do I enable DNS lookups?

...

How do I enable SSL between Client/ATS/Origin end points?

• TODOSee Using SSL Termination section of the Administrator's Guide

What happens if Traffic Server crashes?

...

1. add these remap rules to remap.config, you may need to replace localhost to your own hostname if you don't access from localhost, you may need to modify the default port 8080 if you have changed it

   Code Block
   title remap.config borderStyle solid
   map http://localhost:8080/cache-internal/ http://{cache-internal} map http://localhost:8080/cache/ http://{cache} map http://localhost:8080/stat/ http://{stat} map http://localhost:8080/test/ http://{test} map http://localhost:8080/hostdb/ http://{hostdb} map http://localhost:8080/net/ http://{net} map http://localhost:8080/http/ http://{http}

2. enable http_ui from records.config, we use command line tool here：

   Code Block
   title command borderStyle solid
   traffic_line -s proxy.config.http_ui_enabled -v 3 traffic_line -s proxy.config.http.enable_http_info -v 1

3. get traffic_server aware of the change:

   Code Block
   title command borderStyle solid
   traffic_line -x

4. testing with nc:

   Code Block
   title command borderStyle solid
   echo -ene "GET http://localhost/stat/ HTTP/1.0\r\n\r\n" | nc -i 1 localhost 8080

...

You must also ensure the trafficserver user owns the device and has block-level access. To do this we utilize udev rules. This must be a physical device and not an LVM mapping:

    # /etc/udev/rules.d/50-ats.rules

...

    # Apache Traffic Server owns disk for RAW access
    KERNEL=="dm-2", OWNER="trafficserver"

How do I know what debug tags are available?

When enabling debug logging, you specify tags to filter the debug output with the proxy.config.diags.debug.tags option. The following command will show you all debug tags used in the trafficserver source code when outputting debug messages. Run it from inside the trafficserver source tree:

# This assumes gnu grep
grep -orh 'Debug("[^"]*' * | sort | uniq | sed 's/Debug("//'

More Frequently Asked Questions?

• There are additional frequently asked questions available in the Traffic Server admin guideAdministrator's Guide