Ok, I've verified that director is down, only storage and file daemons are running:
root 12915 1 0 Mar26 ? 00:00:00 bacula-fd -c /etc/bacula/bacula-fd.conf -u root -g root
bacula 26664 1 0 00:21 ? 00:00:00 bacula-sd -c /etc/bacula/bacula-sd.conf -u bacula -g disk
[root@ops:~] #bacula-dir -c /etc/bacula/bacula-dir.conf -d 200 -f
bacula-dir: dird.c:194-0 Debug level = 200
bacula-dir: runscript.c:284-0 runscript: debug
bacula-dir: runscript.c:285-0 --> RunScript
bacula-dir: runscript.c:287-0 --> Target=
bacula-dir: runscript.c:288-0 --> RunOnSuccess=1
bacula-dir: runscript.c:289-0 --> RunOnFailure=0
bacula-dir: runscript.c:290-0 --> FailJobOnError=1
bacula-dir: runscript.c:291-0 --> RunWhen=2
bacula-dir: runscript.c:284-0 runscript: debug
bacula-dir: runscript.c:285-0 --> RunScript
bacula-dir: runscript.c:286-0 --> Command=/etc/bacula/delete_catalog_backup
bacula-dir: runscript.c:287-0 --> Target=
bacula-dir: runscript.c:288-0 --> RunOnSuccess=1
bacula-dir: runscript.c:289-0 --> RunOnFailure=0
bacula-dir: runscript.c:290-0 --> FailJobOnError=1
bacula-dir: runscript.c:291-0 --> RunWhen=1
bacula-dir: jcr.c:128-0 read_last_jobs seek to 192
bacula-dir: jcr.c:135-0 Read num_items=10
bacula-dir: dir_plugins.c:148-0 Load dir plugins
bacula-dir: dir_plugins.c:150-0 No dir plugin dir!
bacula-dir: dird.c:972-0 Could not open Catalog "JokefireCatalog", database "bacula".
bacula-dir: dird.c:977-0 Query failed: SELECT VersionId FROM Version: ERR=no such table: Version
27-Mar 12:04 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf
It looks like it can't find a catalog by the name "JokefireCatalog". But it used to be there before some data got deleted.
So is this a physical file on the file system that it's not finding? Or is this an entry in the database that it's not finding? Any ideas how to correct this?