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

Opened 11 years ago

Closed 9 years ago

Bug: sessions not cleaned on daily builds.

Reported by: jamoore Owned by: cblackburn
Priority: major Milestone: 5.1.1
Component: Deployment Version: 5.1.0
Keywords: n.a. Cc: sbesson, cxallan, cblackburn
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

The daily jobs (e.g. OMERO-merge-develop) perform bin/omero login, but do not logout. (See docs/hudson/OMERO-start.sh). This leaves a load of sessions in the ~/omero/sessions directory. Logout should be called actively, but as a further pre-caution, the sessions directory can be moved to OMERO-CURRENT in order to have a temporary (day-long) lifetime.

This is likely the cause of the SSL problems on import:
http://hudson.openmicroscopy.org.uk/job/OMERO-trunk-components/component=start,label=linux/1517/console

2013-03-24 09:02:52,403 3108       [      main] INFO       ome.formats.OMEROMetadataStoreClient  - Attempting initial SSL connection to localhost:4064
2013-03-24 09:02:59,454 10159      [      main] ERROR  formats.importer.cli.CommandLineImporter  - Error during import process.
Ice.ConnectionLostException
    error = 0
	at IceSSL.TransceiverI.readNonBlocking(TransceiverI.java:689)
	at IceSSL.TransceiverI.handshakeNonBlocking(TransceiverI.java:394)
	at IceSSL.TransceiverI.initialize(TransceiverI.java:43)
	at Ice.ConnectionI.initialize(ConnectionI.java:1536)
	at Ice.ConnectionI.socketReady(ConnectionI.java:1116)
	at Ice.ConnectionI$SocketReadyCallback.socketReady(ConnectionI.java:2299)
	at IceInternal.SelectorThread.run(SelectorThread.java:203)

since by this point in the job, the parent process has opened so many communicators that some resource (ports? entropy?) is no longer available.

Change History (6)

comment:1 Changed 11 years ago by jamoore

Another option might be to limit the number of active sessions to 10 or similar, closing all >10 on login.

comment:2 Changed 11 years ago by sbesson

  • Owner set to sbesson
  • Status changed from new to accepted

comment:3 Changed 11 years ago by sbesson

  • Milestone changed from OMERO-4.4.x to OMERO-5

Moving ticket to OMERO-5 milestone since the components builds has been disabled until Paris. Will be fixed this summer with the integration test effort.

comment:4 Changed 11 years ago by sbesson

  • Owner changed from sbesson to cblackburn

OMERO-trunk-components has been disabled until Paris Users meeting 2013. These integrations tests will be rewritten over the summer.

In the meantime, lots of sessions are currently created (and not closed) in the auto-import scripts. Delegating this ticket to Colin for now who is working on omero-setup.git.

comment:5 Changed 9 years ago by jamoore

  • Milestone changed from 5.x to 5.1.1
  • Version set to 5.1.0

This can be closed now, right?

comment:6 Changed 9 years ago by sbesson

  • Resolution set to fixed
  • Status changed from accepted to closed

Closing. The logic is in-place on 5.0.x via the OMERO_SESSION_DIR envvar to isolate sessions per job. This is already used by the daily integration job and can be similarly implemented for a resurrect CI auto-import job or any other CI job requiring CLI sessions cretated.

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

We're Hiring!