Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #10999 (new)

Opened 11 years ago

Last modified 7 years ago

Better, prompter hints from bin/omero admin start

Reported by: mtbcarroll Owned by:
Priority: major Milestone: Unscheduled
Component: Deployment Version: OMERO-5.2.0
Keywords: n.a. Cc: server@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.


When bin/omero admin start fails it takes a long time to do so and then gives no suggestions. Some common conditions are actually quite promptly detectable -- server already running, wrong DB patch number, whatever -- it would be far nicer for the common cases if the script could give advice quickly instead of disappointment slowly.

Change History (9)

comment:1 Changed 11 years ago by jamoore

  • Cc jamoore added
  • Milestone changed from Unscheduled to OMERO-4.4.9
  • Owner jamoore deleted
  • Priority changed from minor to major

Similar feedback from stick:

so… I'm mucking around with improving the weekly index process we run for jcb and have attempted to start omero against a read-only database (yeah I know it won't work) but it strikes me as very misleading as to it's behavior. Basically the start seems to just hang, the blitz log certainly gives clues to what the problem is but seems like admin start should return an error or something more helpful (been running about 6m at this point without returning)

Other than teaching python how to connect to PG, a small java class with main would be needed that connects to the DB using the same spring configuration (ome/config.xml and ome/services/datalayer.xml) and does some form of validation (checking the dbpatch table, for example).

comment:2 Changed 10 years ago by spli

Another request: If OMERO.server is unable to listen on a port because it's already taken then warn immediately or abort startup.

comment:3 Changed 10 years ago by mtbcarroll

Another condition: on Windows, needing an administrator-level shell.

comment:4 Changed 10 years ago by mtbcarroll

See also #12464.

comment:5 Changed 8 years ago by jamoore

  • Milestone changed from 5.x to Unscheduled

comment:6 Changed 8 years ago by pwalczysko

  • Version set to OMERO-5.2.0

Note that if there is a DB mismatch, not only the error does not come back quickly and understandably, but logs, such as Indexer-0.log gets further and further ERRORs and WARNs as you are doing nothing else but trying to find out what is going on actually. Only bin/omero admin stop stops this flurry in the logs.

comment:7 Changed 7 years ago by mtbcarroll

  • Cc server@… added; omero-team@… jamoore removed

On trello: OMERO added to global PATH/PYTHONPATH jamoore suggests,

... omero could detect if more than one is present on the path ...

comment:8 Changed 7 years ago by mtbcarroll

Several man-hours were just wasted trying to run OMERO with Ice 3.6.1 which is already documented to not work. Some detection of bad prerequisites would be useful.

comment:9 Changed 7 years ago by spli

Several man-hours were just wasted trying to run OMERO with Ice 3.6.1 which is already documented to not work. Some detection of bad prerequisites would be useful.

The Ice check should be relatively easy to implement:


Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.62340 sec.)

We're Hiring!