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 #2979 (closed)

Opened 14 years ago

Closed 14 years ago

Bug: bin/omero is too strict for scripting purposes

Reported by: jamoore Owned by: cxallan
Priority: critical Milestone: OMERO-Beta4.2.1
Component: Scripting Version: n.a.
Keywords: n.a. Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: 2010-09-30 (17)

Description

/opt/omero/OMERO-CURRENT$ bin/omero script serve user
FATAL: Cannot access /opt/omero/OMERO-CURRENT/var, a required directory for OMERO
/opt/omero/OMERO-CURRENT$ bin/omero -s omero.hms.harvard.edu -u jc168 script serve user
FATAL: Cannot access /opt/omero/OMERO-CURRENT/var/django.pid, a required directory for OMERO

These directories are necessary for a server installation, but not for a scripting installation. These checks may need to be moved to omero/plugins/admin.py or similar.

Change History (2)

comment:1 Changed 14 years ago by cxallan

  • Owner set to cxallan
  • Remaining Time set to 0.25
  • Status changed from new to assigned

comment:2 Changed 14 years ago by cxallan

  • Remaining Time changed from 0.25 to 0
  • Resolution set to fixed
  • Status changed from assigned to closed

(In [8219]) Solution to pedantic checks of 'var'. Moved checks to the admin plugin and made the checks read-only/read-write flexible (so that a user with only read-only rights can run bin/omero admin diagnostics for instance). (Fixes #2979)

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.69859 sec.)

We're Hiring!