Severe Issue with Scheduled Events

Steps to reproduce

  • Schedule an event (CA)

  • Wait

  • Processing Fails, several problems show up

1. Going to Job Details -> Workflow, no workflow shows up, but a workflow was processed (FFmpeg commands show up in the logs, ...) (See Screenshot)

2. There are errors in the log files

3. com.entwinemedia.fn.data.json.SimpleSerializer throws errors that are not in the logfile but show up in the interactive shell.

Please find attached a screenshot of the missing workflow in the ui, the shell output (logs + entwine-lib error).

I checked that the uploaded media is undamaged.

Activity

Show:
Former user
May 28, 2015, 2:25 PM

Is this a vote of not requiring a title for a Recording? The mediapackage will still fail during publish.

Lukas Rohner
May 28, 2015, 2:48 PM

The mediapackage always failed during publishing if no 'title' was available. I would only fix the null pointer here and then close it. I don't think we should add a new behavior to allow a non-existing title short before a release, I'm worry about a lot of impacts in lot of services.

Former user
May 28, 2015, 2:57 PM

Ok, so this ticket is the null pointer fix.

Lars Kiesow
May 29, 2015, 11:31 AM

Looking thrugh all of this, I think we can downrade this to a critical or even major issue instead of keeping it as blocker.

In the end, the cause why this issue showed up was that the dublincore xml for the episodes had changed and ot some additional parameters. Sure, it is kind of an API change but I do not think that it will hit most CAs. It was more due to my sloppy handling of the XML data. Although I would vote for a cleaner way to identify the metadata type in the new CA API.

Apart from that I think we found three smaller issues with this:

  • The ingest service accepts MPs without title. If we really require a title, we should already do that at this point.

  • The Admin UI dies with a null pointer exception when there is no title (fixed with Lukas' patch?)

  • Exceptions thrown by the entwinemedia lib are not logged.

How do we want to continue? Resolve this and create separate tickets for the issues? Or do we want to keep everyting in here?

Former user
June 1, 2015, 7:04 PM

Merged pull #523 commit d74deda

Assignee

Lukas Rohner

Reporter

Lars Kiesow

Severity

Non Functioning

Tags (folksonomy)

Components

Fix versions

Affects versions

Priority

Critical
Configure