|
1332
by David Coles
Incorporated old faq.txt into new Sphinx docs |
1 |
.. IVLE - Informatics Virtual Learning Environment
|
2 |
Copyright (C) 2007-2009 The University of Melbourne
|
|
3 |
||
4 |
.. This program is free software; you can redistribute it and/or modify
|
|
5 |
it under the terms of the GNU General Public License as published by
|
|
6 |
the Free Software Foundation; either version 2 of the License, or
|
|
7 |
(at your option) any later version.
|
|
8 |
||
9 |
.. This program is distributed in the hope that it will be useful,
|
|
10 |
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
11 |
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
12 |
GNU General Public License for more details.
|
|
13 |
||
14 |
.. You should have received a copy of the GNU General Public License
|
|
15 |
along with this program; if not, write to the Free Software
|
|
16 |
Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
|
|
17 |
||
18 |
.. _ref-faq: |
|
19 |
||
20 |
**************************
|
|
21 |
Frequently Asked Questions
|
|
22 |
**************************
|
|
23 |
||
24 |
This is a list of Frequently Asked Questions for IVLE. It answers questions |
|
25 |
about common issues encountered when configuring or running the system. |
|
26 |
||
27 |
.. _ref-faq-how: |
|
|
1385
by David Coles
Fix references in Documentation |
28 |
|
|
1332
by David Coles
Incorporated old faq.txt into new Sphinx docs |
29 |
How can I...
|
30 |
============
|
|
31 |
||
32 |
... change the Terms of Service notice?
|
|
33 |
---------------------------------------
|
|
34 |
||
35 |
You should customize the ToS notice at :file:`/var/lib/ivle/notices/tos.html`. |
|
36 |
||
37 |
||
38 |
.. _ref-faq-why: |
|
|
1385
by David Coles
Fix references in Documentation |
39 |
|
|
1332
by David Coles
Incorporated old faq.txt into new Sphinx docs |
40 |
Why does...
|
41 |
===========
|
|
42 |
||
43 |
... Apache not restart?
|
|
44 |
-----------------------
|
|
45 |
||
46 |
Make sure no console processes are lying around (e.g. sudo killall |
|
47 |
python), then restart with ``sudo /etc/init.d/apache2 restart``. If the issue
|
|
48 |
persists, try stopping the server and starting it in two separate |
|
49 |
steps, so you see the errors reported by the start script. |
|
50 |
||
51 |
... IVLE dump me back to the login screen with no error when I try to login?
|
|
52 |
----------------------------------------------------------------------------
|
|
53 |
||
54 |
This is usually because IVLE can't save your session information. IVLE saves |
|
55 |
sessions to a sessions directory on disk. Unfortunately, this is not currently |
|
56 |
configurable in :file:`./setup.py` config. You need to edit the Apache config |
|
57 |
file. |
|
58 |
||
59 |
Look for ``PythonOption mod_python.file_session.database_directory``. Make
|
|
60 |
sure it is set to the place you want. Then, you need to manually make sure |
|
61 |
that directory exists. |
|
62 |
||
63 |
The default is :file:`/var/lib/ivle/sessions`. |
|
64 |
||
|
1387
by David Coles
FAQs for common error messages |
65 |
|
66 |
... ivle-buildjail throw an UnsafeJail exception
|
|
67 |
------------------------------------------------
|
|
68 |
||
69 |
When running :program:`ivle-buildjail` you may occasionally see an error |
|
70 |
like::
|
|
71 |
||
72 |
Traceback (most recent call last):
|
|
73 |
File "bin/ivle-buildjail", line 158, in <module>
|
|
74 |
raise UnsafeJail(d)
|
|
75 |
__main__.UnsafeJail: /var/lib/ivle/jails/__base_build__/tmp/.ICE-unix
|
|
76 |
||
77 |
This means that writable files exist in the Jail template. If left in the jail |
|
78 |
then users would be able to edit a file that is shared between all jail |
|
79 |
instances. The usual solution is just to remove these file from the jail build |
|
80 |
directory and try again. |
|
81 |
||
82 |
||
83 |
... the console return 'Console Restart' messages
|
|
84 |
-------------------------------------------------
|
|
85 |
||
86 |
There are three cases where a console may be restarted: |
|
87 |
||
88 |
1. **Console Restart: The IVLE console has timed out due to inactivity** |
|
89 |
||
90 |
The Python console process is no longer running. This is most likey due to |
|
91 |
the console process being automatically terminated due to no messages |
|
92 |
being sent or received by the console in the previous 15 minutes. |
|
93 |
||
94 |
This message can also be triggered if the console is terminated for |
|
95 |
another reason (such as being sent :const:`SIGKILL` from the system |
|
96 |
command line or any other fatal signal). |
|
97 |
||
98 |
2. **Console Restart: CPU Time Limit Exceeded** |
|
99 |
||
100 |
To prevent exhaustion of local system resources, Python console processes |
|
101 |
are set with an CPU Time Limit of 25 seconds of user time (time executing |
|
102 |
on the CPU rather than real "clock-on-the-wall" time). |
|
103 |
||
104 |
This setting can be configured by changing the values associated with |
|
105 |
:const:`RLIMIT_CPU` in :file:`bin/trampoline/trampoline.c`. |
|
106 |
||
107 |
3. **Console Restart: Communication to console process lost** |
|
108 |
||
109 |
IVLE was unable to understand a response from the console process. This |
|
110 |
will only happen if the console sends a malformed response and quite |
|
111 |
likely a bug. |
|
112 |
||
113 |
4. **Console Restart: Communication to console process reset** |
|
114 |
||
115 |
IVLE's TCP connection to the console process was reset. May indicate |
|
116 |
network issues. |
|
117 |