Retry-ingest settings?

3 views
Skip to first unread message

Hans Erasmus

unread,
Jul 27, 2018, 1:50:13 AM7/27/18
to comm...@galicaster.org
Hey all

So as a side issue during my attempt to get a workaround up and running for the 1 sec recording issue, I came across a video that has failed to ingest. The log shows the line 
galicaster 2018-07-27 07:42:44,819 DEBUG plugins/retryingest reingest checking: 1537229822595490816 status: Failed

but the video is not re-ingested automatically. Am I missing something? Is the plugin only there to check if an ingest has failed, or is it actually there to try and reingest the mp?

As per the docs https://github.com/teltek/Galicaster-doc/blob/master/GalicasterConfiguration/Plugins.md#retry-failed-ingest it seems it should retry the ingest. I have double checked my OC env and the MP is definitely not published (in fact, it is missing atm due to it recording successfully but not ingested).

My settings:

retryingest = True

[retryingest]
check_after = 300
check_published = True
nightly = False


My log:

galicaster 2018-07-27 07:48:44,840 INFO opencast/service Set status idle to server
galicaster 2018-07-27 07:48:44,840 INFO opencast/client Sending state idle
galicaster 2018-07-27 07:48:54,820 DEBUG plugins/retryingest reingest checking: 4530258543024413696 status: Done
galicaster 2018-07-27 07:48:54,820 DEBUG plugins/retryingest reingest checking: 6514337800272611328 status: Done
galicaster 2018-07-27 07:48:54,820 DEBUG plugins/retryingest reingest checking: 7372067781054036992 status: Done
galicaster 2018-07-27 07:48:54,820 DEBUG plugins/retryingest reingest checking: 1537229822595490816 status: Failed
galicaster 2018-07-27 07:48:54,820 INFO opencast/client Looking up Opencast endpoint for org.opencastproject.search
galicaster 2018-07-27 07:48:54,862 DEBUG scheduler/heartbeat galicaster-notify-short in 10
galicaster 2018-07-27 07:48:54,862 INFO opencast/service Set status idle to server
galicaster 2018-07-27 07:48:54,862 DEBUG scheduler/heartbeat galicaster-notify-long in 60
galicaster 2018-07-27 07:48:54,862 INFO opencast/client Sending state idle
galicaster 2018-07-27 07:48:54,873 INFO opencast/service Process ical
galicaster 2018-07-27 07:48:54,883 INFO opencast/client iCal Not modified
galicaster 2018-07-27 07:48:54,884 INFO opencast/service Updating series from server
galicaster 2018-07-27 07:48:55,256 INFO opencast/service Setting CA configuration to server
galicaster 2018-07-27 07:49:04,819 DEBUG plugins/retryingest reingest checking: 4530258543024413696 status: Done
galicaster 2018-07-27 07:49:04,819 DEBUG plugins/retryingest reingest checking: 6514337800272611328 status: Done
galicaster 2018-07-27 07:49:04,819 DEBUG plugins/retryingest reingest checking: 7372067781054036992 status: Done
galicaster 2018-07-27 07:49:04,819 DEBUG plugins/retryingest reingest checking: 1537229822595490816 status: Failed
galicaster 2018-07-27 07:49:04,819 INFO opencast/client Looking up Opencast endpoint for org.opencastproject.search
galicaster 2018-07-27 07:49:04,884 DEBUG scheduler/heartbeat galicaster-notify-short in 10
galicaster 2018-07-27 07:49:04,884 INFO opencast/service Set status idle to server
galicaster 2018-07-27 07:49:04,885 INFO opencast/client Sending state idle


The video was recorded yesterday, so in about 8 hours it did not try to reingest once.

Did I misconfigure something?

Regards

HE

Vrywaringsklousule / Disclaimer: http://www.nwu.ac.za/it/gov-man/disclaimer.html


Alfonso Rodriguez

unread,
Jul 27, 2018, 4:50:18 AM7/27/18
to comm...@galicaster.org
Hi Hans,

The plugin should try to reingest once it detects a recording that failed to ingest. From the logs, it looks like it's not doing anything else because of this line:
(galciaster/plugins/retryingest.py:79)
if not (mp.status == mediapackage.SCHEDULED or mp.status == mediapackage.RECORDING):

Could you check the "status" value on the galicaster.json/galicaster.xml file of the mediapackage?

Best Regards,


Alfonso Rodríguez Pereira
TELTEK Video Research

http://teltek.es/


La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.

The 
information contained in this message and/or attached file(s) is confidential/privileged and is intended to be read only by the person(s) to whom it is directed. If you are reading this message and you are not the indicated recipient, or the employee or agent responsible for delivering the message to the addressee, or you have received this communication by mistake, please be aware that any dissemination, distribution or reproduction of this communication is strictly prohibited and may be illegal. Please notify us immediately and return the original message to the aforementioned address. Thank you.

--
You received this message because you are subscribed to the Google Groups "Galicaster-Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to community+unsubscribe@galicaster.org.
To post to this group, send email to comm...@galicaster.org.

Hans Erasmus

unread,
Jul 27, 2018, 5:00:54 AM7/27/18
to comm...@galicaster.org
Hi Alfonso

The galicaster.xml file for that MP shows:

<?xml version="1.0" encoding="utf-8"?>
<galicaster>
   <status>4</status>
   <operations>
      <operation key="ingest">
         <status>5</status>
      </operation>
   </operations>
   <properties>
      <property name="origin">CAP-D1-303</property>
      <property name="notes"></property>
   </properties>
</galicaster>

The problem was that GC was restart midway through the ingest, and this is something that might happen in the field due to power failures or network interrupts etc. So imho this is not a "special" case at all.

Regards

HE 



Vrywaringsklousule / Disclaimer: http://www.nwu.ac.za/it/gov-man/disclaimer.html


>>> Alfonso Rodriguez <arodr...@teltek.es> 07/27/18 10:50 AM >>>
To unsubscribe from this group and stop receiving emails from it, send an email to community+...@galicaster.org.

To post to this group, send email to comm...@galicaster.org.

--
You received this message because you are subscribed to the Google Groups "Galicaster-Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to community+...@galicaster.org.

Andrew Wilson

unread,
Jul 27, 2018, 5:08:38 AM7/27/18
to comm...@galicaster.org
i think somthing different probably

from your logs, you see retry ingest looking up the search endpoint to see if its been published
i dont think its geting anything back from that
'search/episode.json'

for retry ingest config. have check_published = False. it wont check opencast then and will just use galicasters status as the trigger to retry

-andy

Andrew Wilson
Applications Analyst | Media Technologies Team | IT Services
IT Services Office 1, Kilburn Building
Tel: +44 (0) 161 27 51154 | email: andrew....@manchester.ac.uk

From: Hans Erasmus [Hans.E...@nwu.ac.za]
Sent: 27 July 2018 10:00
To: comm...@galicaster.org
Subject: Re: [Galicaster] Retry-ingest settings?

La informacioěn contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y estaě destinada a ser leiěda soělo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario senŢalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicacioěn por error, le informamos que estaě totalmente prohibida, y puede ser ilegal, cualquier divulgacioěn, distribucioěn o reproduccioěn de esta comunicacioěn, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la direccioěn arriba mencionada. Gracias.

The 
information contained in this message and/or attached file(s) is confidential/privileged and is intended to be read only by the person(s) to whom it is directed. If you are reading this message and you are not the indicated recipient, or the employee or agent responsible for delivering the message to the addressee, or you have received this communication by mistake, please be aware that any dissemination, distribution or reproduction of this communication is strictly prohibited and may be illegal. Please notify us immediately and return the original message to the aforementioned address. Thank you.

Hans Erasmus

unread,
Jul 27, 2018, 5:22:00 AM7/27/18
to comm...@galicaster.org
Mr Wilson to the rescue

Thanks Andy! Probably something broken in OC deployment then.

Thanks a stack!

HE
 



Vrywaringsklousule / Disclaimer: http://www.nwu.ac.za/it/gov-man/disclaimer.html


>>> Andrew Wilson <andrew....@manchester.ac.uk> 07/27/18 11:08 AM >>>

Andrew Wilson

unread,
Jul 27, 2018, 5:59:24 AM7/27/18
to comm...@galicaster.org
i think you may have stumbled on a bit of a bug *maybe* i'll have a look into it
at UoM we dont use check_published as the id's on the mediapackage in galicaster didnt used to correspond the the resulting published id on opencast. this may have changed since. but really we only cared that it had sucessfully ingested 


-andy

Andrew Wilson
Applications Analyst | Media Technologies Team | IT Services
IT Services Office 1, Kilburn Building
Tel: +44 (0) 161 27 51154 | email: andrew....@manchester.ac.uk

From: Hans Erasmus [Hans.E...@nwu.ac.za]
Sent: 27 July 2018 10:21
To: comm...@galicaster.org
Subject: Re: RE: [Galicaster] Retry-ingest settings?

Hans Erasmus

unread,
Jul 27, 2018, 6:21:25 AM7/27/18
to comm...@galicaster.org
OK. Thanks anycase for your help, now I can sleep a bit better. 

All the best man!

Cheers!


Vrywaringsklousule / Disclaimer: http://www.nwu.ac.za/it/gov-man/disclaimer.html


>>> Andrew Wilson <andrew....@manchester.ac.uk> 07/27/18 11:59 AM >>>

Andrew Wilson

unread,
Jul 27, 2018, 6:22:39 AM7/27/18
to comm...@galicaster.org
try the below rest endpoint on your opencast

http://<insert your server here>/search/episode.json?id=1537229822595490816

also check where the search service is:
http://<insert your server here>/available.json?serviceType=org.opencastproject.search

these are used by GC retryingest to figure the check_published out

Andrew Wilson
Applications Analyst | Media Technologies Team | IT Services
IT Services Office 1, Kilburn Building
Tel: +44 (0) 161 27 51154 | email: andrew....@manchester.ac.uk

From: Hans Erasmus [Hans.E...@nwu.ac.za]
Sent: 27 July 2018 06:49
To: comm...@galicaster.org
Subject: [Galicaster] Retry-ingest settings?

Alfonso Rodriguez

unread,
Jul 27, 2018, 6:42:01 AM7/27/18
to comm...@galicaster.org
Oh!

Thanks, Andrew, I can see what is happening now. If you have check_published to True and the endpoint does not return anything, it should treat it as if it's not published and reingest, but that is currently failing.


Alfonso Rodríguez Pereira
TELTEK Video Research

http://teltek.es/


La información contenida en este mensaje y/o archivo(s) adjunto(s) es confidencial/privilegiada y está destinada a ser leída sólo por la(s) persona(s) a la(s) que va dirigida. Si usted lee este mensaje y no es el destinatario señalado, el empleado o el agente responsable de entregar el mensaje al destinatario, o ha recibido esta comunicación por error, le informamos que está totalmente prohibida, y puede ser ilegal, cualquier divulgación, distribución o reproducción de esta comunicación, y le rogamos que nos lo notifique inmediatamente y nos devuelva el mensaje original a la dirección arriba mencionada. Gracias.

The 
information contained in this message and/or attached file(s) is confidential/privileged and is intended to be read only by the person(s) to whom it is directed. If you are reading this message and you are not the indicated recipient, or the employee or agent responsible for delivering the message to the addressee, or you have received this communication by mistake, please be aware that any dissemination, distribution or reproduction of this communication is strictly prohibited and may be illegal. Please notify us immediately and return the original message to the aforementioned address. Thank you.

To unsubscribe from this group and stop receiving emails from it, send an email to community+unsubscribe@galicaster.org.

To post to this group, send email to comm...@galicaster.org.

--
You received this message because you are subscribed to the Google Groups "Galicaster-Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to community+unsubscribe@galicaster.org.

Hans Erasmus

unread,
Jul 27, 2018, 6:54:06 AM7/27/18
to comm...@galicaster.org
Hi Andy, see inline answers.
 



Vrywaringsklousule / Disclaimer: http://www.nwu.ac.za/it/gov-man/disclaimer.html


>>> Andrew Wilson <andrew....@manchester.ac.uk> 07/27/18 12:22 PM >>>
try the below rest endpoint on your opencast

http://<insert your server here>/search/episode.json?id=1537229822595490816

Returns:

{"search-results":{"offset":"0","limit":"0","total":"0","searchTime":"4","query":"(id:1537229822595490816) AND oc_organization:mh_default_org AND (oc_acl_read:ROLE_ADMIN OR oc_acl_read:ROLE_ANONYMOUS OR oc_acl_read:ROLE_LOGACCESS OR oc_acl_read:ROLE_USER_NWU) AND -oc_mediatype:Series AND -oc_deleted:[* TO *]"}}

I Suspect it is because I removed the video after it was ingested (was a test vid). Will do that with one of the upcoming videos and see if there is any returned result.


also check where the search service is:
http://<insert your server here>/available.json?serviceType=org.opencastproject.search

Returns 404 Hmmm....
Reply all
Reply to author
Forward
0 new messages