<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Curtis<div><br></div><div>Thanks for testing deployment</div><div><br><div><div>On 24 Oct 2009, at 00:00, Curtis Rueden wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi everyone,<br><br>I installed OMERO-Beta4.1 successfully on an Ubuntu Linux 9.04 (Jaunty) server.<br><br>However, I ran into problems trying to get OMERO.web working with Apache+mod_python as described on the "Web on production" page at:<br> <a href="http://www.openmicroscopy.org.uk/site/support/omero4/server/install_web">http://www.openmicroscopy.org.uk/site/support/omero4/server/install_web</a><br><br>I was able to overcome them, so I thought I would pass on the steps to do so, in case anyone else has similar difficulties.<br> <br>1) In the "Configure mod_python" step, presumably you are supposed to edit /etc/apache2/sites-available/default (or other Apache configuration file), placing those lines inside the relevant VirtualHost block, but it never indicates that anywhere. I suggest placing the Location block just before the "</VirtualHost>" at the bottom of the file.<br> <br>After editing the Apache configuration file, as you might expect (but is not documented anywhere), you should execute:<br> sudo /etc/init.d/apache2 reload<br></blockquote><div><br></div>Good idea<br><br><blockquote type="cite"> 2) When I ran the "syncdb" step, it initially blew up. The fix required two changes:<br><br> A) Install Django:<br> sudo aptitude install python-django<br><br> B) Chown the webdb and weblog folders back to omero:omero temporarily:<br> sudo chown -R omero:omero ~omero/omero/webdb ~omero/omero/weblog<br> And then back to www-data:www-data afterward.<br></blockquote><div><br></div>The command should be </div><div><pre><code>sudo -u apache_user PYTHONPATH=/home/omero/omero_dist/lib/python/ bin/omero web syncdb<br></code></pre><div>Django package is delivered with OMERO.server and does not need to be installed separately because it require particular version 1.0.</div><div>Doc is already fixed.</div><br><blockquote type="cite">3) I then ran into a problem accessing the URL in the web browser. The modules "webadmin.controller" and "webclient.controller" were not found. Looking in the OMERO distribution's lib/python folder, it appears that some modules are nested in a subdirectory called "omeroweb" -- so to fix the problem, I edited the Apache configuration file again, changing:<br> PythonPath "['/home/omero/omero_dist/lib/python'] + sys.path"<br>To:<br> PythonPath "['/home/omero/omero_dist/lib/python'] + ['/home/omero/omero_dist/lib/python/omeroweb'] + sys.path"<br> <br>Make sure these paths match where you actually have your omero_dist tree. Then restart your Apache again ("sudo /etc/init.d/apache2 reload").<br></blockquote><div><br></div>That is also fixed. Thanks<br><br><blockquote type="cite">With these steps I was able to get OMERO.web working with Apache+mod_python; I hope it is helpful to others as well.<font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></blockquote><div><br></div><div><br></div><blockquote type="cite"><br>Three additional comments for the developers:<br><br>1) When editing default.xml in the "Configuration Guide for mod_python" section, regarding the line with id="Web" and act="on-demand" is not commented out: the instructions are inconsistent. One place says to "comment the following" while another says to "re-configure the Web server in default.xml to be on-demand." Reading the lightweight OMERO.web instructions, it suggests changing "on-demand" to "always" so I am guessing this step means to change it back from "always" to "on-demand"? (I left the line alone and things are working for me.)<br></blockquote><div><br></div>Yes, that step says that if you have ever changed to "always", turn it back.<br><br><blockquote type="cite">2) On the OMERO server install page, I would suggest splitting out the Django server OMERO.web installation instructions into their own page as well, and just providing two links: one to the Django instructions (marked "easier but only suitable for localhost configuration") and the Apache/mod_python ones (marked "more involved but suitable for a production environment"). Right now it is not clear which, if any, of the OMERO.web instructions from the main page are applicable to the Apache/mod_python way of doing things.<br></blockquote><div><br></div>We have just merged two docs in one installation page because beginners, who want to run demo on their own machine, didn't know they needed to configure OMERO.web. From the other side, sysadmins had no problems with finding right docs.<br><br><blockquote type="cite">3) FYI, the log in ~omero/weblog still reports: "2009-10-23 17:40:24,601 omero.util.UpgradeCheck: WARNING UPGRADE AVAILABLE:Please upgrade to Beta-4.1-RC1 See <a href="http://trac.openmicroscopy.org.uk/omero">http://trac.openmicroscopy.org.uk/omero</a> for the latest version"<br></blockquote><div><br></div>Upgrade check contained old version, now should be fine.<br><br></div><div>THanks Curtis for help.</div><div><br><blockquote type="cite"><br>Regards,<br>Curtis<br><br> _______________________________________________<br>ome-users mailing list<br><a href="mailto:ome-users@lists.openmicroscopy.org.uk">ome-users@lists.openmicroscopy.org.uk</a><br>http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users<br></blockquote></div><br><div> <span class="Apple-style-span" style="font-size: 12px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Thanks</div><div>Ola</div></div></span> </div><br></div></body></html>