-
Notifications
You must be signed in to change notification settings - Fork 0
Processes Tab
This menu allows you to look into the processes table of Omeka. It is useful for debugging background jobs started by plugins and detecting overloaded job queues.
You can click on any process ID to view more details, including the parameters being passed into it when the job was started.
Below is a number of common situations that indicate malfunctioning background jobs. For more detailed guidance, please ask for assistance on the Omeka forums.
-
Status remains at "in progress" for a long time: Note the PID of the process and run
ps -p <pid>
to determine whether the job is still running.- If an entry for the PID still exists: The job is still running. Allow it more time to finish. If it does not finish, there may be an infinite loop within the process, which can be interrupted by killing the process (exercise with caution).
- If the PID no longer exists: The job has stopped unexpectedly. Please check your logs for error or debug messages that may come from the source of the job. The
"className"
entry in the process' data often contains the prefix for a plugin or Omeka itself.
-
A process that you expect does not appear: The job dispatch queue may be busy or incorrectly configured. Run a Long-Running Job test and look for errors or timeouts. Also look for clumps of recent process entries that are "in progress".