Ry4an Brase wrote:
I've created a new data library and have added two datasets using the admin interface to provide file paths to two large-ish files. In the admin interface they're still showing up as "Information: This job is queued" but no jobs show up in the admin job list, system load is zero, and I see no mention of the files in the log past the initial web-requests that kicked off the process.
I do have "track_jobs_in_database = True" and "enable_job_recovery = True", and I have previously killed off some data-set-addition jobs that seemed stalled and _were_ using CPU.
Where should I be looking for blocked data set import jobs? Do load jobs make it into the database too? Is there I table I can clear out to remove the import jobs that I interrupted by deleting their library previously? Is there anything I should be looking for in the logs Is there a handle I can jiggle?
Hi Ry4an, Could you find these jobs in the database and see what the value of their 'state' column is? If no job action was ever logged in the server log from which you can determine the job id, you can check job_to_output_library_dataset (unless you have added a lot of library datasets since these two became stuck). Thanks, --nate
I'm running rev 2c7acb546d6d.
Thanks!