[ome-users] OMERO.web not starting
Wood, Christopher
CJW at stowers.org
Tue Jul 5 17:15:54 BST 2011
It could also be an issue with the PYTHONPATH, we are checking on that also.
Thanks
Chris
-----Original Message-----
From: Aleksandra Tarkowska [mailto:aleksandrat at lifesci.dundee.ac.uk]
Sent: Tuesday, July 05, 2011 11:09 AM
To: Wood, Christopher
Subject: Re: [ome-users] OMERO.web not starting
Dear Chris
I am glade it works. That is interesting. Definitely web does not use py-sqlite2 at all. There is DATABASE_ENGINE = 'sqlite3' set up because of unitetests, but I have never noticed any issues with that. I will look at that closer.
Thank you very much for you feedback.
Thanks
Ola
On 5 Jul 2011, at 16:59, Wood, Christopher wrote:
> Hi Ola,
>
> We have it working now. The devel web server required us to upgrade to py-sqlite2. After this upgrade, the apache/fastcgi omero.web works. Does OMERO.web/django require py-sqlite2? I couldn't find it in the documentation if that is the case.
>
> Thanks for your help.
> Chris
>
> -----Original Message-----
> From: Aleksandra Tarkowska [mailto:aleksandrat at lifesci.dundee.ac.uk]
> Sent: Tuesday, July 05, 2011 2:17 AM
> To: Wood, Christopher
> Subject: Re: [ome-users] OMERO.web not starting
>
> Hi Chris
>
> Sorry about delay in answer to you.
> Based on the diagnostics information
>
> OMERO.web status... [NOT STARTED]
>
> web hasn't started, obviously apache cant find preforked server then (omero.fcgi file does not exist).
>
> 1) Double check if there are no processes run behind
>
> Please run 'ps auxwf' and check if you see anything like this:
>
> omero 9991 0.0 0.2 99836 36040 ? S 07:54 0:00 python manage.py runfcgi workdir=./ method=prefork host=0.0.0.0 port=4080 pidfile=/home/omero/OMERO.server-4
> omero 9992 0.0 0.2 99836 35524 ? S 07:54 0:00 \_ python manage.py runfcgi workdir=./ method=prefork host=0.0.0.0 port=4080 pidfile=/home/omero/OMERO.serv
> omero 9993 0.0 0.2 99836 35524 ? S 07:54 0:00 \_ python manage.py runfcgi workdir=./ method=prefork host=0.0.0.0 port=4080 pidfile=/home/omero/OMERO.serv
> omero 9994 0.0 0.2 99836 35524 ? S 07:54 0:00 \_ python manage.py runfcgi workdir=./ method=prefork host=0.0.0.0 port=4080 pidfile=/home/omero/OMERO.serv
> omero 9995 0.0 0.2 99836 35524 ? S 07:54 0:00 \_ python manage.py runfcgi workdir=./ method=prefork host=0.0.0.0 port=4080 pidfile=/home/omero/OMERO.serv
> omero 9996 0.0 0.2 99836 35524 ? S 07:54 0:00 \_ python manage.py runfcgi workdir=./ method=prefork host=0.0.0.0 port=4080 pidfile=/home/omero/OMERO.serv
>
> If so, please kill the main one (in this case 9991) then try to start web again. Killing the main process should automatically destroy the workers.
>
> If this is not the issue lets try something else.
> 2) Running webclient by hand with the development server.
>
> cd /OMERO/OMERO.server-Beta-4.3.0/lib/python/omeroweb
> PYTHONPATH=$PYTHONPATH: /OMERO/OMERO.server-Beta-4.3.0/lib/python/
> python manage.py runserver 0.0.0.0:8000
>
> If there is any issue with the application you will immediately see it on the output. Please send me the errors I will try to help with them then.
>
> Once server started successfully you should see:
>
> Validating models...
> 0 errors found
>
> Django version 1.1.1, using settings 'omeroweb.settings'
> Development server is running at http://0.0.0.0:8000/
> Quit the server with CONTROL-C.
>
> Now, you can go to http://your_domain:8000/webadmin and you should see the login page.
>
> Let me know how this was going. I hope the problem would be solved.
>
> Thanks
> Ola
>
> On 2 Jul 2011, at 16:13, Wood, Christopher wrote:
>
>> Hi Ola,
>>
>> Everything is attached in the gzipped tar file.
>>
>> Thanks
>> Chris
>> ________________________________________
>> From: Aleksandra Tarkowska [aleksandrat at lifesci.dundee.ac.uk]
>> Sent: Saturday, July 02, 2011 12:39 AM
>> To: Wood, Christopher
>> Cc: ome-users at lists.openmicroscopy.org.uk
>> Subject: Re: [ome-users] OMERO.web not starting
>>
>> Hi Chris
>>
>> Could you please send me the output from:
>>
>> bin/omero config get (this is stored in omero/etc/grid/config.xml)
>> bin/omero diagnostics
>>
>> apache and nginx config supporting OMERO.
>>
>> Thanks
>> Ola
>>
>> On 1 Jul 2011, at 20:58, "Wood, Christopher" <CJW at stowers.org<mailto:CJW at stowers.org>> wrote:
>>
>> Hi,
>> We upgraded our server today to 4.3. OMERO.web is not starting (it worked for 4.2.2).
>>
>> the error.log from apache is listed below:
>>
>> [Fri Jul 01 14:06:35 2011] [error] [client 10.2.20.65]
>> (111)Connection
>> refused: FastCGI: failed to connect to server "/OMERO/OMERO.server-Beta-4.3.0/var/omero.fcgi": connect() failed [Fri Jul 01 14:06:35 2011] [error] [client 10.2.20.65] FastCGI: incomplete headers (0 bytes) received from server "/OMERO/OMERO.server-Beta-4.3.0/var/omero.fcgi"
>>
>> We don't receive any error on bin/omero web start or in the OMERO.web log files.
>>
>> linux (centos), apache httpd, mod_ fastcgi python 2.4, postgres 8.4
>>
>> I tried this on my VM and have the same problems.
>>
>> Any ideas?
>>
>> Thanks
>> Chris
>> _______________________________________________
>> ome-users mailing list
>> ome-users at lists.openmicroscopy.org.uk<mailto:ome-users at lists.openmicr
>> o
>> scopy.org.uk>
>> http://lists.openmicroscopy.org.uk/mailman/listinfo/ome-users
>> <stowers_omero_web.tgz>
>
More information about the ome-users
mailing list