New videos are not processed

32 views
Skip to first unread message

Hartmut Trüe

unread,
Oct 17, 2024, 6:59:15 AM10/17/24
to Opencast Users
Hello,

new videos are not processed on a test system (fortunately only there until now).

All newly uploaded videos remain in status "Pending" (instantiaded) and nothing more happens. It is the same for starting a workflow manually (e.g. "Republish metadata").

It happened after upgrade from 15.x to 16.5 and replacing elasticsearch with opensearch. Index is ok, switching back to elasticsearch doesn't help.

Does anyone have any ideas what I can do?

Regards,
Hartmut

Greg Logan

unread,
Oct 17, 2024, 8:13:34 PM10/17/24
to us...@opencast.org
Hi Hartmut,

Have you checked that at least one node is set up to be the job dispatcher?  Otherwise we're going to need to see logs, especially from the admin node.

Thanks,
G

To unsubscribe from this group and stop receiving emails from it, send an email to users+un...@opencast.org.

Hartmut Trüe

unread,
Oct 18, 2024, 7:10:14 AM10/18/24
to Opencast Users, Greg Logan
Hi Greg,

it is an AllInOne node. I added

log4j2.logger.jobdispatcher.name = org.opencastproject.serviceregistry.impl.JobDispatcher
log4j2.logger.jobdispatcher.level = DEBUG

to org.ops4j.pax.logging.cfg and got this:
...
2024-10-17T13:57:23,320 | DEBUG | (ScrLogManager$ScrLoggerFacade:195) - bundle opencast-serviceregistry:16.5.0 (171)[org.opencastproject.serviceregistry.impl.JobDispatcher(242)] : Locating method activate in class org.opencastproject.serviceregistry.impl.JobDispatcher
2024-10-17T13:57:23,320 | DEBUG | (ScrLogManager$ScrLoggerFacade:195) - bundle opencast-serviceregistry:16.5.0 (171)[org.opencastproject.serviceregistry.impl.JobDispatcher(242)] : Found activate method: public void org.opencastproject.serviceregistry.impl.JobDispatcher.activate(org.osgi.service.component.ComponentContext) throws org.osgi.service.cm.ConfigurationException
2024-10-17T13:57:23,320 | DEBUG | (ScrLogManager$ScrLoggerFacade:195) - bundle opencast-serviceregistry:16.5.0 (171)[org.opencastproject.serviceregistry.impl.JobDispatcher(242)] : invoking activate: activate: parameters [org.apache.felix.scr.impl.manager.ComponentContextImpl]
2024-10-17T13:57:23,320 | INFO  | (JobDispatcher:182) - Activate job dispatcher
2024-10-17T13:57:23,321 | INFO  | (JobDispatcher:186) - Activated
2024-10-17T13:57:23,321 | INFO  | (JobDispatcher:205) - Updating job dispatcher properties
2024-10-17T13:57:23,321 | INFO  | (JobDispatcher:239) - Job dispatching is disabled
2024-10-17T13:57:23,321 | DEBUG | (ScrLogManager$ScrLoggerFacade:195) - bundle opencast-serviceregistry:16.5.0 (171)[org.opencastproject.serviceregistry.impl.JobDispatcher(242)] : invoked activate: activate
2024-10-17T13:57:23,321 | DEBUG | (ScrLogManager$ScrLoggerFacade:195) - bundle opencast-serviceregistry:16.5.0 (171)[org.opencastproject.serviceregistry.impl.JobDispatcher(242)] : Set implementation object for component
2024-10-17T13:57:23,321 | DEBUG | (ScrLogManager$ScrLoggerFacade:195) - bundle opencast-serviceregistry:16.5.0 (171)[org.opencastproject.serviceregistry.impl.JobDispatcher(242)] : Changed state from satisfied to active
2024-10-17T13:57:23,321 | DEBUG | (ScrLogManager$ScrLoggerFacade:195) - bundle opencast-serviceregistry:16.5.0 (171)[org.opencastproject.serviceregistry.impl.JobDispatcher(242)] : dm ServiceRegistry tracking 8 SingleStatic added [org.osgi.service.cm.ManagedService, org.opencastproject.serviceregistry.api.ServiceRegistry, org.opencastproject.serviceregistry.impl.ServiceRegistryJpaImpl] (exit)
...

Thanks,
Hartmut

Hartmut Trüe

unread,
Oct 22, 2024, 6:00:31 AM10/22/24
to Opencast Users, Hartmut Trüe, Greg Logan
... mysterious:

my implJobDispatcher.cfg was:

# Configuration for the job dispatcher

# The interval in seconds between two rounds of dispatching in the service registry. A minimum value of 1s is enforced
# due to performance reasons. Set to 0 to disable dispatching from this service registry.  Default for the job dispatch
# node is 2. Service registry dispatching is automatically set to 0 on everything but admin or allinone nodes and should
# usually not be activated on these nodes to avoid concurrency problems.
# Default: 0
#dispatch.interval=0

I removed the # and set it to 2

Now its working again. I expected it to be 2 if not set ...

Regards,
Hartmut
Reply all
Reply to author
Forward
0 new messages