Janus does not load janus.jcfg

General
1

It seems like I’m unable to load any config files.
How to check what config file Janus have loaded?
I’ve renamed my folder from /opt/janus/etc/janus to /opt/janus/etc/1janus and Janus starts without any problems. There are no janus.jcfg files inside docker container.

When I start my server with
/opt/janus/bin/janus --stun-server=stun.l.google.com:19302
the starting log says that

STUN server to use: stun.l.google.com:19302
  >> 173.194.76.127:19302 (IPv4)
Testing STUN server: message is of 20 bytes
  >> Our public address is 78.140.242.29

But when I start it just with
/opt/janus/bin/janus
and having my janus.jcfg located at
/opt/janus/etc/janus
with the content

nat: {
	stun_server = "stun.l.google.com"
	stun_port = 19302
	nice_debug = true

It does not write any info on testing STUN.

The main question is how to figure out if any jcfg files are being loaded?

Thanks!

2

You can’t just rename the config folder: obvjoisly Janus won’t find them anymore if you do that.

3

If you start Janus with debug level 5 it will print where it’s getting the config files from on the console.

1 Like
4

Wow, thanks!

So, this log level 5 thing says that

Configuration file: /opt/janus/etc/janus/janus.transport.http.jcfg
HTTP transport timer started
[janus.transport.http.jcfg]
    general: {
        json: indented
        base_path: /janus
        http: true
        port: 8088
        https: false
    }
    admin: {
        admin_base_path: /admin
        admin_http: false
        admin_port: 7088
        admin_https: false
    }

although
cat /opt/janus/etc/janus/janus.transport.http.jcfg

says:

admin: {
        admin_base_path = "/admin"                      
        admin_http = true                                       
        admin_port = 7088

What is going on?

5

I think that jcfg are cached somehow

6

There’s no such thing as caching in Janus. Configuration files are read from scratch every time you restart Janus.

7

restarting the container solved the issue