1. Setup

FileAgo v1.0 Created on: October 19, 2018

Is FileAgo running?

The status of FileAgo services can be determined by checking whether the containers are running or not in Docker. Execute:

docker ps

The command will list all running containers. The list must show the below 3 containers as running (NOTE: container id will be different):

CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS                          NAMES
c852e5e79684        fileago_nginx            "/bin/sh -c '/bin/..."   2 days ago          Up 2 days           80/tcp,>443/tcp   fileago_nginx_1
8af228408cac        fileago_dms              "/sbin/tini -- /bi..."   2 days ago          Up 2 days           8080/tcp                       fileago_dms_1
971a0c6e0900        neo4j:3.2.1-enterprise   "/docker-entrypoin..."   2 days ago          Up 2 days           7473-7474/tcp, 7687/tcp        fileago_db_1

Check for error logs

Errors in fileago_dms container are output to the screen, and is accessible via:

docker logs 8af228408cac
You must replace 8af228408cac with the container id of fileago_dms container in your server.

High work-load environments

CAUTION: Only follow if you know what you are doing.

These are some of the issues that we have come across while running FileAgo in high work-load environments.

Runaway soffice processes

If file conversion (from Office to pdf) takes a loooong time, then it can become a runaway process, and there could be many of them eventually. In such cases. it is recommended to run this cron on the server which will kill those processes that are running for more than 10 minutes:

*/5 * * * * ps -eo pid,comm,etimes,args | grep soffice | awk '$3 > 600 {print $1, $4, $3}' | grep soffice | cut -f1 -d" " | xargs /usr/bin/kill -9 > /dev/null 2>&1

Disk usage in / is 100%

Most likely reason will be docker folder /var/lib/docker taking a large chunk of the disk.

If that is the case, you should stop the FileAgo docker containers, followed by the docker daemon. Then move this folder to somewhere else, for e.g., /opt/fileago/docker (assuming that the target is on a separate disk), create/edit the file /etc/docker/daemon.json to reflect the new path:

	"data-root": "/opt/fileago/docker"

Finally, start docker daemon and the FileAgo docker containers and confirm that everything is back and running fine.