Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frequent Failures #15

Closed
gjsman opened this issue Sep 4, 2019 · 5 comments
Closed

Frequent Failures #15

gjsman opened this issue Sep 4, 2019 · 5 comments

Comments

@gjsman
Copy link

gjsman commented Sep 4, 2019

I am frequently having failures because of this:


E
===============================================================================
Error: test_vconn1(Vconn1):
  NameError: undefined local variable or method `log' for #<Vconn1:0x0000560d807d1980>
  Did you mean?  load
/root/kaltura-adobe-connect/adobe-connect-to-mkv-to-kaltura/ac_new.rb:109:in `test_vconn1'
     106:         return false
     107:       end
     108:     else
  => 109:       log.error('Failed to get duration from audio track or XML metadata :(')
     110:       return false
     111:     end
     112:
===============================================================================
E
===============================================================================

I don't know what else to say. Help.

@kaltura-hooks
Copy link

Hi @gjsman,

Thank for you reporting an issue and helping improve Kaltura!

To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):

  • Is the issue you're experiencing consistent and across platforms? or does it only happens on certain conditions?
    please provide as much details as possible.
  • Which Kaltura deployment you're using: Kaltura SaaS, or self-hosted?
    If self hosted, are you using the RPM or deb install?
  • Packages installed.
    When using RPM, paste the output for:
	# rpm -qa \"kaltura*\"
For deb based systems:
	# dpkg -l \"kaltura-*\"
  • If running a self hosted ENV - provide the MySQL server version used
  • If running a self hosted ENV - is this a single all in 1 server or a cluster?
  • If running a self hosted ENV, while making the problematic request, run:
	# tail -f /opt/kaltura/log/*.log /opt/kaltura/log/batch/*.log | grep -A 1 -B 1 --color \"ERR:\|PHP\|trace\|CRIT\|\[error\]\"

and paste the output.

  • When relevant, provide any screenshots or screen recordings showing the issue you're experiencing.

For general troubleshooting see:
https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.13.0/doc/kaltura-packages-faq.md#troubleshooting-help

If you only have a general question rather than a bug report, please close this issue and post at:
http://forum.kaltura.org

Thank you in advance,

@jessp01
Copy link
Contributor

jessp01 commented Sep 4, 2019

Hi @gjsman,

See https://github.com/kaltura/adobe-connect-to-mkv-to-kaltura/blob/master/ac_new.rb#L98
This will happen if the recording has no audio track at all. Is that the case?
If so, you'll need to revise the code to handle such recordings. At the moment, the code assumes that an audio track is present, as well as a video one.

@gjsman gjsman mentioned this issue Sep 5, 2019
@gjsman
Copy link
Author

gjsman commented Sep 5, 2019

I got a little further today... Apparently, if the Adobe Connect recording (for whatever reason) doesn't finish downloading or gets cancelled, the next time I run the command it will simply reuse the half-downloaded files, which predictably fails...

I am having issues other than this one soon. I will post the next time they happen (which shouldn't be too long).

@jessp01
Copy link
Contributor

jessp01 commented Sep 5, 2019

Okay, so can we close this one?

@gjsman
Copy link
Author

gjsman commented Sep 5, 2019

For now, yes. My bad.

@gjsman gjsman closed this as completed Sep 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants