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
FS#4085 - dnsmasq: cannot open or create lease file /tmp/dhcp.leases: Read-only file system #9064
Comments
bittorf: reverting this commit fixes it for me:
commit 44f694ba1bca1417d24e851c637c284f9f78c06d
Author: Daniel Golle
Date: Wed Oct 21 15:04:17 2020 +0100
|
Same issue on 22.03.0rc1 build for armvirt64 target after restoring old configuration tar. |
Same with rc4, also worked fine until restoring config |
opkg remove procd-ujail seems to have fixed it |
nice I guess we can set another location for
|
This issue in 22.03 is caused by the
If you update it to match the default 22.03 configuration as follows then the service will start correctly:
I do not understand why, or what the relationship is with the error reported for |
The root of the problem is that the 22.xx brings the I see two parallel solutions for the issue:
|
I updated to 22.03 and had this problem. After changing the resolvfile option as instructed by johnfzc, the dnsmasq starts. But a few seconds after dnsmasq successfully started, openwrt restarts. I can't understand why ? I see several ubus messages with ubus monitor just before reboot but no explication in logs. procd-ujail completely breaks my openwrt. The only solution is to simply uninstall the procd-ujail package. |
I found out why my openwrt reboots when dnsmasq is started with ujail.
As ujail starts dnsmaq in a container with another pid namespace, the pid of dnsmaq is 1. So, when the device is configured fine, proc-ujail works as expected. |
Had the same problem recently on 22.03.0. Simply remove |
yep, thanks a lot. it solves my problem |
@hauke I think this issue can be closed , correcting the option resolvfile setting in
will resolve the problem. You can also remove |
just went through fixing this, and here's my contribution: if you were previously using:
same problem as described above will occur. A usable replacement can be found in:
|
bittorf:
with a selfcompiled r17753 with mipsel ramips/mt7621 on 'TP-LINK Archer C6U'
It was working without these issues with r17560
The filesystem looks normal:
The text was updated successfully, but these errors were encountered: