InstallationUpdate problems » History » Version 2
  Amber Herold, 04/15/2010 10:09 AM 
  
| 1 | 1 | Amber Herold | h1. InstallationUpdate problems | 
|---|---|---|---|
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | * <link linkend="InstT_win_install">Python installer fails on pyScope and numExtension for | ||
| 9 | Windows</link> | ||
| 10 | |||
| 11 | |||
| 12 | * <link linkend="InstT_bad_update">Not all files are updated</link> | ||
| 13 | |||
| 14 | |||
| 15 | * <link linkend="InstT_1st_Grp">New Group/User added does not show up in the selection | ||
| 16 | list in Web Leginon Administration Tool</link>. | ||
| 17 | |||
| 18 | |||
| 19 | * <link linkend="Inst_no_tomo">I can't install SciPy/NumPy on SUSE</link> | ||
| 20 | |||
| 21 | |||
| 22 | * <link linkend="InstT_php_display_error">Something is not showing in Web viewer or the | ||
| 23 | administration tool components</link> | ||
| 24 | |||
| 25 | |||
| 26 | * <link linkend="instlT_updatecom">Stage does not move after a pyScope update on the | ||
| 27 | computer controlling the microscope</link> | ||
| 28 | |||
| 29 | |||
| 30 | |||
| 31 | |||
| 32 | |||
| 33 | |||
| 34 | |||
| 35 | h2. Failed pyScope numExtension Window installation through | ||
| 36 | python | ||
| 37 | |||
| 38 | |||
| 39 | |||
| 40 | |||
| 41 | |||
| 42 | <title>Why:</title> | ||
| 43 | * Specially compiled pyScope and numExtension are needed to comunicate with Gatan | ||
| 44 | CCD camera. Currently we only have them compiled for python2.5 | ||
| 45 | |||
| 46 | |||
| 47 | Solution: Download and use python2.5 and use the window-installer in win-install | ||
| 48 | folder (start by double-clicking them) not "python setup.py install". | ||
| 49 | |||
| 50 | |||
| 51 | |||
| 52 | |||
| 53 | |||
| 54 | |||
| 55 | |||
| 56 | |||
| 57 | |||
| 58 | h2. Incomplete Leginon update | ||
| 59 | |||
| 60 | |||
| 61 | |||
| 62 | This normally happens to files that you have modified in the previous version. | ||
| 63 | |||
| 64 | |||
| 65 | |||
| 66 | |||
| 67 | <title>Why:</title> | ||
| 68 | * unknown | ||
| 69 | |||
| 70 | |||
| 71 | Solution: Remove the old installation first. | ||
| 72 | |||
| 73 | |||
| 74 | |||
| 75 | |||
| 76 | * Find the location of your Leginon installation. Once you have tried,even | ||
| 77 | unsuccessfully, to install Leginon. You can use the following command to find | ||
| 78 | the directory: | ||
| 79 | |||
| 80 | |||
| 81 | |||
| 82 | <pre>Linux> cd | ||
| 83 | Linux> start-leginon.py -v</pre> | ||
| 84 | <pre>Window> Go to \All Programs\Leginon\Leginon Folder from your Start Menu</pre> | ||
| 85 | |||
| 86 | |||
| 87 | |||
| 88 | * Go to the directory above it. This is normally the site-package directory | ||
| 89 | under your python installation | ||
| 90 | |||
| 91 | |||
| 92 | |||
| 93 | <pre>Linux> rm -r Leginon | ||
| 94 | Window> drag the Leginon folder to Recycle Bin</pre> | ||
| 95 | |||
| 96 | |||
| 97 | |||
| 98 | * Redo Leginon installation. | ||
| 99 | |||
| 100 | |||
| 101 | |||
| 102 | |||
| 103 | |||
| 104 | |||
| 105 | |||
| 106 | |||
| 107 | |||
| 108 | |||
| 109 | |||
| 110 | |||
| 111 | |||
| 112 | h2. Installation without a class of nodes | ||
| 113 | |||
| 114 | |||
| 115 | If you encounter a problem with node classes that you don't actually use, you may avoid | ||
| 116 | loading the codes with the following modification: | ||
| 117 | |||
| 118 | |||
| 119 | |||
| 120 | |||
| 121 | * Fnd the location of your Leginon installation | ||
| 122 | |||
| 123 | |||
| 124 | |||
| 125 | <pre>Linux> cd | ||
| 126 | Linux> start-leginon.py -v</pre> | ||
| 127 | |||
| 128 | |||
| 129 | |||
| 130 | * go to the subdirectory of noderegistry | ||
| 131 | |||
| 132 | |||
| 133 | |||
| 134 | <pre>Linux/home> cd leginon_directory/noderegistry</pre> | ||
| 135 | |||
| 136 | |||
| 137 | |||
| 138 | * edit the file "default.ncr" to coment out the registry of the class of nodes that | ||
| 139 | you do not need (Tomography node class in this example): | ||
| 140 | |||
| 141 | |||
| 142 | |||
| 143 | <pre>#[Tomography] | ||
| 144 | #module: tomography | ||
| 145 | #type: Pipeline | ||
| 146 | #package: tomography</pre> | ||
| 147 | |||
| 148 | |||
| 149 | |||
| 150 | |||
| 151 | |||
| 152 | |||
| 153 | |||
| 154 | |||
| 155 | |||
| 156 | |||
| 157 | h2. SciPy Installation failed in SuSE | ||
| 158 | |||
| 159 | |||
| 160 | |||
| 161 | SciPy may not build properly on some versions of SuSE due to an incompatible LAPACK | ||
| 162 | package that comes with SuSE. You can get scipy as well as a compatible LAPACK etc. from | ||
| 163 | http://repos.opensuse.org/science (need to specify your SuSE version and machine etc. | ||
| 164 | |||
| 165 | |||
| 166 | |||
| 167 | |||
| 168 | |||
| 169 | h2. Display errors on webviewer and web | ||
| 170 | administration tools | ||
| 171 | |||
| 172 | |||
| 173 | |||
| 174 | To display error and report them to get help for the php, including mysql-php and mrc | ||
| 175 | extension, do the following: | ||
| 176 | |||
| 177 | |||
| 178 | * Find your php.ini the following parameters and change them accordingly: | ||
| 179 | |||
| 180 | |||
| 181 | |||
| 182 | <pre>display_errors = On | ||
| 183 | error_reporting = E_ALL & ~E_NOTICE</pre> | ||
| 184 | |||
| 185 | |||
| 186 | |||
| 187 | * Restart your apache server | ||
| 188 | |||
| 189 | |||
| 190 | |||
| 191 | <pre>> /etc/init.d/apache2 restart</pre> | ||
| 192 | |||
| 193 | |||
| 194 | |||
| 195 | * From your webbrowser, refresh the problematic page. If you don't know what to do | ||
| 196 | with it, report it when you ask for help. | ||
| 197 | 2 | Amber Herold | |
| 198 | ______ | ||
| 199 | |||
| 200 | [[Getting Help|< Getting Help]] | [[Administration Tool problems|Administration Tool problems >]] |