I'm not sure exactly what the problem is and why a second instance is still running.
Anyways, to solve it you just need to stop the second instance (either via job control - or "task manager"-like - or by killing the process).
e.g. something like:
You could also just restart the system (if that is doable/possible on your system).
Of course if this happens very often you might need to check what exactly is causing this problem.
BTW: with --sessions you might be able to run multiple instances, but it's not a good idea to run multiple long/heavy cracking jobs simultaneously on the same system.
if the problem persist across reboots, it might be possible to just remove the .pid file (or download a fresh copy of hashcat and run that new/clean version instead).
Anyways, to solve it you just need to stop the second instance (either via job control - or "task manager"-like - or by killing the process).
e.g. something like:
Code:
pkill hashcatYou could also just restart the system (if that is doable/possible on your system).
Of course if this happens very often you might need to check what exactly is causing this problem.
BTW: with --sessions you might be able to run multiple instances, but it's not a good idea to run multiple long/heavy cracking jobs simultaneously on the same system.
if the problem persist across reboots, it might be possible to just remove the .pid file (or download a fresh copy of hashcat and run that new/clean version instead).