Config file must be .edn or .yaml when running standalone jar?

[rlperez]

Hi there. I'm currently working on a fresh project and after a good bit of deliberation decided XTDB what I would like to use and with v2 being about ready it was my choice.

The goal use the standalone jar to stand up a node with my configuration file to define storage and log paths. However, I can't get this to run with any configuration, much less how I would like to configure it. I can compile things fine on openjdk 21 and clojure 1.12. The jar will run as long as I don't try and pass a configuration to it. I've tried it as both yaml and edn. Tried it with more and with less. It always says the configuration is invalid.

For instance this fails

---

server:
  port: 5432

log: !Local
  path: <redacted>/data/xtdb/log

storage: !Local
  path: <redacted>/data/xtdb/storag

This also fails

{:server {:port 5432}}

And this one too

server:
  port: 5432

It's always this error...the stacktrace is there after adding a logback but it still fails validation without adding the logback config.

Starting XTDB 2.x ...
Failed to validate "-f <config path>/xtdb.config.<yaml|yml|edn>": Config file must be .edn or .yaml
23:14:48 | DEBUG java.lang.Runtime | Runtime.exit() called with status: 2
java.lang.Throwable: Runtime.exit(2)
        at java.base/java.lang.Shutdown.logRuntimeExit(Shutdown.java:179)
        at java.base/java.lang.Shutdown.exit(Shutdown.java:160)
        at java.base/java.lang.Runtime.exit(Runtime.java:188)
        at java.base/java.lang.System.exit(System.java:1920)
        at xtdb.cli$start_node_from_command_line$fn__27867.invoke(cli.clj:114)
        at xtdb.cli$start_node_from_command_line.invokeStatic(cli.clj:111)
        at xtdb.cli$start_node_from_command_line.invoke(cli.clj:103)
        at clojure.lang.Var.invoke(Var.java:386)
        at xtdb.main$_main.invokeStatic(main.clj:17)
        at xtdb.main$_main.doInvoke(main.clj:5)
        at clojure.lang.RestFn.applyTo(RestFn.java:140)
        at clojure.lang.Var.applyTo(Var.java:707)
        at clojure.core$apply.invokeStatic(core.clj:667)
        at clojure.main$main_opt.invokeStatic(main.clj:515)
        at clojure.main$main_opt.invoke(main.clj:511)
        at clojure.main$main.invokeStatic(main.clj:665)
        at clojure.main$main.doInvoke(main.clj:617)
        at clojure.lang.RestFn.applyTo(RestFn.java:140)
        at clojure.lang.Var.applyTo(Var.java:707)
        at clojure.main.main(main.java:40)

This is the command I'm running at the moment...which always exits with code 2.

❯ java $JAVA_OPTS -Dclojure.main.report=stderr --add-opens=java.base/java.nio=ALL-UNNAMED -Dio.netty.tryReflectionSetAccessible=true -cp xtdb-standalone.jar clojure.main -m xtdb.main -f <config path>

Is there anything obvious I am doing wrong here? Any pointers on how to troubleshoot it? I used a linter to doublecheck my yaml for any gotchas but I am genuinely stuck.

Edit: I have the v2.0.0 tag checked out when building it but had v2.0.0-beta9.1 before that with the same issue. Main as well so presumably this is a me issue.

[rlperez]

Ok, so I was just trying one last minute thing and I notice if I change the run command to use -f local_config.edn with the above edn it appears to be honoring the configuration and starting a node. Basically the file has to be named local_config.yaml or local_config.edn. That seems not super intuitive. Is this in the documentation anywhere?

[jarohen]

that sounds like a bug tbh! let's get that one filed as an issue

[danmason]

Hi there 👋 - thanks for raising this! We’ve created the following issue to track it: #4540

In your original post, the filename was xtdb.config.yaml. This is what is currently causing the problem - the CLI’s validation logic treats .config.yaml as the file extension, rather than recognizing it as a .yaml file.

Renaming the file to something like xtdbconfig.yaml should allow the command to work correctly for now.

[rlperez]

Awesome! That makes much more sense. I was baffled but now the error message makes a lot more sense with your explanation. Thank you!

[danmason]

You're very welcome! Just a quick update on this - we’ve pushed a fix to main that allows the CLI to accept config files with multiple-dot extensions (like xtdb.config.yaml). This will be included in the next XTDB release.

Thanks again for reporting the issue - much appreciated! 😄