Hi:

I have one user who’s jobs won’t execute on my local instance.

The user was mysteriously listed as inactive. I reactivated and restored the handlers, still jobs are not executing. The user has plenty of quota (82% used)

Anybody have an idea about what might be wrong with this user?

I have impersonated the user, jobs can be added

galaxy.util.object_wrapper WARNING 2016-11-30 00:40:08,118 Unable to create dynamic subclass for <type 'instance'>, None: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases galaxy.tools.actions INFO 2016-11-30 00:40:08,271 Handled output (153.865 ms) galaxy.tools.actions INFO 2016-11-30 00:40:08,330 Verified access to datasets (5.648 ms) galaxy.tools.execute DEBUG 2016-11-30 00:40:08,490 Tool [toolshed.g2.bx.psu.edu/repos/jjohnson/fastqc/FastQC/1.0.0http://toolshed.g2.bx.psu.edu/repos/jjohnson/fastqc/FastQC/1.0.0] created job [537201] (384.040 ms) galaxy.tools.execute DEBUG 2016-11-30 00:40:08,498 Executed all jobs for tool request: (413.473 ms) 10.254.254.95 - - [30/Nov/2016:00:40:07 -0400] "POST /api/tools HTTP/1.0" 200 - "http://galaxy.neb.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36 OPR/41.0.2353.69”

but they never get scheduled or run.

Nothing else in the logs after submitting the job.

They just remain in this state: This is a new dataset and not all of its data are available yet

Any ideas? Brad