[Bigjob-users] [saga-devel] cyder.cct.lsu.edu

[azebrowski at cct.lsu.edu]

Hi all,

I'm not sure what it could be either -- the Cactus simulations I run  
take up about 8GiB of RAM, and I only run one at a time.  I wonder if  
this is somehow related to the random hangs that happen with Cyder,  
which can cause 5-10 minute delays in writing to/from disk.

-Ashley Z

Quoting Ole Weidner <oweidner at cct.lsu.edu>:

> No, unfortunately, not.
>
> Ole.
>
> On Jan 11, 2012, at 10:59 AM, Joohyun Kim wrote:
>
>> Ole,
>>
>> Do you have any sense about what programs could drive that situation? It
>> is worth knowing what caused such a situation to avoid the same problem.
>>
>> JK
>>
>>
>>
>>
>> On 1/10/12 9:10 PM, "Ole Weidner" <oweidner at cct.lsu.edu> wrote:
>>
>>> Hi all,
>>>
>>> I finally got access to the server room and the rack were we keep
>>> cyder.cct.lsu.edu. After connecting monitor and keyboard, it turned out
>>> that the machine had completely run out of memory and the kernel finally
>>> barfed and halted the system.
>>>
>>> Now, Cyder has 64GB (!) of RAM and it's somewhat beyond my comprehension
>>> why the machine would ever run out of memory, unless of course someone
>>> runs simulation codes with ultra-high memory requirements. If that's the
>>> case, please refrain from doing that. As you might have noticed, it is
>>> not exactly trivial to get access to the machine in order to reboot it,
>>> once it hangs.
>>>
>>> cyder.cct.lsu.edu is back online
>>>
>>> Best,
>>> Ole
>>>
>>>
>>
>>
>
> _______________________________________________
> saga-devel mailing list
> saga-devel at cct.lsu.edu
> https://mail.cct.lsu.edu/mailman/listinfo/saga-devel
>