question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No configuration setting found for key 'randomize-control-muc-nickname'

See original GitHub issue

Description

The current stable jibri (8.0-113-g56bf495-1) doesn’t work without randomize-control-muc-nickname in jibri.conf and there is no info in example_xmpp_envs.conf related with this param

Current behavior

jibri service throws the following error message in systemd status and doesn’t work

Exception in thread "main" org.jitsi.metaconfig.ConfigException$UnableToRetrieve$NotFound: No suppliers found a value:                                                  
  org.jitsi.metaconfig.ConfigException$UnableToRetrieve$NotFound: Considering empty XMPP envs list as not found                                                         
  org.jitsi.metaconfig.ConfigException$UnableToRetrieve$Error: /etc/jitsi/jibri/jibri.conf: 41: No configuration setting found for key 'randomize-control-muc-nickname'                        
        at org.jitsi.metaconfig.supplier.FallbackSupplier.doGet(FallbackSupplier.kt:57)                                                                                 
        at org.jitsi.metaconfig.supplier.ConfigValueSupplier$value$2.invoke(ConfigValueSupplier.kt:30)                                                                  
        at org.jitsi.metaconfig.supplier.ConfigValueSupplier$value$2.invoke(ConfigValueSupplier.kt:29)                                                                  
        at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)                                                                                                          
        at org.jitsi.metaconfig.supplier.ConfigValueSupplier.getValue(ConfigValueSupplier.kt)                                                                           
        at org.jitsi.metaconfig.supplier.ConfigValueSupplier.get(ConfigValueSupplier.kt:32)                                                                             
        at org.jitsi.jibri.MainKt.main(Main.kt:141)

Expected Behavior

randomize-control-muc-nickname in example config or running as expected without this param

Steps to reproduce

Use the current stable without randomize-control-muc-nickname in jibri.conf

Environment details

Debian 11 Bullseye openjdk-11-jre-headless 11.0.13+8-1~deb11u1 jibri 8.0-113-g56bf495-1

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
damenchocommented, Dec 7, 2021

@emrahcom I just pushed the next version 8.0-114 to stable, I had forgotten about this … sorry. Should be fine now.

0reactions
emrahcomcommented, Dec 9, 2021

It works for me with this jibri.conf

Read more comments on GitHub >

github_iconTop Results From Across the Web

No configuration setting found for key typesafe config
The error message is telling you that whatever configuration got read, it didn't include a top level setting named add .
Read more >
Struggling with "No configuration setting found for key 'akka'"
I am able to run the tests successfully in my IntelliJ IDEA. However, when I run `sbt test` the test is failing with...
Read more >
com.typesafe.config.ConfigException$Missing: system ...
ConfigException$Missing: system properties : No configuration setting found for key 'akka' at com.typesafe.config.impl.SimpleConfig.
Read more >
No configuration setting found for key 'kafka.connections' #19
I get a 500 error when I visit localhost:8080. Server Error message: No configuration setting found for key 'kafka.connections' status: 500.
Read more >
Jibri service fails - Install & Config - Jitsi Community Forum
loadConfigFromFile() An unrecognized config parameter was found: ... 78: No configuration setting found for key 'signing-key-path'
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found