4 This page provides a list of common problems and errors encountered when
5 installing Ganeti Web Manager with Fabric, and their solutions.
7 If you discover ambiguities or problems with the installation
8 instructions that aren't addressed in this page, please ask in the
9 #ganeti-webmgr channel on Freenode! If you're unfamiliar with IRC,
10 Freenode's `Using the Network <http://freenode.net/using_the_network.shtml>`_
11 document can help you get started.
21 sudo pip install fabric
28 sudo apt-get install python-pip
38 Fatal error: Couldn't find any fabfiles!
40 #. Are you in the ganeti\_webmgr directory?
41 #. Are you running version **0.7**? Check your version in the Changelog.
42 **0.7** is the first release to come packaged with the fabfile. There
43 will be a short interval between the publication of these
44 instructions and the release of **0.7** during which install from
45 Fabric will not work from the master, which is what Fabric
46 automatically downloads. If you want to use Fabric before **0.7** is
47 officially released, you'll need to use the develop version:
51 git pull origin develop
53 Can't find settings.py
54 ~~~~~~~~~~~~~~~~~~~~~~
58 Error: Can't find the file 'settings.py' in the directory containing './manage.py'. It appears you've customized things.
59 You'll have to run django-admin.py, passing it your settings module.
60 (If the file settings.py does indeed exist, it's causing an ImportError somehow.)
62 Did you remember to **cp setttings.py.dist settings.py** ?
64 Database Error ("no such table", "no column named *\_*", etc.)
65 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
70 no such table: django_session
76 table ganeti_web_virtualmachinetemplate has no column named disks
78 when this error appears in your browser (with testing set to true in
79 your settings.py), you might be able to fix it by quitting the server
80 and running **./manage.py syncdb --migrate**
82 If the error persists, try **diff settings.py.dist settings.py**. Add
83 any lines from settings.py.dist to settings.py that weren't previously
85 You could use **cp settings.py.dist settings.py**, but that would
86 overwrite any custom settings you've added. Then:
90 ./manage.py reset ganeti_web
91 ./manage.py syncdb --migrate
93 This works because reset then syncdb causes the database to be
94 re-created containing tables that the installed apps listed in
95 settings.py will need. If the app whose table was missing (such as
96 tastypie) was not listed in your settings.py, no table would have been
99 DRBD machine creation error
100 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
104 Primary and Secondary Nodes must not match
106 This happens when you try to create a machine using drbd disk template
107 on a cluster with only one node. The template requires both a primary
108 and a secondary node, and if your cluster doesn't have a second node,
109 the 'secondary node' selection field cannot be made available. The
110 solution is to either add another node to your cluster, or select a
111 different disk template.
113 Instance Create error
114 ~~~~~~~~~~~~~~~~~~~~~
120 The given name (<name of VM you're trying to create>) does not resolve: Name or service not known
122 Cause of Error: The name you chose for your VM broke the DNS name
124 Solution: Click edit at the lower right of the error screen. If you're
125 sure you gave it the name you want, uncheck the DNS Name Check box and
126 click create again. Otherwise, change the Instance Name to something
127 that will resolve better, leave the DNS Name Check box checked, and
130 OS Create Script Failed
131 ~~~~~~~~~~~~~~~~~~~~~~~
135 OS create script failed (exited with exit code 1)
137 If you get this error when creating a VM, you should try deleting the VM
138 and re-creating it with more disk space. A good rule of thumb is to give
147 Instance 'oldname.gwm.osuosl.org' not known
149 This error occurs when you had the DNS name check enabled when renaming
158 Instance 'breakthis.gwm.osuosl.org' not known
160 - Diskless machines cannot start. This error sometimes happens when you
162 - Is the OS successfully installed?
167 Problem: output such as **raise TemplateDoesNotExist(name)
168 TemplateDoesNotExist:** from either testing or trying to use the site.
170 Solution: If you've recently updated from the Develop branch (recently
171 as in 6/28/2011), you'll need to **cp settings.py.dist settings.py**
172 again. If you had an old settings.py, it will be looking for the
173 templates in the wrong place. It seeks the templates in a top-level
174 registration directory, when they're now actually in a sub-directory of
175 the ganeti\_web\_layout module.
177 whoosh\_index not writable for current user/group
178 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
180 Situation: This can happen when running GWM through Apache.
185 chown apache:apache whoosh_index/