25. FAQ/Troubleshooting Matrix
This section provides a brief overview of some of the issues you may encounter when running an SF Archive system. It details actions which can be taken to rectify many common issues.
One of the main tools for analyzing issues is the queue window in NxUI, together with the logs and perhaps some database access. Any job which has failed can at any time be re-run either from the command line or from the Web UI. Any further execution will still log a separate run in the logs directory so the original information will not be lost.
The logs directory consists of <year>/<month>/NxCore_<jobID>_<processID>.log
- jobID - Is the queues job id number as seen on the UI.
- processID - Is the Linux process ID of the execution of NxCore. Since this number varies the log files for any particular job will stack and never overwrite.
An example of a set of log files for job 14227 is:
/usr/share/SFS/logs/2025/2/NxCore_14227_341762.log /usr/share/SFS/logs/2025/2/NxCore_14227_185910.log
Both of these logs contain output and trace information for the job 14227 and provide a history of the jobs progress. These entries show the job was run at least twice.
Do note of course that the job may have been run in another month in that year in which case that log will not be shown here but in the /2025/1/…. Directory entries.
If a job has failed, these logs can be invaluable for tracing issues.