Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with umdns and dawn #241

Open
kingrun opened this issue Mar 27, 2024 · 0 comments
Open

Issues with umdns and dawn #241

kingrun opened this issue Mar 27, 2024 · 0 comments

Comments

@kingrun
Copy link

kingrun commented Mar 27, 2024

Hello,

I have a router that has a compatible snapshot version of Openwrt in the firmware selector.
TP-Link Archer C50 v6 (CA/EU/RU)

I have updated it to the latest SNAPSHOT version. But I am having trouble setting up umdns and dawn on this router. I am using the default config just by installing the packages. But in the logs, I see these errors.

By default, the umdns config has the option jail 1 and it seems to not be able to set up during boot.
cat /etc/config/umdns
config umdns
option jail 1
list network lan

The error is:
user.err : jail: failed to clone/fork: Invalid argument

After 6 times it just gives this message:
daemon.info procd: Instance umdns::instance1 s in a crash loop 6 crashes, 0 seconds since last crash

Since umdns is failing to seemingly setup, dawn is also not working with errors like:

daemon.err dawn: ubus_call_umdns()=ubus.c@1385 Failed to look up test object for umdns

I have successfully been able to set up this same configuration (using defaults) with two other different routers but they run release versions and not SNAPSHOT. I am unsure if this is the problem that the firmware used is not a release version.

I couldn't find what exactly is the cause of the jail: failed to clone/fork: Invalid argument

Is there any way to troubleshoot this?
I tried the proposed fixes in https://openwrt.org/docs/guide-user/network/wifi/dawn (although it is listed for older versions of openwrt) like:

/etc/init.d/umdns restart
or
mv /etc/seccomp/umdns.json /etc/seccomp/umdns.json.disable

But this doesnt seem to be related to the issue I am facing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant