On Tue, 1 Mar 2011, Jim Lawson wrote:
> The messages you both received indicate that the zoo client (wapiti) was
> clearly having trouble talking to the fileserver (barasinga) at the time.
> It appears to be fine now, and the network is solid between the two
> hosts. The hosts themselves are healthy. Our monitoring systems did
> not detect a problem at the time, but that doesn't mean there wasn't a
> problem. We'll keep our eyes open. I'm assuming things are working OK
> for you both now?
> On 03/01/2011 10:33 AM, Barbara Joan Hogel wrote:
>> Hi saa,
>> was trying to get into pine on zoo... and I got
>> "server barasinga.uvm.edu not responding still trying"
>> message as well.
>> I finally got it.
>> Thought saa should know.
>> Is zoo healthy?
>> ---------- Forwarded message ----------
>> Date: Tue, 1 Mar 2011 10:26:58 -0500
>> From: Jacob Beauregard <[log in to unmask]>
>> Reply-To: Technology Discussion at UVM <[log in to unmask]>
>> To: [log in to unmask]
>> Subject: git, chmod on zoo being horribly slow?
>> I had to change the permissions of some files on Zoo. It took a
>> ridiculous amount of time.
>> I also really want to commit some source code changes for a project
>> with git.
>> The git commit command took a very long time, and in the meanwhile
>> NFS server barasinga.uvm.edu not responding still trying
>> (and much later...)
>> NFS server barasinga.uvm.edu ok
>> (commit-related text)
> Jim Lawson
> Systems Architecture & Administration
> Enterprise Technology Services
> University of Vermont
> Burlington, VT USA