Troubleshooting

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.

A server running FileAgo (without chat) will see the following containers running (NOTE: container id will be different in your server)

[root@localhost fileago]# docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                                    NAMES
a8f35521cff2        fileago_nginx                 "/bin/sh -c '/bin/sh…"   23 hours ago        Up 23 hours         80/tcp, 9999/tcp, 0.0.0.0:443->443/tcp   fileago_nginx_1
adc015af7fec        fileago_lool                  "/bin/sh -c 'bash st…"   23 hours ago        Up 23 hours         9980/tcp                                 fileago_lool_1
64d800273967        fileago_dms                   "/sbin/tini -- /bin/…"   23 hours ago        Up 23 hours         8080/tcp                                 fileago_dms_1
d96f988cf099        graphfoundation/ongdb:3.5.1   "/sbin/tini -g -- /d…"   23 hours ago        Up 23 hours         7473-7474/tcp, 7687/tcp                  fileago_db_1

A server running FileAgo + chat will see the follow containers running (NOTE: container id will be different in your server):

[root@localhost fileago]# docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                                    NAMES
a8f35521cff2        fileago_nginx                 "/bin/sh -c '/bin/sh…"   23 hours ago        Up 23 hours         80/tcp, 9999/tcp, 0.0.0.0:443->443/tcp   fileago_nginx_1
adc015af7fec        fileago_lool                  "/bin/sh -c 'bash st…"   23 hours ago        Up 23 hours         9980/tcp                                 fileago_lool_1
f7ed455a7511        rocket.chat:latest            "bash -c 'for i in `…"   23 hours ago        Up 23 hours         3000/tcp                                 fileago_rocketchat_1
64d800273967        fileago_dms                   "/sbin/tini -- /bin/…"   23 hours ago        Up 23 hours         8080/tcp                                 fileago_dms_1
c2f8a7f9c27d        mongo:4.0                     "docker-entrypoint.s…"   23 hours ago        Up 23 hours         27017/tcp                                fileago_mongo_1
d96f988cf099        graphfoundation/ongdb:3.5.1   "/sbin/tini -g -- /d…"   23 hours ago        Up 23 hours         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 64d800273967

High work-load environments

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.

Read more

Managing Fonts Uninstall FileAgo