failed to fetch `/usr/local/apisix/conf/apisix.yaml`: No such file or directory, context: ngx.timer

[kayx23]

failed to fetch `/usr/local/apisix/conf/apisix.yaml`: No such file or directory, context: ngx.timer

[kayx23]

The repetitive logging would stop when a working configuration is present in apisix.yaml it seems.

For example, it won't stop logging warning and errors with just the creation of the file:

sudo docker exec apache-apisix bash -c "echo '#END' > /usr/local/apisix/conf/apisix.yaml"

It would stop when a working config is present:

docker exec -i apache-apisix sh -c 'cat > /usr/local/apisix/conf/apisix.yaml <<_EOC_
routes:
  -
    id: httpbin
    uri: /*
    upstream:
      nodes:
        "httpbin.org": 1
      type: roundrobin
    plugin_config_id: 1

plugin_configs:
  -
    id: 1
    plugins:
      response-rewrite:
        body: "Hello APISIX\n"
    desc: "response-rewrite"
#END
_EOC_'

APISIX is usable, however, just with a very polluted log.

Please evaluate if this is something to fix for. If this is not a concern, the issue can be closed. It doesn't block me for anything personally.

[kayx23]

Another way is to mount the file apisix.yaml at container start up, with a working config (e.g. a route) inside the file.

If you mount an empty file, you could get the following:

/usr/local/openresty//luajit/bin/luajit ./apisix/cli/apisix.lua init
/usr/local/openresty//luajit/bin/luajit: /usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:756: bad argument #1 to 'sfind' (string expected, got nil)
stack traceback:
        [C]: in function 'sfind'
        /usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:756: in function 'parsedocuments'
        /usr/local/apisix/deps/share/lua/5.1/tinyyaml.lua:818: in function 'parse'
        /usr/local/apisix/apisix/cli/file.lua:321: in function 'read_yaml_conf'
        /usr/local/apisix/apisix/cli/ops.lua:174: in function </usr/local/apisix/apisix/cli/ops.lua:157>
        /usr/local/apisix/apisix/cli/ops.lua:976: in function 'execute'
        ./apisix/cli/apisix.lua:40: in main chunk
        [C]: at 0x56493d0c23d0

[Revolyssup]

@kayx23 These are just yaml parsing warnings present that go away once a valid configuration is given. I think since these are warning logs and not error logs, it's fine to have them.