Hello!
Last week I've had a look at the sample SQL-questions, and they worked perfectly well.
Since then, we had to go back to an older version of the server. It should be a very similar set-up, but it seems that there is a crucial difference I can't find. Maybe you can help me detect the problem, so I can revert that change?
When I run one of the example SQL-questions, two things happen:
- Moodle tells me in a banner at the top of the page that it "Cannot read file 'q1.db'. Either the file does not exist or there is a permission problem".
Validate on Save gives me the following error message in the 'Got'-column:
***Error*** Traceback (most recent call last): File "__tester__.python3", line 40, in <module> universal_newlines=True) File "/usr/lib/python3.5/subprocess.py", line 626, in check_output **kwargs).stdout File "/usr/lib/python3.5/subprocess.py", line 693, in run with Popen(*popenargs, **kwargs) as process: File "/usr/lib/python3.5/subprocess.py", line 947, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.5/subprocess.py", line 1551, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'sqlite3' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "__tester__.python3", line 43, in <module> raise Exception("sqlite3 error: " + str(e)) Exception: sqlite3 error: [Errno 2] No such file or directory: 'sqlite3'
['q1.db', 'prog.out', '__pycache__', 'prog.err', '__tester__.python3', 'prog.cmd']I see that sqlite3 is not present - should it be? how do I get it to be loaded into that directory?