NCSA uses the AG3.1 release on Fedora 8. (Thanks Doug!). We monitor it by my trying to connect when I think to do it, I'm trying to be more consistent, but you know how it goes. I've long suspected the problem arises when the logs roll over, but I can't confirm that. We restart it as needed and it can be days or weeks between.
Hope this helps myk "If you're clear in your vision and trust the people in your team with clear objectives, they will invariably do their best to achieve everything desired, and usually deliver everything you could have hoped for and even more." -Paul Debevec ----- Original Message ----- From: "Jeremy Mann" <[email protected]> To: "Thomas D. Uram" <[email protected]> Cc: "ag-tech" <[email protected]> Sent: Tuesday, February 3, 2009 11:47:46 AM GMT -06:00 US/Canada Central Subject: Re: [AG-TECH] Bridge service reliability? On Tue, Feb 3, 2009 at 11:32 AM, Thomas D. Uram <[email protected]> wrote: > We needn't wait until then. I'll document its operation and send that out > later today, and think about how to instrument it for debugging. > > If you have specific questions, send them along now and I'll address them in > the write-up. Well the questions which I have yet to receive a response are: 1. What Bridge code does NCSA and Argonne use? 2. Is it the same code base as AG3.1 or a custom version? 3. Do they also have to restart their Bridge servers on a daily/weekly basis? If not, why? If yes, how often do they restart it? -- Jeremy Mann [email protected] University of Texas Health Science Center Bioinformatics Core Facility http://www.bioinformatics.uthscsa.edu Phone: (210) 567-2672
