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

Recording fails #544

Open
felix-afd opened this issue Jul 8, 2024 · 4 comments
Open

Recording fails #544

felix-afd opened this issue Jul 8, 2024 · 4 comments

Comments

@felix-afd
Copy link

felix-afd commented Jul 8, 2024

# dpkg -l | grep jitsi
ii  jitsi-meet-prosody                   1.0.7790-1                        all          Prosody configuration for Jitsi Meet
ii  jitsi-meet-tokens                    1.0.7790-1                        all          Prosody token authentication plugin for Jitsi Meet
ii  jitsi-meet-turnserver                1.0.7790-1                        all          Configures coturn to be used with Jitsi Meet
ii  jitsi-meet-web                       1.0.7790-1                        all          WebRTC JavaScript video conferences
ii  jitsi-meet-web-config                1.0.7790-1                        all          Configuration for web serving of Jitsi Meet
ii  lua-basexx                           0.4.1-jitsi1                      all          baseXX encoding/decoding library for Lua
ii  lua-cjson:amd64                      2.1.0.10-jitsi1                   amd64        JSON parser/encoder for Lua
dpkg -l | grep ji
ii  jibri                                 8.0-169-g1258814-1                    all          Jibri
  • Above is version i am running for both jitsi and jibri
  • Successfully completed upgrade to these versions
  • Calls are working perfectly as expected, however RECORDING is failing with below error messages from

=== /var/log/jitsi/jibri/log.0.txt === JIBRI

2024-07-08 12:14:32.988 SEVERE: [217] CallPage.visit#65: Timed out waiting for call page to load

2024-07-08 12:14:32.988 INFO: [217] [session_id=eepocfvqboneopkv] JibriSelenium.onSeleniumStateChange#218: Transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2024-07-08 12:14:32.989 INFO: [217] [session_id=eepocfvqboneopkv] StatefulJibriService.onServiceStateChange#39: File recording service transitioning from state Starting up to Error: FailedToJoinCall SESSION Failed to join the call
2024-07-08 12:14:32.989 INFO: [217] XmppApi$createServiceStatusHandler$1.invoke#311: Current service had an error Error: FailedToJoinCall SESSION Failed tojoin the call, sending error iq <iq xmlns='jabber:client' to='[email protected]/focus' id='4D7GF-635' type='set'><jibri xmlns='http://jitsi.org/protocol/jibri' status='off' failure_reason='error' should_retry='true'/></iq>

=== /var/log/jitsi/jicofo.log === JITSI

Jicofo 2024-07-08 12:18:23.657 SEVERE: [21] HealthChecker.run#181: Health check failed in PT0.0069S: Result(success=false, hardFailure=false, responseCode=null, sticky=false, message=XMPP ping failed: No suppliers found a value:
  org.jitsi.metaconfig.ConfigException$UnableToRetrieve$NotFound: Key 'org.jitsi.jicofo.XMPP_DOMAIN' not found in source 'sip communicator props'
  org.jitsi.metaconfig.ConfigException$UnableToRetrieve$NotFound: Key 'jicofo.xmpp.client.xmpp-domain' not found in source 'typesafe config (reloaded 1 times)')
Jicofo 2024-07-08 12:18:33.657 SEVERE: [21] HealthChecker.run#181: Health check failed in PT0.006562S: Result(success=false, hardFailure=false, responseCode=null, sticky=false, message=XMPP ping failed: No suppliers found a value:
  org.jitsi.metaconfig.ConfigException$UnableToRetrieve$NotFound: Key 'org.jitsi.jicofo.XMPP_DOMAIN' not found in source 'sip communicator props'
ruby 

Question

  • Any idea why recording based on above errors ?
  • Is there any known bug to recording features for above versions ?
@felix-afd felix-afd changed the title ll Recording fails Jul 8, 2024
@damencho damencho closed this as completed Jul 8, 2024
@felix-afd
Copy link
Author

@damencho any reason this was marked as completed ?

@damencho
Copy link
Member

damencho commented Jul 8, 2024

When I closed this issue was empty with no information.

@damencho damencho reopened this Jul 8, 2024
@damencho
Copy link
Member

damencho commented Jul 8, 2024

Include the complete jibri log, with all the failures.

Please, when you have questions or problems use the community forum before opening new issues, thank you. You have better chances of quicker replies there, we prefer discussing there as most of the time these are configuration issues and not bugs in the software.

@felix-afd
Copy link
Author

@damencho thanks for clarifications,
in the meantime, i have created a thread on the community page here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants