Sources:


Building and configuring the Apache Traffic Server is super easy. There is only a few configuration changes to consider and some useful documentation areas to read over before beginning the procedure. This tutorial will build the server form source, but downloaded from the Apache Traffic Server website. Alternatively you can download from the repository or some Linux package managers such as apt-get and yum have older versions of the Traffic Server themselves. This tutorial will be using Apache Traffic Server 6.2.0.

Download

download the program with wget by executing the following commands

wget http://apache.parentingamerica.com/trafficserver/trafficserver-6.2.0.tar.bz2

Build

Execute the following commands to configure the project. The command ./configure will check you have all of the required dependencies for the installation. You may have to run it several times to ensure everything is included. Much of the online documentation provides general names for what is being looked for, but not everything is included.

tar xvf trafficserver-6.2.0.tar.bz2  
cd trafficserver-6.2.0.tar.bz2  
./configre

One of the more difficult dependencies is the openssl dependency. This required installing openssl, libssl1.0.0, libssl-dev, libsslcommon2 and libsslcommon2-dev on unbuntu to pass the configuration check

Install

Execute the next command to install

sudo make install  

Then execute the following and restart

sudo ldconfig  
sudo shutdown -r now  

You system will restart. ldconfig is a command that resets a number of control systems on linux. I ran into issues with the application until i ran this

Now your server is ready to go. Upon installation, the trafficserver command will be available anywhere in console. Simply start/stop/restart/status with a call like this:

sudo trafficserver <start/stop/restart/status>  

Keep an eye on the right hand side after each command as that will give u a status as to whether the command executed properly or not.

Debug / Problems

Errors can occur if the traffic server doesn't have permissions to the log files, which can cause more issues if you have other issues as well. By default the traffic server logs to the syslog daemon and information should be located in /var/log/trafficserver. Note if the trafficserver folder does not exist and does not have read/write permissions, logging will not work. Additionally, traffic server may write its logs to its install location under /usr/local/var/log/trafficserver. You can explicitly set the path that logs will be written to in the records.config file. Add or edit under the logging section of the file the proxy.config.log.logfile_dir attribute with the path to the desired logging location

If there are still issues and writing logs is not working, try executing the command traffic_ctl. This is another helper command for configuring the traffic server while it is still running. If there are errors, this command typicaly will dump them to console