-
Notifications
You must be signed in to change notification settings - Fork 7
Finding the logs
These are the default locations of the logs for the various components of the hydra stack.
The catalina.out log is the main tomcat log - other logs in the same directory can also be useful
Ubuntu: /var/log/tomcat7/catalina.out
Centos: /usr/share/tomcat6/logs/catalina.out
Ubuntu/Centos: /var/log/mysqld.log
Note: this log is owned by the mysql user - you will need to use sudo to view it
Solr logging is directed to the tomcat log; see above.
Note: if you're using a different servlet (e.g. jetty), your solr messages will show up in that log.
Many fedora messages are directed to the tomcat log; see above.
Note: if you're using a different servlet (e.g. jetty), these fedora messages will show up in that log.
Fedora also generates a more detailed log in the server/log sub-directory of your fedora directory. If you installed fedora in /opt, you'll find a fedora log at /opt/fedora/server/logs/fedora.log.
Passenger messages are directed to the apache log; see below.
Ubuntu: /var/log/apache2/error.log or /var/log/apache2/access.log
CentOS: /var/log/httpd/error.log or /var/log/httpd/access.log
By default the application logs to the log sub-directory of your application directory. The filename of the log depends on your rails environment. The rails environment defaults to production. If you are running in production and your code is in /opt/$HYDRA_NAME, then your log will be /opt/$HYDRA_NAME/log/production.log.
- Errors getting resque-pool to run will be logged in /opt/$HYDRA_NAME/log/resque-pool.stderr.log.
- Errors generated by resque workers are easiest to see in the resque web interface at http://yourwebsite/admin/queues
- By default redis errors are sent to /dev/null when running as a daemon - if you want to log redis errors to a file, change the logfile line in /etc/redis/6379.conf