Logs

This page contains information about the logs maintained by the OPS system. Logs can be useful for monitoring the system and for tracking down the source of unexpected errors.

---

Server Logs

Django Logs

PostgreSQL Logs

GeoServer Log

---

Server Logs

Logs concerning server access and errors can be found in /var/www/sites/ops.cresis.ku.edu/logs/ and in /etc/httpd/logs/

Django Logs

Python and Django have documentation on logging. Note that the Django logging documentation draws heavily on the python documentation. This is because Django employs the Python logging module directly.

• Note: the Django logs are currently set to be cleared on the first of every month by a CRON job.

• There is currently only one view in the OPS Django application that maintains logs: createPath(). The log keeps track of the progress of path insert and can be used to monitor progress of especially large inserts. This log can be found in /cresis/snfs1/web/ops/django_logs/.

• More logs can be added to views and other parts of the OPS Django application if needed by following the examples in the documentation and createPath().

PostgreSQL Logs

PostgreSQL maintains logs in the /db/pgsql/9.3/pg_log/ directory. Currently, the PostgreSQL configuration is set to keep a log for each day of the week, which is overwritten each week. The format, verbosity, and frequency of the logs maintained by postgreSQL can be edited in the postgresql.conf file located in the /db/pgsql/9.3/ directory.

• PostgreSQL logs are text documents that can become very large and difficult to interpret. For this reason, a report based on the logs is generated each week. This report is an html document that can be opened with any standard web browser and makes reviewing database activity and performance very easy. It is highly recommended that these reports be looked at on a weekly basis to find areas where the database could be optimized. The PostgreSQL html report is located in the /db/postgresql_reports/ directory.

• Note that the PostgreSQL reports are generated each week on Sunday by a CRON job.

• Note that PostgreSQL reports are currently set to be removed from /db/postgresql_reports/ by a CRON job when they are more than 2 months old.

• PostgreSQL reports are generated using pgBadger.

• PostgreSQL reports can be created on demand using the createPostgresqlReport.sh tool located in /vagrant/conf/tools/:

cd /vagrant/conf/tools/
sh createPostgresqlReport.sh /path/to/output/dir/

##GeoServer Log The GeoServer log can be found in the GeoServer web administration interface (ops.cresis.ku.edu/geoserver/web) under the About & Status header in the sidebar.