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

sqlite3.OperationalError: unable to open database file repeated exception #293

Open
garilla2 opened this issue Oct 8, 2024 · 5 comments

Comments

@garilla2
Copy link

garilla2 commented Oct 8, 2024

On the latest clean and updated version of kali (tried multiple old updated boxes, and clean installs)

PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
VERSION_ID="2024.3"
VERSION="2024.3"
VERSION_CODENAME=kali-rolling
ID=kali
ID_LIKE=debian
HOME_URL="https://www.kali.org/"
SUPPORT_URL="https://forums.kali.org/"
BUG_REPORT_URL="https://bugs.kali.org/"
ANSI_COLOR="1;31"

We are getting repeated errors using responder as below:

[*] [MDNS] Poisoned answer sent to 192.168.X.X for name LAPTOP-XXXXXX(6681)._dosvc

Exception occurred during processing of request from ('::ffff:192.168.X.X', 5353, 0, 0)
Traceback (most recent call last):
File "/usr/lib/python3.11/socketserver.py", line 691, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.11/socketserver.py", line 361, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.11/socketserver.py", line 755, in init
self.handle()
File "/usr/share/responder/poisoners/MDNS.py", line 78, in handle
SavePoisonersToDb({
File "/usr/share/responder/utils.py", line 391, in SavePoisonersToDb
cursor = sqlite3.connect(settings.Config.DatabaseFile)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
sqlite3.OperationalError: unable to open database file

s1

@lgandx
Copy link
Owner

lgandx commented Oct 8, 2024 via email

@garilla2
Copy link
Author

garilla2 commented Oct 9, 2024

Thank you for timely response, will do so.

@fgeek
Copy link

fgeek commented Oct 14, 2024

@garilla2 Did you get Responder working from git? Can you close this issue if you did?

@garilla2
Copy link
Author

Good morning, and apologies for my tardy response. I used your version as recommended, and while there was less verbosity in the error generation, I had the exact same sqllite errors as above.

@lgandx
Copy link
Owner

lgandx commented Oct 15, 2024 via email

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

3 participants