This is not an ideal situation for the appliance. If stderr_path or stdout_path is not set in unicorn.rb then stderr log goes to syslog. Single API hit generates nearly identical entry in at least 3 log files (including nginx which fronts unicorn)
we should look into refactoring the way logging is done in the ontologies_api
Unicorn generates 3 logs:
production.log - access log unicorn.stderr.log - access log + exeptions/error stack traces unicorn.stdout.log - app notifications
This is not an ideal situation for the appliance. If stderr_path or stdout_path is not set in unicorn.rb then stderr log goes to syslog. Single API hit generates nearly identical entry in at least 3 log files (including nginx which fronts unicorn)
we should look into refactoring the way logging is done in the ontologies_api