From shott at snf.stanford.edu Tue Sep 4 16:22:47 2001 From: shott at snf.stanford.edu (John Shott) Date: Tue, 04 Sep 2001 16:22:47 -0700 Subject: Comment metalica 2001-09-04 16:09:21: New Log Sheets Message-ID: <3B956247.AA19DA23@snf.stanford.edu> Jeannie: Let me clarify what some of the mailing lists for equipment are and who gets the messages: Each piece of equipment has 2 mailing lists: one called machine_name at snf.stanford.edu and one called machine_name-pcs at snf.stanford.edu (where the -pcs stands for "Problems, Comments, and Shutdowns"). In the case of metalica ... all of the people who are on the qualified user list are on the metalica at snf mailing list, but only the staff (engineering, process, and maintenance) are on the metalica-pcs mailing list. At the moment, the parts of the Coral equipment client that handle problems, shutdowns, and comments only send messages to the "-pcs" mailing list. In this case, I don't think this is what you want. You can send this message to all of the metalica users by simply sending an e-mail message (using whatever your favorite mail client is) to metalica at snf.stanford.edu. When we have a chance to improve upon the equipment maintenance portion of coral we may give folks the option of sending out messages to all users in addition to the equipment folks ... but, for now, the comment message that you sent didn't go to the folks that, I'm guessing, you had hoped it would. Thanks, John > Please use new log sheets in lab for the Metalica. In a larger > green binder. The old binder has been removed from the lab. From jtsai at kumetrix.com Thu Sep 6 14:27:46 2001 From: jtsai at kumetrix.com (Jr-Hung Tsai) Date: Thu, 06 Sep 2001 14:27:46 -0700 Subject: help on remote coral Message-ID: <3B97EA52.9050606@kumetrix.com> Dear technical consultant: This is Jr-Hung Tsai, a new SNF user. I'm trying to setup the remote coral on my company computer. It was successful until I launched remote coral. The login window popped out. After I typed in the login name and password, an error message window came out after a long while. The message is like this: "cannot access equipment information" Could you help me solve the problem. Thank you! Jr-Hung Tsai From arvisun at stanford.edu Wed Sep 12 14:29:14 2001 From: arvisun at stanford.edu (arvind sundaramurthy) Date: Wed, 12 Sep 2001 14:29:14 -0700 Subject: Problems Logging onto coral Message-ID: <000c01c13bd1$f8b500e0$865540ab@stanford.edu> hi, I am not able to log onto the sun system while in the clean room.My login is arvind. But I am able to log on remotely to snf.stanford.edu could you please fix the problem for me at the earliest.Thanks a lot. Arvind -------------- next part -------------- An HTML attachment was scrubbed... URL: From booth at snf.stanford.edu Thu Sep 13 10:39:38 2001 From: booth at snf.stanford.edu (Len Booth) Date: Thu, 13 Sep 2001 10:39:38 -0700 Subject: can't post shutdown Message-ID: <3BA0EF5A.A36638D5@snf.stanford.edu> Gents - Right now, using remote CORAL, I am not able to do a shutdown on Drytek1. When I attemt this, after a short delay (5sec) a popup appears saying: "! Could not post shutdown message." Len From bmurray at snf.stanford.edu Thu Sep 13 13:19:13 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Thu, 13 Sep 2001 13:19:13 -0700 (PDT) Subject: can't post shutdown In-Reply-To: <3BA0EF5A.A36638D5@snf.stanford.edu> Message-ID: Len, I restarted the servers at about 8:30am this morning. Your probably needs to be restarted. Bill On Thu, 13 Sep 2001, Len Booth wrote: > Gents - > Right now, using remote CORAL, I am not > able to do a shutdown on Drytek1. > When I attemt this, after a short delay (5sec) > a popup appears saying: > "! Could not post shutdown message." > Len > From mtang at snf.stanford.edu Thu Sep 13 16:05:40 2001 From: mtang at snf.stanford.edu (Mary Tang) Date: Thu, 13 Sep 2001 16:05:40 -0700 Subject: Fwd: snf coral References: <20010913215448.5652.cpmta@c001.snv.cp.net> Message-ID: <3BA13BC4.2CAF42DE@snf.stanford.edu> Hi Nina -- I have reserved the sts for mnepo from 5 am to 8:30 am, as it is available. I am not making your other reservations you have requested because I am abiding by the "maximum of one-week in advance" reservation rule. Contact me again tomorrow if you still want the 5 am Friday slot. I trust that you are fully qualified on this system. Many people such as you do have difficulty in accessing remote Coral, as Mike Bell indicates. However, none of these problems is insurmountable and has to do with the type of security firewalls that your internal network has. Thus, the info I sent in previous emails is still accurate (http://snf/Labmembers/RemoteCoralTSGuide.html). You could still access remote Coral, as many people do, using the methods described on the website. What Mike is working on is an alternative approach, which should help organizations such as yours which have not upgraded. Mary ntikho at megasenseinc.com wrote: > Hi Mary, > Please be advised that according to Mike Bell (see message below) we cannot access equipment reservation. > Please make reservation on STS for users mnepo(Mark Nepomnishy) and ntikho(Nina Tikhomirova): > September 20 - 4 hrs any time from 5 AM > September 21 - 4 hrs any time from 5 AM > September 27 - 4 hrs any time from 5 AM > Best regards > Nina Tikhomirova, > Mark Nepomnishy > Megasense Inc. > Phone: (408) 436-9783 > > ------- Start of forwarded message ------- > > From: Mike Bell Save > Date: Tue, 11 Sep 2001 09:28:32 -0700 > To: mnepo at snf.stanford.edu > Subject: Your request. > > --------------------------------------------------------------------------------Mark, > > Unfortunately you are among many who are unable to get remote coral to work. We hope to address this > in a new release of the software due out in the next couple weeks. > Since I work primarily on the software > I was unclear as to what the other issue was you having trouble resolving. I'm sure that Mary Tang > mtang at snf.stanford.edu (process tech issues) or Richard Crane rcrane at snf.stanford.edu (equipment issues) or John Shott shott at snf.stanford.edu (other issues) will be able to help you resolve > this. > > Thanks, > > Mike > snf staff > > > > ------- End of forwarded message ------- -- Mary X. Tang, Ph.D. National Nanofabrication Users' Network Stanford Nanofabrication Facility CIS Room 136, Mail Code 4070 Stanford, CA 94305 (650)723-9980 mtang at snf.stanford.edu From bmurray at snf.stanford.edu Fri Sep 14 09:15:29 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Fri, 14 Sep 2001 09:15:29 -0700 (PDT) Subject: New Event Manager Running Message-ID: John, I got the new event manager (incorporating the changes we discussed) running this morning at about 9:00am. There were only a few users in the lab when I restarted the servers. Bill PS I will be in the office to test the accounting changes as soon as I clean up and eat breakfast. From bmurray at snf.stanford.edu Mon Sep 17 11:33:33 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Mon, 17 Sep 2001 11:33:33 -0700 (PDT) Subject: Coral Changes Message-ID: Len, I spoke with John regarding the changes we discussed. I have modified the history client so that the initial window (time horizon) ends today instead of yesterday. This will be released with a large number of other enhancements this week. The issues we discussed related to client registration, messaging, and automatic shutdown are on the priority list but will not be addressed until we finish the inventory module. Thanks, Bill From bmurray at snf.stanford.edu Mon Sep 17 20:51:11 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Mon, 17 Sep 2001 20:51:11 -0700 (PDT) Subject: Status Message-ID: John, On my final test, I have found something that I don't quite understand. I'll take a look at it when I get home. It may be ok. It was just unexpected. Once I run this down, I think we can install the new version in production. Can I use obfuscation yet? Thanks, Bill From skumar at JasmineNetworks.com Mon Sep 24 18:09:29 2001 From: skumar at JasmineNetworks.com (Sunil Kumar) Date: Mon, 24 Sep 2001 18:09:29 -0700 Subject: coral access behind firewall Message-ID: hurray! coral does work behind my firewall, thanks a lot, it saves me and the planet a lot of trees(hmm! or is it oil) !!!! btw in case u need i have the log file from two sessions attached. thanks again!! Sunil :) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: coral092401.txt URL: From gymclean at alum.mit.edu Mon Sep 24 16:54:25 2001 From: gymclean at alum.mit.edu (George Y. McLean) Date: Mon, 24 Sep 2001 18:54:25 -0500 Subject: remote coral from behind a firewall Message-ID: <2.2.32.20010924235425.01a9ee04@mail.pinol1.sfba.home.com> John, I am running Remote Coral from behind a firewall of sorts, and am happy to report that Remote Coral seems to be running fine. For my "firewall" (I hear that packet filtering and address translation aren't technically firewalling, hence the quotation marks) I'm running Linux with a kernel version 2.2.something, implementing packet filtering and network address translation. The machine from which I run Remote Coral is running Win 98. Also, in the not-so-distant future I will start using a newer kernel on my firewall machine, which will allow me to use "netfilter," a more sophisticated packet filtering scheme. I'll tell you how that works, too. If you care to know more details or need troubleshooting help, please let me know. I appreciate your support of Remote Coral, and would be happy to contribute. Thanks, George McLean Optobionics, Co. gmclean at snf.stanford.edu From pruitt at stanford.edu Mon Sep 24 21:44:39 2001 From: pruitt at stanford.edu (Beth Pruitt) Date: Mon, 24 Sep 2001 21:44:39 -0700 Subject: remote coral test Message-ID: <4.2.0.58.20010924212410.00add380@pruitt.pobox.stanford.edu> error:unable to get admin manager, trying again... just tried remote coral from home over cable modem. no luck. will try from behind a firewall tomorrow. hope this helps, Beth -------------- next part -------------- Java Web Start Console, v1.0 started Mon Sep 24 21:27:20 PDT 2001 Logging to file: c:\coral_1 Java Web Start Console, v1.0 started Mon Sep 24 21:34:40 PDT 2001 Logging to file: c:\coral_1 Labnet instantiated with parameter: remote You are running the remote version of Coral. Include file: /usr/local/coral/etc/Client.conf ADMMGR_IOR_LOC: http://bopeep.snffab.stanford.edu/ {jnlpx.heapsize=NULL,NULL, java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, jnlpx.splashport=1090, sun.boot.library.path=C:\Program Files\Java Web Start\1.3.0\bin, java.vm.version=1.3.0-C, java.vm.vendor=Sun Microsystems Inc., java.vendor.url=http://java.sun.com/, path.separator=;, java.vm.name=Java HotSpot(TM) Client VM, file.encoding.pkg=sun.io, jnlpx.home=C:\Program Files\Java Web Start, java.vm.specification.name=Java Virtual Machine Specification, user.dir=C:\, java.runtime.version=1.3.0-C, java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment, os.arch=x86, java.io.tmpdir=C:\DOCUME~1\BPRUIT~1.PRU\LOCALS~1\Temp\, line.separator= , java.vm.specification.vendor=Sun Microsystems Inc., jnlpx.remove=true, java.awt.fonts=, os.name=Windows 2000, java.library.path=C:\Program Files\Java Web Start\1.3.0\bin;.;C:\WINNT\System32;C:\WINNT;C:\Program Files\Java Web Start;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\VXIpnp\WINNT\BIN;"C:\Program Files\Java Web Start";"C:\Program Files\Java Web Start", java.specification.name=Java Platform API Specification, java.class.version=47.0, os.version=5.0, user.home=C:\Documents and Settings\bpruitt.PRUITT_LAPTOP, java.security.policy=file:C:\Program Files\Java Web Start/javaws.policy, user.timezone=America/Los_Angeles, trustProxy=true, java.awt.printerjob=sun.awt.windows.WPrinterJob, file.encoding=Cp1252, java.specification.version=1.3, java.class.path=C:\Program Files\Java Web Start\javaws.jar, user.name=bpruitt, java.vm.specification.version=1.0, java.home=C:\Program Files\Java Web Start\1.3.0, user.language=en, java.specification.vendor=Sun Microsystems Inc., awt.toolkit=sun.awt.windows.WToolkit, java.vm.info=mixed mode, java.version=1.3.0, java.ext.dirs=C:\Program Files\Java Web Start\1.3.0\lib\ext, sun.boot.class.path=C:\Program Files\Java Web Start\1.3.0\lib\rt.jar;C:\Program Files\Java Web Start\1.3.0\lib\i18n.jar;C:\Program Files\Java Web Start\1.3.0\lib\sunrsasign.jar;C:\Program Files\Java Web Start\1.3.0\classes, java.vendor=Sun Microsystems Inc., file.separator=\, java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi, sun.io.unicode.encoding=UnicodeLittle, sun.cpu.endian=little, jnlpx.jvm="C:\Program Files\Java Web Start\1.3.0\bin\javaw.exe", user.region=US, javawebstart.version=javaws-1.0, sun.cpu.isalist=pentium i486 i386} Crypto Service Provider: ABA Info: ABA Security Provider v1.1, SHA, MD5 message Digests, and Crypto algorithms. Reading AdminServerIOR: http://bopeep.snffab.stanford.edu/AdminServerIOR AdminManagerConnection.connect(): Exception java.net.UnknownHostException: bopeep.snffab.stanford.edu AdminManagerConnection.connect(): could not bind to IOR Reading AdminServerIOR: http://bopeep.snffab.stanford.edu/AdminServerIOR AdminManagerConnection.connect(): Exception java.net.UnknownHostException: bopeep.snffab.stanford.edu AdminManagerConnection.connect(): could not bind to IOR Reading AdminServerIOR: http://bopeep.snffab.stanford.edu/AdminServerIOR AdminManagerConnection.connect(): Exception java.net.UnknownHostException: bopeep.snffab.stanford.edu AdminManagerConnection.connect(): could not bind to IOR Unable to get AdminManager IOR. From bmurray at snf.stanford.edu Mon Sep 24 22:56:16 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Mon, 24 Sep 2001 22:56:16 -0700 (PDT) Subject: remote coral test In-Reply-To: <4.2.0.58.20010924212410.00add380@pruitt.pobox.stanford.edu> Message-ID: Beth, It looks like you downloaded the development version of Coral. You don't want to run this one. (The one that says Note: Extreme Caution). Bill On Mon, 24 Sep 2001, Beth Pruitt wrote: > error:unable to get admin manager, trying again... > > just tried remote coral from home over cable modem. no luck. will try from > behind a firewall tomorrow. > > hope this helps, > Beth From yyao at intpax.com Mon Sep 24 21:01:06 2001 From: yyao at intpax.com (Yahong Yao) Date: Mon, 24 Sep 2001 23:01:06 -0500 Subject: New release of Coral ... References: <3BAFCB39.74C0BCAF@snf.stanford.edu> Message-ID: <3BB00182.E737DE77@intpax.com> Hello, I wanted to contribute to this trouble shooting. When I tried but I reached the remote carol successfully. Before, it always showed me "Unable to access equipment information". It seems the problem solved. Regards, Yahong John Shott wrote: > SNF Lab Members: > > We are pleased to announce that we have installed a new version of Coral that, > among other things, addresses some minor features that have been requested. > Those features include: > > 1. The ability to enable a piece of equipment that is enabled by someone else. > This will allow you to terminate someone else's use of a piece of equipment > (and terminate their charges for a piece of equipment) and begin to charge it > under your name. This will pop up a window that warns you "Machine x is > already enabled by y. Do you still want to enable?" ... in case, you didn't > actually want to enable that equipment. Also, when doing this, it doesn't > physically disable the hardware interlock ... that stays on all of the time. > This, we hope, will eliminate the problems of changing from one person to > another. > > 2. A warning message if you are about to disable a piece of equipment that has > been enabled by someone else. In this case you will receive a warning: > "Machine x is already enabled by y. Do you still want to disable?" While you > can still disable it ... this warns you and allows you to say no in case you > were about to accidently disable a piece of equipment. > > 3. Default equipment history includes today. Previously, equiment history > showed equipment usage through midnight of last night. Today's equipment > history had to be shown using the "Forward" menu item. We have changed this > so the default window now includes equipment usage for today. Remember, > however, that equipment that is still enabled doesn't show up in history at > all ... even if it has been enabled for a long time. Equipment usage doesn't > become history until the equipment has been disabled. > > There are a variety of "under the covers" changes that, we believe, will > contribute to the overall performance and stability of the Coral system ... > but we won't bore you with those details. > > One project, however, that is a work in progress and deserves an update is > Remote Coral access for people that are behind firewalls. Previously, people > behind firewalls would get the message: "Unable to access equipment > information" ... and then never got a functional Coral window. We have made a > number of changes to eliminate this problem ... but have not yet been able to > fully test them because we don't have an independent firewall from behind > which we can conduct our own testing. Accordingly, we are looking for a > couple of volunteers to help us to test and debug Remote Coral from behind a > firewall. If you think that you are in this group and would like to help, > please let us know. What we would like you to do is: > > 1. Check your Java Web Start installation to make sure that you are logging > errors to a file that you can find ... this is found under the "Advanced" tab > of the "Preferences" window. > > 2. Download and run the latest version of Remote Coral. > > 3. Tell us what happens on your screen. > > 4. Send us the log file that is generated. > > Note: the version that is out there may not work ... we are trying to debug > those changes to make it work. We are looking for a couple of folks who are > willing (and have the patience) to try this a two or three times as we try to > get this capability fully functional. If you want to help to debug the > "behind a firewall" problem, please send e-mail to coral at snf.stanford.edu ... > Final note: people not behind a firewall should not be affected by these > changes. > > Thanks, > > Your Coral Development Team -- Yahong Yao, Ph. D. Sr. MEMS Engineer Intpax, Inc. 6 Results Way Cupertino, CA 95014 Phone: (408) 252-6410 x. 407 Mobile:(408) 718-8831 Fax: (408) 252-6430 From bmurray at snf.stanford.edu Mon Sep 24 23:01:21 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Mon, 24 Sep 2001 23:01:21 -0700 (PDT) Subject: remote coral test (fwd) Message-ID: John, Beth got the development version. To avoid this confusion, I have copied coral-o.jar to coral-dev-o.jar so that both are now the same (the new production version). Bill ---------- Forwarded message ---------- Date: Mon, 24 Sep 2001 21:44:39 -0700 From: Beth Pruitt To: coral at snf.Stanford.EDU Subject: remote coral test error:unable to get admin manager, trying again... just tried remote coral from home over cable modem. no luck. will try from behind a firewall tomorrow. hope this helps, Beth -------------- next part -------------- Java Web Start Console, v1.0 started Mon Sep 24 21:27:20 PDT 2001 Logging to file: c:\coral_1 Java Web Start Console, v1.0 started Mon Sep 24 21:34:40 PDT 2001 Logging to file: c:\coral_1 Labnet instantiated with parameter: remote You are running the remote version of Coral. Include file: /usr/local/coral/etc/Client.conf ADMMGR_IOR_LOC: http://bopeep.snffab.stanford.edu/ {jnlpx.heapsize=NULL,NULL, java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition, jnlpx.splashport=1090, sun.boot.library.path=C:\Program Files\Java Web Start\1.3.0\bin, java.vm.version=1.3.0-C, java.vm.vendor=Sun Microsystems Inc., java.vendor.url=http://java.sun.com/, path.separator=;, java.vm.name=Java HotSpot(TM) Client VM, file.encoding.pkg=sun.io, jnlpx.home=C:\Program Files\Java Web Start, java.vm.specification.name=Java Virtual Machine Specification, user.dir=C:\, java.runtime.version=1.3.0-C, java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment, os.arch=x86, java.io.tmpdir=C:\DOCUME~1\BPRUIT~1.PRU\LOCALS~1\Temp\, line.separator= , java.vm.specification.vendor=Sun Microsystems Inc., jnlpx.remove=true, java.awt.fonts=, os.name=Windows 2000, java.library.path=C:\Program Files\Java Web Start\1.3.0\bin;.;C:\WINNT\System32;C:\WINNT;C:\Program Files\Java Web Start;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\VXIpnp\WINNT\BIN;"C:\Program Files\Java Web Start";"C:\Program Files\Java Web Start", java.specification.name=Java Platform API Specification, java.class.version=47.0, os.version=5.0, user.home=C:\Documents and Settings\bpruitt.PRUITT_LAPTOP, java.security.policy=file:C:\Program Files\Java Web Start/javaws.policy, user.timezone=America/Los_Angeles, trustProxy=true, java.awt.printerjob=sun.awt.windows.WPrinterJob, file.encoding=Cp1252, java.specification.version=1.3, java.class.path=C:\Program Files\Java Web Start\javaws.jar, user.name=bpruitt, java.vm.specification.version=1.0, java.home=C:\Program Files\Java Web Start\1.3.0, user.language=en, java.specification.vendor=Sun Microsystems Inc., awt.toolkit=sun.awt.windows.WToolkit, java.vm.info=mixed mode, java.version=1.3.0, java.ext.dirs=C:\Program Files\Java Web Start\1.3.0\lib\ext, sun.boot.class.path=C:\Program Files\Java Web Start\1.3.0\lib\rt.jar;C:\Program Files\Java Web Start\1.3.0\lib\i18n.jar;C:\Program Files\Java Web Start\1.3.0\lib\sunrsasign.jar;C:\Program Files\Java Web Start\1.3.0\classes, java.vendor=Sun Microsystems Inc., file.separator=\, java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi, sun.io.unicode.encoding=UnicodeLittle, sun.cpu.endian=little, jnlpx.jvm="C:\Program Files\Java Web Start\1.3.0\bin\javaw.exe", user.region=US, javawebstart.version=javaws-1.0, sun.cpu.isalist=pentium i486 i386} Crypto Service Provider: ABA Info: ABA Security Provider v1.1, SHA, MD5 message Digests, and Crypto algorithms. Reading AdminServerIOR: http://bopeep.snffab.stanford.edu/AdminServerIOR AdminManagerConnection.connect(): Exception java.net.UnknownHostException: bopeep.snffab.stanford.edu AdminManagerConnection.connect(): could not bind to IOR Reading AdminServerIOR: http://bopeep.snffab.stanford.edu/AdminServerIOR AdminManagerConnection.connect(): Exception java.net.UnknownHostException: bopeep.snffab.stanford.edu AdminManagerConnection.connect(): could not bind to IOR Reading AdminServerIOR: http://bopeep.snffab.stanford.edu/AdminServerIOR AdminManagerConnection.connect(): Exception java.net.UnknownHostException: bopeep.snffab.stanford.edu AdminManagerConnection.connect(): could not bind to IOR Unable to get AdminManager IOR. From bmurray at snf.stanford.edu Mon Sep 24 23:55:42 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Mon, 24 Sep 2001 23:55:42 -0700 (PDT) Subject: Java Web Start & 1.4 Message-ID: John, According to the documentation at Sun's web site, Java Web Start currently supports two different platforms (1.2 and 1.3). 1.4 will be supported when it ships. So Java Web Start won't work with any of the 1.4 betas. However, I was able to get Coral running on my machine at home using 1.3. Bill From bmurray at snf.stanford.edu Tue Sep 25 12:12:46 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Tue, 25 Sep 2001 12:12:46 -0700 (PDT) Subject: remote coral test In-Reply-To: <4.2.0.58.20010925093810.00ac3440@pruitt.pobox.stanford.edu> Message-ID: Beth, That's correct. Just turn on logging. It would really help if you could send me the log. If you have the time, I would like to spend 5 minutes on the phone with you while you try a couple of things. If that's convenient, could you call me at home this afternoon when you're ready to test a few things. My home phone number is 341-7863. Thanks, Bill On Tue, 25 Sep 2001, Beth Pruitt wrote: > hey Bill > just tried it again, and maybe something about downloading it for the 5th > time in 24 hours or the connection here or there, but it actually OPENED > over my cable modem this morning. woohoo, well done! I'll be behind a > firewall this afternoon, will try again. presumable won't need to > redownload, just turn on logging again, right? > Beth > > At 10:56 PM 9/24/2001 -0700, you wrote: > >Beth, > > > >It looks like you downloaded the development version of Coral. You don't > >want to run this one. (The one that says Note: Extreme Caution). > > > >Bill > > > >On Mon, 24 Sep 2001, Beth Pruitt wrote: > > > > > error:unable to get admin manager, trying again... > > > > > > just tried remote coral from home over cable modem. no luck. will try from > > > behind a firewall tomorrow. > > > > > > hope this helps, > > > Beth > From bmurray at snf.stanford.edu Tue Sep 25 18:32:56 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Tue, 25 Sep 2001 18:32:56 -0700 (PDT) Subject: tylannitride In-Reply-To: <3BB123E4.BD53C082@snf.stanford.edu> Message-ID: Gladys, The tylannitride has a problem reported on it so it has a yellow light. The nh3-2-f24 has a shutdown so it has a red light. However, you cannot enable the tylannitride because it requires a facility which is shutdown (nh3-2-f24). This is my understanding of how the system is supposed to work. Am I correct John? Bill On Tue, 25 Sep 2001, Gladys Sarmiento wrote: > Hi Bill. > So, tylannitride should show a "shutdown" sign ( red button) then? > It only reported a problem, so, users continued using it. > > Gladys > > > > Bill Murray wrote: > > > Gladys, > > > > The tylannitride requires the following facility which is currently > > shutdown : nh3-2-f24. I'd give the maintenance guys a call. > > > > Bill > > > > On 25 Sep 2001 gladys at snf.stanford.edu wrote: > > > > > > > > Hi computer guys. > > > Can not enable it, there's this message "supporting equipment is down". > > > The rest of the equip is ok to enable. > > > > > > Gladys > > > > From gladys at snf.stanford.edu Wed Sep 26 07:52:54 2001 From: gladys at snf.stanford.edu (Gladys Sarmiento) Date: Wed, 26 Sep 2001 07:52:54 -0700 Subject: tylannitride References: Message-ID: <3BB1EBC6.8992162@snf.stanford.edu> Hi Bill. There were two runs that went through and I checked with the users and the gas flows were ok. Just wondering now if that nh3-2-f24 is not the one connected to the nitride tube, I think there's two same gas lines. Or, there might be enough gases left in the line for the two runs. Gladys p.s. these tylans don't need to be enabled to run Bill Murray wrote: > Gladys, > > The tylannitride has a problem reported on it so it has a yellow light. > The nh3-2-f24 has a shutdown so it has a red light. However, you > cannot enable the tylannitride because it requires a facility which is > shutdown (nh3-2-f24). This is my understanding of how the system is > supposed to work. Am I correct John? > > Bill > > On Tue, 25 Sep 2001, Gladys Sarmiento wrote: > > > Hi Bill. > > So, tylannitride should show a "shutdown" sign ( red button) then? > > It only reported a problem, so, users continued using it. > > > > Gladys > > > > > > > > Bill Murray wrote: > > > > > Gladys, > > > > > > The tylannitride requires the following facility which is currently > > > shutdown : nh3-2-f24. I'd give the maintenance guys a call. > > > > > > Bill > > > > > > On 25 Sep 2001 gladys at snf.stanford.edu wrote: > > > > > > > > > > > Hi computer guys. > > > > Can not enable it, there's this message "supporting equipment is down". > > > > The rest of the equip is ok to enable. > > > > > > > > Gladys > > > > > > From shott at snf.stanford.edu Wed Sep 26 09:19:22 2001 From: shott at snf.stanford.edu (John Shott) Date: Wed, 26 Sep 2001 09:19:22 -0700 Subject: tylannitride References: Message-ID: <3BB2000A.AE15C164@snf.stanford.edu> Bill, Gladys, et at: Yes, becuase ammonia is not available, tylannitride cannot be enabled. Thanks, John From bmurray at snf.stanford.edu Fri Sep 28 02:53:09 2001 From: bmurray at snf.stanford.edu (Bill Murray) Date: Fri, 28 Sep 2001 02:53:09 -0700 (PDT) Subject: Event Service Modifications Message-ID: John, I added the logging we discussed. While reviewing the latest logs and adding the logging, I found a problem which I have fixed (I hope). We should know by morning. The logs will get long because subscriptions, unlike subscription removals, are done one event at a time. The logs should be helpful. These changes kept me up a little late. I'll try to get in the office at a reasonable hour. Good Night, Bill