Debugging

Sometimes Faktory will have problems, like any system. This page collects tips and tools for debugging Faktory.

Redis

When running Faktory starts Redis with a persistent data directory at /var/lib/faktory/db. Inside this directory you will find redis.db, the datafile with your persistent job data, and redis.sock which is the Unix socket by which you can connect to Redis.

• To monitor the raw Redis commands in real-time, use redis-cli -s /var/lib/faktory/db/redis.sock monitor.
• To capture current runtime info about Redis, use redis-cli -s /var/lib/faktory/db/redis.sock info.
• There are many other Redis datafile debugging and analysis tools out there.

You must treat the socket as read only. If you wish the edit the raw Redis datafile for some reason, stop Faktory, edit the data with redis-cli, and then start Faktory. This is brain surgery and is strongly discouraged.

TTIN

Sending the TTIN signal to Faktory will cause it to dump stack traces for all goroutines.

Web UI

The Web UI footer has a link to the /debug page which displays a good amount of diagnostic data which can be useful.