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
Captive Portal: Fails to start wit sqlite3.OperationalError #3425
Comments
ok, that's odd, the rc scripts should create the directories. core/src/etc/rc.d/captiveportal Line 88 in ac6a1ef
Are you sure its enabled and applied? We should fix the list clients to not crash when the directory doesn't exist, but that probably won't fix your issue. |
…t, make sure the directory exists. for #3425
Looks like the order during the first startup of captiveportal is wrong:
Interestingly, the |
then a193e1e will probably fix the issue |
Applied the patch in a vm for testing, looks good, thank you :) |
thanks for confirming! |
…t, make sure the directory exists. for opnsense#3425
…t, make sure the directory exists. for opnsense#3425
Describe the bug
The
captiveportal
-service fails to start after creation of the first Zone. The error reported by configd is:Manually calling the offending script to get a full stack trace:
The database_filename is
/var/captiveportal/captiveportal.sqlite
, but:To Reproduce
Steps to reproduce the behavior:
/var/captiveportal
is not created, the servicecaptiveportal
fails to start.Expected behavior
/var/captiveportal
is also created with the configuration described above, so the servicecaptiveportal
starts as designed.Workaround
Changing the Authentication source in the Captive Portal zone to "Local Database" only creates the directory, then the Radius server as authentication source can be added afterwards.
Environment
The text was updated successfully, but these errors were encountered: