[jitsi-dev] post process error


#1

Hi,

I'm having trouble with jipopro, each time the post processing is being
called, the following error is shown and the java process exits:

Exception in thread "main" java.util.NoSuchElementException
    at java.util.Scanner.throwFor(Scanner.java:862)
    at java.util.Scanner.next(Scanner.java:1371)
    at
    org.jitsi.recording.postprocessing.PostProcessing.main(PostProcessing.java:150)

I'm sure it worked before and the only system updates I saw were jitsi
ones (jipopro was not changed, jirecon was not either).

I'm seeing this on Debian/Ubuntu (it worked before there) and now on
CentOS.

OpenJDK is 1.7.0_91
Ant is 1.9.2

The metadata.json file in the recordings folder is empty.

If you have an idea what has changed it would be great.
Thanks!

···

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#2

The empty metadata.json file is the problem -- the line 150 in
PostProcessing.java deals with the json parsing and also when I made
up a metadata.json content with the corresponding media start and sto
timestamps it was all ok.

So now the problem seems to be in jirecon, because it doesn't populate
the metadata file. It creates it, but it's empty.

jirecon is latest git version; I don't see anything strange in its
output in the log.

···

On Wed, 28 Oct 2015 18:05:52 +0200 Yasen Pramatarov wrote:

Hi,

I'm having trouble with jipopro, each time the post processing is
being called, the following error is shown and the java process exits:

Exception in thread "main" java.util.NoSuchElementException
   at java.util.Scanner.throwFor(Scanner.java:862)
   at java.util.Scanner.next(Scanner.java:1371)
   at
   org.jitsi.recording.postprocessing.PostProcessing.main(PostProcessing.java:150)

I'm sure it worked before and the only system updates I saw were jitsi
ones (jipopro was not changed, jirecon was not either).

I'm seeing this on Debian/Ubuntu (it worked before there) and now on
CentOS.

OpenJDK is 1.7.0_91
Ant is 1.9.2

The metadata.json file in the recordings folder is empty.

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services


#3

Hi,

I'm having trouble with jipopro, each time the post processing is
being called, the following error is shown and the java process exits:

Exception in thread "main" java.util.NoSuchElementException
    at java.util.Scanner.throwFor(Scanner.java:862)
    at java.util.Scanner.next(Scanner.java:1371)
    at
    org.jitsi.recording.postprocessing.PostProcessing.main(PostProcessing.java:150)

I'm sure it worked before and the only system updates I saw were jitsi
ones (jipopro was not changed, jirecon was not either).

I'm seeing this on Debian/Ubuntu (it worked before there) and now on
CentOS.

OpenJDK is 1.7.0_91
Ant is 1.9.2

The metadata.json file in the recordings folder is empty.

  The empty metadata.json file is the problem

Exactly. The metadata file is an essential part of the recording, and post-processing will not work without it.

-- the line 150 in
  PostProcessing.java deals with the json parsing and also when I made
  up a metadata.json content with the corresponding media start and sto
  timestamps it was all ok.

  So now the problem seems to be in jirecon, because it doesn't populate
  the metadata file. It creates it, but it's empty.

  jirecon is latest git version; I don't see anything strange in its
  output in the log.

This is weird, I don't see how changes to the other component would cause this (without braking the actual media files). Can you check the file during the recording (it gets re-writen multiple times)? Can you post (or send me personally) the jirecon logs? Do you reproduce this every time?

Regards,
Boris

···

On 28/10/15 15:57, Yasen Pramatarov wrote:

On Wed, 28 Oct 2015 18:05:52 +0200 Yasen Pramatarov wrote:


#4

The metadata file was not being populated, because Jitsi Meet stopped
using MUC presence to advertise the SSRCs. It uses jingle now and all
other components work ok with that, but Jirecon still uses the old way.

In order to fix this and to add a backward compatibility with Jirecon,
Boris committed changes to the Jitsi Meet master.

With this latest commit[0] and with an option
"advertiseSSRCsInPresence: true" in config.js you can have the
metadata.json files working again.

I checked this on two instances already and it does the job. Kudos to
Boris for pinpointing the problem and for the quick fix!

[0]https://github.com/jitsi/jitsi-meet/commit/932af962b2bd38eaf9bb58a54cf9848456c0c64d

···

On Wed, 28 Oct 2015 16:42:08 -0500 Boris Grozev wrote:

This is weird, I don't see how changes to the other component would
cause this (without braking the actual media files). Can you check the
file during the recording (it gets re-writen multiple times)? Can you
post (or send me personally) the jirecon logs? Do you reproduce this
every time?

--

Yasen Pramatarov
Lindeas Ltd. https://lindeas.com
'working on GNU/Linux ideas'
Professional Jitsi Meet services