You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(1) |
Mar
(6) |
Apr
(9) |
May
(28) |
Jun
(19) |
Jul
(8) |
Aug
(9) |
Sep
(42) |
Oct
(43) |
Nov
(59) |
Dec
(50) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(67) |
Feb
(47) |
Mar
(55) |
Apr
(11) |
May
(23) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Andrew H. <hel...@cs...> - 2009-02-19 23:18:30
|
No, it was not successful in removing the worm, though it may not be as
much of a problem for external computers as long as the firewall is on.
We can still try this approach:
Install a second copy of windows onto the C drive, then run the
virus checker again on the original windows directory. From there
it should be capable of removing the worm's files, but might still
leave some registry keys lying around in the original windows
directory.
... if that fails, then it is time to reinstall Windows XP, the Affy
software, and all of the other software that is needed on that machine.
That will probably be a major undertaking... :P If this is necessary,
then we need to ensure that the firewall is enabled and configured
sufficiently well that no one wants to turn it off. Also, we'll need to
ensure that the virus scanner scans all removable devices that get plugged
in.
----
Andy
On Thu, 19 Feb 2009, Bret Harry wrote:
> Hey Andy,
>
> Was the virus-checker successful, should I order a glue gun?
>
> -bret
>
> On Mon, Feb 16, 2009 at 08:03:02PM -0800, Andrew Helsley wrote:
>> Hi all,
>>
>> If you have ever plugged your removable storage device into the
>> HG5605Affy-SN01 computer (Windows XP, hooked up to the Affy scanner on 5th
>> floor Gonda at the end of the building), it may be now be infected with
>> the W32/SillyFDC-N worm:
>>
>> http://www.sophos.com/security/analyses/viruses-and-spyware/w32sillyfdcn.html
>>
>> Click "More Information" to find a list of files and registry keys that
>> can indicate the presence of the worm. FYI: Where the website writes
>> <Windows> and <System>, this usually means C:\WINDOWS\ and
>> C:\WINDOWS\system\ respectively.
>>
>> This appears to be a rather nasty worm to eradicate. Sophos has not been
>> able to successfully remove it thus far, so a full system re-install may
>> be required. This worm spreads by infecting removable drives with an
>> "autorun.inf" file. Consequently, any windows machines that you may have
>> plugged your device into (either prior to or after connecting to the
>> machine mentioned above) are also potentially infected and should be
>> checked.
>>
>> I am quite certain that this virus was installed onto this computer as a
>> result of plugging in a USB flash device, and/or made its way off of the
>> computer via a USB flash device. Virus scan logs indicate its presence on
>> two drives lettered "H" and "I" which are not currently plugged into the
>> machine and are definitely not the usual CD/DVD drives (since those are
>> still plugged in and labeled "F" and "G").
>>
>> Please run a virus checker on your removable drives and any computers they
>> may have come into contact with as soon as possible. You should probably
>> log in to a non-privileged account before plugging in the removable device
>> for checking it, as you may infect a machine in the process of plugging in
>> the device (isn't autorun convenient and wonderful?). You might be able
>> to get a Linux/Mac person to mount the device and look for any
>> "Autorun.inf" files at the root of the device. It should not affect these
>> machines since they do not automatically execute such files. Except for
>> special circumstances, such a file should not exist on your flash drive.
>> If found, the file could probably be deleted on the Linux box/Mac prior to
>> checking it for infection on the PC.
>>
>> Unfortunately, I do not have any information as to when this infection
>> started and the symptoms of infection do not necessarily arise soon after
>> infection, so please be diligent about checking the machines and USB
>> storage devices that you have control over. If you cannot check your
>> device right now, please consider using it under quarantine (avoid
>> connecting to file shares, creating CDs/DVDs, or working with known-clean
>> USB flash drives) until such time as you are able to check/repair it.
>> This may mean unplugging from the network until it can be checked.
>>
>> If possible, I would like to propose that people avoid plugging personal
>> removable devices into computers that are hooked up to common lab
>> infrastructure such as this, particularly if they regularly use the
>> storage device with Microsoft Windows. Besides the fact that infection
>> may necessitate a re-install of the operating system and specialized
>> applications for driving the hardware, such computers serve as places
>> where viruses can propagate very quickly to other lab members' machines.
>>
>> --------
>> regards,
>> Andy
>>
>> Andrew Helsley
>> Programmer/Analyst
>> Computing Technologies Research Lab (CTRL)
>> David Geffen School of Medicine at UCLA
>> Email: hel...@cs...
>> Office: 1 (310) 206-6556 (shared)
>> Phone: 1 (213) 591-0420 (cell phone)
>> AIM: morgaladh
>> Jabber: andrew.helsley at gmail dot com
>>
>>
>> ------------------------------------------------------------------------------
>> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
>> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
>> -Strategies to boost innovation and cut costs with open source participation
>> -Receive a $600 discount off the registration fee with the source code: SFAD
>> http://p.sf.net/sfu/XcvMzF8H
>> _______________________________________________
>> Nelsonlab-sysops mailing list
>> Nel...@li...
>> https://lists.sourceforge.net/lists/listinfo/nelsonlab-sysops
>
--------
regards,
Andy
Andrew Helsley
Programmer/Analyst
Computing Technologies Research Lab (CTRL)
David Geffen School of Medicine at UCLA
Email: hel...@cs...
Office: 1 (310) 206-6556 (shared)
Phone: 1 (213) 591-0420 (cell phone)
AIM: morgaladh
Jabber: andrew.helsley at gmail dot com
WWW: http://www.cs.ucr.edu/~helsleya
|
|
From: Bret H. <ja...@ga...> - 2009-02-19 20:11:50
|
Hey Andy, Was the virus-checker successful, should I order a glue gun? -bret On Mon, Feb 16, 2009 at 08:03:02PM -0800, Andrew Helsley wrote: > Hi all, > > If you have ever plugged your removable storage device into the > HG5605Affy-SN01 computer (Windows XP, hooked up to the Affy scanner on 5th > floor Gonda at the end of the building), it may be now be infected with > the W32/SillyFDC-N worm: > > http://www.sophos.com/security/analyses/viruses-and-spyware/w32sillyfdcn.html > > Click "More Information" to find a list of files and registry keys that > can indicate the presence of the worm. FYI: Where the website writes > <Windows> and <System>, this usually means C:\WINDOWS\ and > C:\WINDOWS\system\ respectively. > > This appears to be a rather nasty worm to eradicate. Sophos has not been > able to successfully remove it thus far, so a full system re-install may > be required. This worm spreads by infecting removable drives with an > "autorun.inf" file. Consequently, any windows machines that you may have > plugged your device into (either prior to or after connecting to the > machine mentioned above) are also potentially infected and should be > checked. > > I am quite certain that this virus was installed onto this computer as a > result of plugging in a USB flash device, and/or made its way off of the > computer via a USB flash device. Virus scan logs indicate its presence on > two drives lettered "H" and "I" which are not currently plugged into the > machine and are definitely not the usual CD/DVD drives (since those are > still plugged in and labeled "F" and "G"). > > Please run a virus checker on your removable drives and any computers they > may have come into contact with as soon as possible. You should probably > log in to a non-privileged account before plugging in the removable device > for checking it, as you may infect a machine in the process of plugging in > the device (isn't autorun convenient and wonderful?). You might be able > to get a Linux/Mac person to mount the device and look for any > "Autorun.inf" files at the root of the device. It should not affect these > machines since they do not automatically execute such files. Except for > special circumstances, such a file should not exist on your flash drive. > If found, the file could probably be deleted on the Linux box/Mac prior to > checking it for infection on the PC. > > Unfortunately, I do not have any information as to when this infection > started and the symptoms of infection do not necessarily arise soon after > infection, so please be diligent about checking the machines and USB > storage devices that you have control over. If you cannot check your > device right now, please consider using it under quarantine (avoid > connecting to file shares, creating CDs/DVDs, or working with known-clean > USB flash drives) until such time as you are able to check/repair it. > This may mean unplugging from the network until it can be checked. > > If possible, I would like to propose that people avoid plugging personal > removable devices into computers that are hooked up to common lab > infrastructure such as this, particularly if they regularly use the > storage device with Microsoft Windows. Besides the fact that infection > may necessitate a re-install of the operating system and specialized > applications for driving the hardware, such computers serve as places > where viruses can propagate very quickly to other lab members' machines. > > -------- > regards, > Andy > > Andrew Helsley > Programmer/Analyst > Computing Technologies Research Lab (CTRL) > David Geffen School of Medicine at UCLA > Email: hel...@cs... > Office: 1 (310) 206-6556 (shared) > Phone: 1 (213) 591-0420 (cell phone) > AIM: morgaladh > Jabber: andrew.helsley at gmail dot com > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Nelsonlab-sysops mailing list > Nel...@li... > https://lists.sourceforge.net/lists/listinfo/nelsonlab-sysops |
|
From: Andrew H. <hel...@cs...> - 2009-02-17 04:23:48
|
Hi all, If you have ever plugged your removable storage device into the HG5605Affy-SN01 computer (Windows XP, hooked up to the Affy scanner on 5th floor Gonda at the end of the building), it may be now be infected with the W32/SillyFDC-N worm: http://www.sophos.com/security/analyses/viruses-and-spyware/w32sillyfdcn.html Click "More Information" to find a list of files and registry keys that can indicate the presence of the worm. FYI: Where the website writes <Windows> and <System>, this usually means C:\WINDOWS\ and C:\WINDOWS\system\ respectively. This appears to be a rather nasty worm to eradicate. Sophos has not been able to successfully remove it thus far, so a full system re-install may be required. This worm spreads by infecting removable drives with an "autorun.inf" file. Consequently, any windows machines that you may have plugged your device into (either prior to or after connecting to the machine mentioned above) are also potentially infected and should be checked. I am quite certain that this virus was installed onto this computer as a result of plugging in a USB flash device, and/or made its way off of the computer via a USB flash device. Virus scan logs indicate its presence on two drives lettered "H" and "I" which are not currently plugged into the machine and are definitely not the usual CD/DVD drives (since those are still plugged in and labeled "F" and "G"). Please run a virus checker on your removable drives and any computers they may have come into contact with as soon as possible. You should probably log in to a non-privileged account before plugging in the removable device for checking it, as you may infect a machine in the process of plugging in the device (isn't autorun convenient and wonderful?). You might be able to get a Linux/Mac person to mount the device and look for any "Autorun.inf" files at the root of the device. It should not affect these machines since they do not automatically execute such files. Except for special circumstances, such a file should not exist on your flash drive. If found, the file could probably be deleted on the Linux box/Mac prior to checking it for infection on the PC. Unfortunately, I do not have any information as to when this infection started and the symptoms of infection do not necessarily arise soon after infection, so please be diligent about checking the machines and USB storage devices that you have control over. If you cannot check your device right now, please consider using it under quarantine (avoid connecting to file shares, creating CDs/DVDs, or working with known-clean USB flash drives) until such time as you are able to check/repair it. This may mean unplugging from the network until it can be checked. If possible, I would like to propose that people avoid plugging personal removable devices into computers that are hooked up to common lab infrastructure such as this, particularly if they regularly use the storage device with Microsoft Windows. Besides the fact that infection may necessitate a re-install of the operating system and specialized applications for driving the hardware, such computers serve as places where viruses can propagate very quickly to other lab members' machines. -------- regards, Andy Andrew Helsley Programmer/Analyst Computing Technologies Research Lab (CTRL) David Geffen School of Medicine at UCLA Email: hel...@cs... Office: 1 (310) 206-6556 (shared) Phone: 1 (213) 591-0420 (cell phone) AIM: morgaladh Jabber: andrew.helsley at gmail dot com |
|
From: Bret H. <ja...@ga...> - 2008-08-17 04:49:52
|
This is a test. -bret |
|
From: Matthew S. M. <mm...@co...> - 2008-08-16 04:14:13
|
This is only a test, there is no need to respond to this message. -- Matthew S. Moore <mm...@co...> Systems Programmer/Analyst, SourceForge.net *************************************************************************** This email may contain confidential and privileged material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. *************************************************************************** |
|
From: Allen D. <all...@uc...> - 2006-05-24 18:04:05
|
please fix. it is sshable, but it lost its NFS mount from neuron, along with the gridengine processes. -Allen |
|
From: Allen D. <all...@uc...> - 2006-05-24 06:01:59
|
It's been doing that for a long time. Needs to be updated anyway. -Allen On 5/23/06, Brian O'Connor <boc...@uc...> wrote: > > Hey, > > FYI: It looks like there is an RPM in the repo that's corrupted: > > >>>>>>>>>> > biopackages/$mode/fedora/$version/$arch ; done ; done ; done' | bash > error: rpmts_HdrFromFdno: MD5 digest: BAD > Expected(e08b146c9ed71b35706fa8434a059488) != > (f0ebfcf4a23cf45b02d5d31fa0517391) > > Error opening package - obo-extra-1.0.0-6.20051003.bp.fc2.noarch.rpm > error: rpmts_HdrFromFdno: MD5 digest: BAD > Expected(2ff2776d0255f20f692862ef2ff194cd) != > (79e67d516bce107fabbd4503169adb4a) > > Error opening package - obo-core-1.0.0-8.20051004.bp.fc2.noarch.rpm > Old data directory exists, please remove: .olddata > <<<<<<<<<< > > --Brian > > > ------------------------------------------------------- > All the advantages of Linux Managed Hosting--Without the Cost and Risk! > Fully trained technicians. The highest number of Red Hat certifications in > the hosting industry. Fanatical Support. Click to learn more > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 > _______________________________________________ > Nelsonlab-admin mailing list > Nel...@li... > https://lists.sourceforge.net/lists/listinfo/nelsonlab-admin > |
|
From: Allen D. <all...@uc...> - 2006-05-24 03:43:46
|
I would like to schedule 2 days partial downtime beginning Friday afternoon for the celsius database on axis, and the associated webservice at http://das.biopackages.net. The reason for this is that there has been a large increase, greater than 30%, in the size of the database tables containing the normalized data, leading to increasingly long query times. To keep query times low, we need to physically reorder, or "cluster", the contents of the tables. There are a total of 8 tables needing maintenance, and each will be taken offline for ~10 hours for the larger tables, clustered, and brought back online. If this collides with anyone's plans to access the database, or any other scheduled outages please let me know so I can reschedule. -Allen |
|
From: Brian O'C. <boc...@uc...> - 2006-05-23 23:07:40
|
Hey, FYI: It looks like there is an RPM in the repo that's corrupted: >>>>>>>>>> biopackages/$mode/fedora/$version/$arch ; done ; done ; done' | bash error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(e08b146c9ed71b35706fa8434a059488) != (f0ebfcf4a23cf45b02d5d31fa0517391) Error opening package - obo-extra-1.0.0-6.20051003.bp.fc2.noarch.rpm error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(2ff2776d0255f20f692862ef2ff194cd) != (79e67d516bce107fabbd4503169adb4a) Error opening package - obo-core-1.0.0-8.20051004.bp.fc2.noarch.rpm Old data directory exists, please remove: .olddata <<<<<<<<<< --Brian |
|
From: Brian O'C. <boc...@uc...> - 2006-05-23 00:37:01
|
Hi Andy & Patrick,
I have a few RPMs that need to be installed on the cluster nodes. The
RPM install process works fine on neuron. However, when I try the
following:
>>>>>>>>>>>
sudo shmux -c 'yum update; yum -y install perl-Class-DBI-Pg
perl-Class-DBI-Pager perl-Class-Accessor-Chained
perl-Class-DBI-Plugin-Type perl-DBIx-ContextualFetch
perl-Graph-Writer-GraphViz perl-IO-All perl-XML-LibXML' compute-0-00
compute-0-01 compute-0-02 compute-0-03 compute-0-04 compute-0-05
compute-0-06 compute-0-07 compute-0-08 compute-0-09 compute-0-10
compute-0-11 compute-0-12 compute-0-13 compute-0-14
<<<<<<<<<<<
I get the following error:
>>>>>>>>>>>
compute-0-00: Gathering header information file(s) from server(s)
compute-0-00: Server: BioPackages (Extra) for Fedora Core 2 - noarch
compute-0-00: Server: BioPackages (Extra) for Fedora Core 2 - noarch
compute-0-00: Server: BioPackages (Stable) for Fedora Core 2 - i386
compute-0-00: Server: BioPackages (Stable) for Fedora Core 2 - noarch
compute-0-00: Server: BioPackages (Testing) for Fedora Core 2 - i386
compute-0-00: Server: BioPackages (Testing) for Fedora Core 2 - noarch
compute-0-00: Server: Fedora Linux 2 - i386 - core
compute-0-00: Server: Fedora Linux 2 - i386 - updates
compute-0-00: Finding updated packages
compute-0-00: Downloading needed headers
compute-0-00: Resolving dependencies
compute-0-00: .Package perl-Log-Dispatch needs perl(Apache::Log), this
is not available.
compute-0-00! Cannot find a package matching perl-Graph-Writer-GraphViz
compute-0-00! Cannot find a package matching perl-IO-All
shmux! Waiting for existing children to abort..
...
<<<<<<<<<<<
Here's the output on neuron:
>>>>>>>>>>>
sudo yum -y install perl-Class-DBI-Pg perl-Class-DBI-Pager
perl-Class-Accessor-Chained perl-Class-DBI-Plugin-Type
perl-DBIx-ContextualFetch perl-Graph-Writer-GraphViz perl-IO-All
perl-XML-LibXML
Password:
Gathering header information file(s) from server(s)
Server: BioPackages (Extra) for Fedora Core 2 - noarch
Server: BioPackages (Extra) for Fedora Core 2 - noarch
Server: BioPackages (Stable) for Fedora Core 2 - i386
Server: BioPackages (Stable) for Fedora Core 2 - noarch
Server: BioPackages (Testing) for Fedora Core 2 - i386
Server: BioPackages (Testing) for Fedora Core 2 - noarch
Server: Fedora Linux 2 - i386 - core
Server: Dag RPM Repository for Fedora Core 2
Server: Fedora Linux 2 - i386 - updates
Finding updated packages
Downloading needed headers
perl-Class-DBI-Pg is installed and is the latest version.
perl-Class-DBI-Pager is installed and is the latest version.
perl-Class-Accessor-Chained is installed and is the latest version.
perl-Class-DBI-Plugin-Type is installed and is the latest version.
perl-DBIx-ContextualFetch is installed and is the latest version.
perl-Graph-Writer-GraphViz is installed and is the latest version.
perl-IO-All is installed and is the latest version.
perl-XML-LibXML is installed and is the latest version.
No actions to take
<<<<<<<<<<<
So there seems to be some problem with the yum setup on the compute
nodes, the DAG RPM repo is missing on the cluter nodes. I really need
to get these packages installed so I appreciate any help you can give.
Thanks
--Brian
|
|
From: Allen D. <all...@uc...> - 2006-05-22 19:38:01
|
Hi, I thought it would be useful to have a list of lab IM accounts, so I started adding entries to the table here: http://genomics.ctrl.ucla.edu/wiki/pmwiki.php?n=Main.LabDirectory Please update your details. -Allen |
|
From: Allen D. <all...@uc...> - 2006-05-22 19:17:50
|
status au, please fix. -allen |
|
From: Allen D. <all...@uc...> - 2006-05-17 21:36:32
|
Thanks Jared. It looks like when I moved the jobs it restarted them, so if you were appending to file you may want to kill/cleanup/resubmit. They have now been running for 12 minutes. All but one were restarted, you can see which by the submission time (or the "R" resubmit flag in the job state). -Allen On 5/17/06, Jared Fox <jar...@uc...> wrote: > > Will do. I don't think my jobs were causing trouble, but I'll switch to > the new volume for future jobs. My jobs were reading into memory 1 or 2 > files at the beginning and then not touching the disk for hours while the > data was processed and then writing output to file. I was only running 2 > jobs at a time as well except for last night. > > Thanks for the info and for moving my jobs to the other queue so that > Brian could use the bigmem queue. > > ----- Original Message ----- > *From:* Allen Day <all...@uc...> > *To:* Jared Fox <jar...@uc...> ; Brian O'Connor <boc...@uc...> ; > nel...@li... ; > nel...@li... > *Sent:* Wednesday, May 17, 2006 2:09 PM > *Subject:* cluster tips > > Hi Jared, > > When you submit jobs, please specify the queue you with them to go to. > Now that we have multiple queues, the default behavior of the qsub utility > is to first put jobs to all.q, then to gb4.q, then to celsius.q, faulting > down the chain if a queue is currently full. We're working on making all > jobs go to only all.q unless otherwise requested, but until then if you do > not need the bigmem queue, please explicity request all.q with the "-q > all.q" option to qsub. > > Also, it appears that the I/O your jobs were doing over the last couple of > days were putting a heavy load on the xsan NFS processes. It appeared that > you were touching a large number of small files. Please copy your files > over to nucleus:/clustertmp/jaredfox that are going to be used from the > compute nodes. This volume is NFS exported to all the compute nodes. > > Thanks. > > -Allen > > |
|
From: Jared F. <jar...@uc...> - 2006-05-17 21:33:23
|
Will do. I don't think my jobs were causing trouble, but I'll switch to the new volume for future jobs. My jobs were reading into memory 1 or 2 files at the beginning and then not touching the disk for hours while the data was processed and then writing output to file. I was only running 2 jobs at a time as well except for last night. Thanks for the info and for moving my jobs to the other queue so that Brian could use the bigmem queue. ----- Original Message ----- From: Allen Day To: Jared Fox ; Brian O'Connor ; nel...@li... ; nel...@li... Sent: Wednesday, May 17, 2006 2:09 PM Subject: cluster tips Hi Jared, When you submit jobs, please specify the queue you with them to go to. Now that we have multiple queues, the default behavior of the qsub utility is to first put jobs to all.q, then to gb4.q, then to celsius.q, faulting down the chain if a queue is currently full. We're working on making all jobs go to only all.q unless otherwise requested, but until then if you do not need the bigmem queue, please explicity request all.q with the "-q all.q" option to qsub. Also, it appears that the I/O your jobs were doing over the last couple of days were putting a heavy load on the xsan NFS processes. It appeared that you were touching a large number of small files. Please copy your files over to nucleus:/clustertmp/jaredfox that are going to be used from the compute nodes. This volume is NFS exported to all the compute nodes. Thanks. -Allen |
|
From: Allen D. <all...@uc...> - 2006-05-17 21:10:06
|
Hi Jared, When you submit jobs, please specify the queue you with them to go to. Now that we have multiple queues, the default behavior of the qsub utility is to first put jobs to all.q, then to gb4.q, then to celsius.q, faulting down the chain if a queue is currently full. We're working on making all jobs go to only all.q unless otherwise requested, but until then if you do not need the bigmem queue, please explicity request all.q with the "-q all.q" option to qsub. Also, it appears that the I/O your jobs were doing over the last couple of days were putting a heavy load on the xsan NFS processes. It appeared that you were touching a large number of small files. Please copy your files over to nucleus:/clustertmp/jaredfox that are going to be used from the compute nodes. This volume is NFS exported to all the compute nodes. Thanks. -Allen |
|
From: Allen D. <all...@uc...> - 2006-05-16 20:39:32
|
Is anyone doing a lot of I/O on the xsan since last night or this morning? There is a heavy load on nucleus and it's making several other systems sluggish. Please contact me ASAP if you think it might be you. -Allen |
|
From: Andrew H. <hel...@cs...> - 2006-05-12 16:23:04
|
File services should be available now. On Fri, 12 May 2006, Andrew Helsley wrote: > > The file server is going down for maintenance now. See below for details. > > > On Wed, 10 May 2006, Andrew Helsley wrote: > >> Greetings all, >> >> The problems with the file server have so far not responded to our efforts >> to fix the problem by replacing and reconfiguring the memory hardware. >> Small numbers of corrected-errors continue to be reported by the ECC >> circuitry. Through our contact with the hardware vendor we have been given >> additional replacements for memory, a processor, and main circuit board and >> plan on installing these on Friday, May 12th during the hour from 8 to 9am. >> >> Again, the expected down-time will be from 8am to 9am, affecting home >> directories, vol07, other more specialized file shares, and work done >> through >> the web-interface found at http://microarray.genetics.ucla.edu. >> >> An email will be sent out immediately prior to the down-time and another >> once the system has been returned to service. Feel free to contact me if >> you have any questions, concerns, or suggestions. >> >> -------- >> regards, >> Andy >> >> Andrew Helsley >> Programmer/Analyst >> Computing Technologies Research Lab (CTRL) >> David Geffen School of Medicine at UCLA >> Email: hel...@cs... >> Office: (310) 206-6556 (shared) >> > |
|
From: Andrew H. <hel...@cs...> - 2006-05-12 15:11:03
|
The file server is going down for maintenance now. See below for details. On Wed, 10 May 2006, Andrew Helsley wrote: > Greetings all, > > The problems with the file server have so far not responded to our efforts to > fix the problem by replacing and reconfiguring the memory hardware. Small > numbers of corrected-errors continue to be reported by the ECC circuitry. > Through our contact with the hardware vendor we have been given additional > replacements for memory, a processor, and main circuit board and plan on > installing these on Friday, May 12th during the hour from 8 to 9am. > > Again, the expected down-time will be from 8am to 9am, affecting home > directories, vol07, other more specialized file shares, and work done through > the web-interface found at http://microarray.genetics.ucla.edu. > > An email will be sent out immediately prior to the down-time and another once > the system has been returned to service. Feel free to contact me if you have > any questions, concerns, or suggestions. > > -------- > regards, > Andy > > Andrew Helsley > Programmer/Analyst > Computing Technologies Research Lab (CTRL) > David Geffen School of Medicine at UCLA > Email: hel...@cs... > Office: (310) 206-6556 (shared) > |
|
From: Allen D. <all...@uc...> - 2006-05-12 00:33:52
|
This ought to be really good. Anyone interested in carpooling over to Ticketmaster for the evening? -Allen ---------- Forwarded message ---------- From: Todd Cranston-Cuebas <Tod...@ti...> Date: May 11, 2006 3:11 PM Subject: [LA.pm] LA.pm Tech Talk - Tuesday, April 23th 2006 - PPI: Transforming Pe rl To: "Los...@pm..." <Los...@pm...> *Announcing this month's LA.pm Tech Talk!* When: Tuesday, May 23, 2006, 7-9 p.m. Where: Ticketmaster's movie theater 8800 W. Sunset Blvd West Hollywood, CA 90069 *PPI: Transforming Perl* Guest Speaker: Jeffrey Goff *Short description...* Parsing Perl in a standalone module allows automated code visualization, refactoring and much more. This month's LA.pm Tech Talk will explore new ways to display and refactor perl code through the PPI module suite. *Preview of next month...* We're going to have a guest speaker coming all the way from Australia on his way to YAPC in Chicago. In an effort to avoid potential LA.pm member conflicts for those attending YAPC and also so we can have this guest speaker, I've moved next month's meeting to Thursday, June 22nd. Mark your calendars! Please click on the supplied link below to let us know if you're coming. As far as I know, you will _not_ be required to register with Evite if this is a concern. This will help me to get a better idea of the head count so PLEASE take the time to RVSP. The Evite invitation also has more information regarding parking, etc. http://www.evite.com/app/publicUrl/tc...@ti.../lapmtech052306 Thank you! Todd Cranston-Cuebas _______________________________________________ Losangeles-pm mailing list Los...@pm... http://mail.pm.org/mailman/listinfo/losangeles-pm |
|
From: Matthew O. <mo...@uc...> - 2006-05-11 07:24:47
|
-----Original Message----- From: Silva, Alcino [mailto:Si...@me...] Sent: Wednesday, May 10, 2006 7:58 PM To: 'si...@uc...' Subject: UCLA learning and memory meeting on May 31, 2006 Dear Colleagues, David Glanzman, Michael Fanselow and I would like to invite you, and your colleagues to the May 31, 2006 UCLA Learning and Memory Symposium, a yearly meeting for Southern California labs interested in plasticity and memory. Registration is free but required. You can register by simply responding to this e-mail with your name, position and affiliation. For detailed information about program, location, directions, etc, go to http://www.silvalab.com/uclasymposium.htm Place: Neuroscience Research Building Auditorium at UCLA Medical School Speakers: Aaron Blaisdell, Ph.D., UCLA John Guzowski, Ph.D., UCI Kelsey Martin, M.D., Ph.D., UCLA Ken Kosik, M.D., UCSB Larry Squire, Ph.D., VA Medical Center, San Diego Marcelo Wood, Ph.D., UCI Mark Frye, Ph.D., UCLA Mark Tuszynski, M.D., Ph.D., UCSD Paul Patterson, Ph.D., California Institute of Technology, Pasadena Robert Bjork, Ph.D., UCLA Russ Poldrack, Ph.D., UCLA Tom Otis, Ph.D., UCLA Please, forward this e-mail to people in your lab and to other colleagues working on plasticity and memory. We hope to see you at UCLA in May! Cheers, Alcino Alcino J. Silva Professor Departments of Neurobiology, Psychiatry and Biobehavioral Sciences, Psychology and Brain Research Institute. 695 Young Drive South, Room 2357 Box 951761, UCLA Los Angeles, California 90095-1761 si...@me... http://www.silvalab.org/ Direct Ph 310 794 6345 Lab Ph 310 794 6609 Lab Fax 310 794 7088 ---------------------------------------------------------- IMPORTANT WARNING: This email (and any attachments) is only intended for the use of the person or entity to which it is addressed, and may contain information that is privileged and confidential. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. Unauthorized redisclosure or failure to maintain confidentiality may subject you to federal and state penalties. If you are not the intended recipient, please immediately notify us by return email, and delete this message from your computer. ---------------------------------------------------------- |
|
From: Andrew H. <hel...@cs...> - 2006-05-11 02:38:22
|
Greetings all, The problems with the file server have so far not responded to our efforts to fix the problem by replacing and reconfiguring the memory hardware. Small numbers of corrected-errors continue to be reported by the ECC circuitry. Through our contact with the hardware vendor we have been given additional replacements for memory, a processor, and main circuit board and plan on installing these on Friday, May 12th during the hour from 8 to 9am. Again, the expected down-time will be from 8am to 9am, affecting home directories, vol07, other more specialized file shares, and work done through the web-interface found at http://microarray.genetics.ucla.edu. An email will be sent out immediately prior to the down-time and another once the system has been returned to service. Feel free to contact me if you have any questions, concerns, or suggestions. -------- regards, Andy Andrew Helsley Programmer/Analyst Computing Technologies Research Lab (CTRL) David Geffen School of Medicine at UCLA Email: hel...@cs... Office: (310) 206-6556 (shared) |
|
From: Andrew H. <hel...@cs...> - 2006-05-09 01:35:41
|
The file server is back online now. On Mon, 8 May 2006, Andrew Helsley wrote: > Greetings all, > > Although the RAM on our main file server, nucleus, was replaced last friday, > it still seems to be warning us of errors corrected by the ECC circuitry. We > hope to address this problem once and for all by shutting down file services > again at 6pm tonight to change the RAM configuration. > > The file server will be down for the next half-hour. > > As a result, home directories, vol07, and other more specialized file shares > will be unavailable during this time. Please note that this will also affect > work done through the web-interface found at > http://microarray.genetics.ucla.edu. > > An email will be sent out once the system has been returned to service. Feel > free to contact me if you have any questions or concerns. > > -------- > regards, > Andy > > Andrew Helsley > Programmer/Analyst > Computing Technologies Research Lab (CTRL) > David Geffen School of Medicine at UCLA > Email: hel...@cs... > Office: (310) 206-6556 (shared) > |
|
From: Andrew H. <hel...@cs...> - 2006-05-09 01:01:13
|
Greetings all, Although the RAM on our main file server, nucleus, was replaced last friday, it still seems to be warning us of errors corrected by the ECC circuitry. We hope to address this problem once and for all by shutting down file services again at 6pm tonight to change the RAM configuration. The file server will be down for the next half-hour. As a result, home directories, vol07, and other more specialized file shares will be unavailable during this time. Please note that this will also affect work done through the web-interface found at http://microarray.genetics.ucla.edu. An email will be sent out once the system has been returned to service. Feel free to contact me if you have any questions or concerns. -------- regards, Andy Andrew Helsley Programmer/Analyst Computing Technologies Research Lab (CTRL) David Geffen School of Medicine at UCLA Email: hel...@cs... Office: (310) 206-6556 (shared) Phone: (213) 591-0420 (cell phone) |
|
From: Andrew H. <hel...@cs...> - 2006-05-08 19:23:39
|
Greetings all, Although the RAM on our main file server, nucleus, was replaced last friday, it still seems to be warning us of errors corrected by the ECC circuitry. We hope to address this problem once and for all by shutting down file services again at 6pm tonight to change the RAM configuration. The expected down-time will be from 6pm to 6:30pm. As a result, home directories, vol07, and other more specialized file shares will be unavailable during this time. Please note that this will also affect work done through the web-interface found at http://microarray.genetics.ucla.edu. An email will be sent out immediately prior to the down-time and another once the system has been returned to service. Feel free to contact me if you have any questions or concerns. -------- regards, Andy Andrew Helsley Programmer/Analyst Computing Technologies Research Lab (CTRL) David Geffen School of Medicine at UCLA Email: hel...@cs... Office: (310) 206-6556 (shared) |
|
From: Andrew H. <hel...@cs...> - 2006-05-06 00:22:18
|
The file server should be back up and running. ---- Andy On Fri, 5 May 2006, Andrew Helsley wrote: > Greetings all, > > The RAM on our main file server, nucleus, is increasingly showing signs of > wear. Fortunately, the system has ECC RAM (Error-Correcting RAM) and the > warnings we have received so far have been recoverable and thus far have not > affected system operation. > > We are currently replacing the chip. As a result home directories, vol07, > and other more specialized file shares are unavailable. Please note that > this will also affect work done through the web-interface found at > http://microarray.genetics.ucla.edu. > > An email will be sent out once the system has been returned to service. Feel > free to contact me if you have any questions or concerns. > > -------- > regards, > Andy > > Andrew Helsley > Programmer/Analyst > Computing Technologies Research Lab (CTRL) > David Geffen School of Medicine at UCLA > Email: hel...@cs... > Office: (310) 206-6556 (shared) > Mobile: (213) 591-0420 |