Troubleshooting

Hashview fails to start

Many distros will automatically start redis after install. Make sure you don't already have a instance running on port 6379. You can either stop redis via OS (and don't forget to disable it on boot), or you can let the OS handle redis and remove the line in Profile that starts it.

My jobs are not running

Jobs start and stop reliably, but there can be a time when some subsystem gets out of sync/control and it can cause odd behavior. This has been known to happen with excessive starting and stopping of foreman. These following steps usually will get you back to a working state.

Is hashcat-worker outputting its stdout via foreman?

If not, stop hashview (ctrl+c in foreman window). Once foreman has stopped, make sure redis is not listening still (netstat -tnap). If you have an instance of redis running outside of foremans control, you will most likely have issues with the service worker (resque) which handles the hashcat worker. Also verify you don't have any stale resque processes (ps -ef | grep -i resque). If you do, kill them and restart hashview.

If the above method didn’t help:

start resque-web in the hashview root (under your rvm environment). This will stand up a web app on port :5678. You can see the resque queue and determine if you are having any failed jobs. If so, first try to purge all the failed jobs so they are not retried, and restart hashview. If you continue to get errors do the following:

1. start hashview
2. in another window, under the hashview root in your rvm environment, run redis-cli.
3. while in the redis command line, issues a flushall and fluashdb command.
4. in resque web app, delete the hashcat queue
5. restart hashview