Service fails to start, complains about server_name not being set #392

New issue

Open

opened 2023-10-03 16:22:03 +00:00 by desultory1 · 4 comments

desultory1 commented

2023-10-03 16:22:03 +00:00

(Migrated from gitlab.com)

I've created a LXC container, and have the following config:

lxc.init.uid = 249
lxc.init.gid = 249
lxc.environment = RUST_BACKTRACE=1
lxc.environment = CONDUIT_CONFIG="/etc/conduit/conduit.toml"
lxc.init.cmd = /usr/bin/tini /usr/bin/conduit

The container fails to start with:

It looks like your config is invalid. The following error occurred: missing field `server_name`

This is set. Changing the path to a nonexistent file does not throw any different error. Breaking the config doesn't throw a different error. As far as i can tell it's reading some default and disregarding my config file.

Why can't i just pass it as a parameter?

I've created a LXC container, and have the following config: ``` lxc.init.uid = 249 lxc.init.gid = 249 lxc.environment = RUST_BACKTRACE=1 lxc.environment = CONDUIT_CONFIG="/etc/conduit/conduit.toml" lxc.init.cmd = /usr/bin/tini /usr/bin/conduit ``` The container fails to start with: ``` It looks like your config is invalid. The following error occurred: missing field `server_name` ``` This is set. Changing the path to a nonexistent file does not throw any different error. Breaking the config doesn't throw a different error. As far as i can tell it's reading some default and disregarding my config file. Why can't i just pass it as a parameter?

Aranjedeath commented

2023-10-03 16:28:11 +00:00

(Migrated from gitlab.com)

confirm conduit inside the container can actually read that file. config invalid because of missing term is usually file path or permissions issue. you can pass all details via environment variables if you prefer, see: docker deploy directions for the list

desultory1 commented

2023-10-03 16:37:55 +00:00

(Migrated from gitlab.com)

if I run unshare and map to the same user the container uses, I can read the file fine.

lxc-conduit@amazon ~/.local/share/lxc/conduit $ ls -lan rootfs/etc/conduit/conduit.toml 
-rw-r--r--. 1 493216 493216 2119 Oct  3 11:08 rootfs/etc/conduit/conduit.toml
lxc-conduit@amazon ~/.local/share/lxc/conduit $ cat /etc/subuid | grep conduit
lxc-conduit:493216:65536
lxc-conduit@amazon ~/.local/share/lxc/conduit $ unshare --user --map-user 249 --map-group 249
I have no name!@amazon ~/.local/share/lxc/conduit $ file rootfs/etc/conduit/conduit.toml 
rootfs/etc/conduit/conduit.toml: ASCII text
I have no name!@amazon ~/.local/share/lxc/conduit $

What I find most concerning is that I'm getting an error about some missing field but it doesn't seem to be reading the file at all.

if I run unshare and map to the same user the container uses, I can read the file fine. ``` lxc-conduit@amazon ~/.local/share/lxc/conduit $ ls -lan rootfs/etc/conduit/conduit.toml -rw-r--r--. 1 493216 493216 2119 Oct 3 11:08 rootfs/etc/conduit/conduit.toml lxc-conduit@amazon ~/.local/share/lxc/conduit $ cat /etc/subuid | grep conduit lxc-conduit:493216:65536 lxc-conduit@amazon ~/.local/share/lxc/conduit $ unshare --user --map-user 249 --map-group 249 I have no name!@amazon ~/.local/share/lxc/conduit $ file rootfs/etc/conduit/conduit.toml rootfs/etc/conduit/conduit.toml: ASCII text I have no name!@amazon ~/.local/share/lxc/conduit $ ``` What I find most concerning is that I'm getting an error about some missing field but it doesn't seem to be reading the file at all.

germtoo commented

2023-10-30 03:52:05 +00:00

(Migrated from gitlab.com)

Installed conduit natively to an x86_64 LLVM musl device and hit a similar error that does little to inform one of the issue.config.toml This config is located in /etc/conduit/conduit.toml and the contents of CONDUIT_CONFIG=$"{CONDUIT_CONFIG:=/etc/conduit/conduit.toml}" The error mentions a missing field called server_name that is in my config as "server_name = "mipseb.com""

Installed conduit natively to an x86_64 LLVM musl device and hit a similar error that does little to inform one of the issue.[config.toml](/uploads/e5d49c2c84f8c1ea014f93f3a334a513/config.toml) This config is located in /etc/conduit/conduit.toml and the contents of CONDUIT_CONFIG=$"{CONDUIT_CONFIG:=/etc/conduit/conduit.toml}" The error mentions a missing field called server_name that is in my config as "server_name = "mipseb.com""

Richard-Rogalski commented

2023-10-30 04:39:17 +00:00

(Migrated from gitlab.com)

welp, source of the issue found.

I was walking through zen and mips here through setting up conduit, and realized I forgot a crucial step: setting the .well-known/matrix/server (my fault guys, sorry!!)

However I didn't figure that out until now as the error message was completely misleading. The message indicates that either A), you have a typo or something wrong with your toml, or B), conduit can't find the toml (as zen suggested) as it seems to also be the error for when it can't find the config.

I don't think zen tested with git master, so I don't know if there is a sane error message for "we can't find/don't have perms to read the config" yet, but that would be nice, but also a message here explaining that 'server name' is indeed NOT missing, it just does not match what conduit is expecting. (if that's the issue, I don't really understand why that error was popping up tbh, just that now it's fixed)

welp, source of the issue found. I was walking through zen and mips here through setting up conduit, and realized I forgot a crucial step: setting the .well-known/matrix/server (my fault guys, sorry!!) However I didn't figure that out until now as the error message was completely misleading. The message indicates that either A), you have a typo or something wrong with your toml, or B), conduit can't find the toml (as zen suggested) as it seems to also be the error for when it can't find the config. I don't think zen tested with git master, so I don't know if there is a sane error message for "we can't find/don't have perms to read the config" yet, but that would be nice, but also a message here explaining that 'server name' is indeed NOT missing, it just does not match what conduit is expecting. (if that's the issue, I don't really understand why that error was popping up tbh, just that now it's fixed)