<html><head></head><body>Hi Josiah,<br>
<br>
Thank you so much for asking, and for the time you're dedicating to this. I actually have two paper deadlines coming up, one on January 15 and another one on February 3. I have some interesting results right now, but need to run more experiments to confirm and expand on stuff. While life happens, and I'll deal with whatever comes up, I could really use cpu time right now. <br>
<br>
Thanks again,<br>
<br>
Jaime<br><br><div class="gmail_quote">On December 22, 2015 10:13:50 AM EST, "Wm. Josiah Erikson" <wjerikson@hampshire.edu> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hey folks,<br /> I'm trying to get an idea of how much people were planning on using<br />the cluster over the holidays, i.e. how much effort I should put into<br />this. Are there folks who were planning to do important work over the<br />break whose plans will be totally screwed up if it's not back until<br />after the new year?<br /> I will come in tomorrow and probably be able to get it back up<br />anyway, just want to know what kind of priority to give it in case of<br />mishap.<br /> Thanks and happy holidays!<br /> -Josiah<br /><br /><br />On 12/22/15, 8:47 AM, Wm. Josiah Erikson wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I got some time this morning and came in on a vacation day...<br /><br /> After some mucking around with BIOS and CPU's and memory config, things<br /> deteriorating quickly...<br /><br /> Well, the machine won't even post now, so I
'll
have to move everything<br /> over to a new machine and get a new license file from Pixar. I'll try to<br /> get this done tomorrow morning, but this may mean that the cluster will<br /> be down until January if everything doesn't go smoothly.<br /><br /> Apologies!<br /> -Josiah<br /><br /><br /> On 12/21/15 9:28 PM, Wm. Josiah Erikson wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> ...or not. It appears to be happening again. I'm out tomorrow, but I<br /> should be in briefly on Wednesday and will make another attempt.<br /> -Josiah<br /><br /><br /> On 12/21/15, 11:04 AM, Wm. Josiah Erikson wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"> One of the power supplies was probably bad (dim/flickering lights, and<br /> Google searches had other people experiencing this problem with a bad<br /> power supply).
I
replaced it with a spare I had sitting around (thanks<br /> Mt. Holyoke)! and hopefully that will be the end of that. Of course, it<br /> could be something else too :)<br /> For now, fly's back up. Hopefully for good, but no guarantees.<br /> -Josiah<br /><br /><br /> On 12/21/15 10:35 AM, Wm. Josiah Erikson wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> Well, it just kernel panicked. Neat. That's new. So it's down now until<br /> I get it back up :) I'll keep you updated...<br /> -Josiah<br /><br /><br /> On 12/21/15 10:08 AM, Wm. Josiah Erikson wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"> Hello all,<br /> I rebooted fly again - it is not fixed yet, though it is up and<br /> running currently. I will probably take it down later today to try<br /> removing one of the CPU's to see if it is the pro
blem.
This should<br /> result in less than 10 minutes of downtime, and jobs should resume where<br /> they left off, so no need to hold off launching renders or whatever. My<br /> current theory is that CPU #2 is faulty. It could also be a bad power<br /> supply. I'll keep you updated.</blockquote><br /></blockquote></blockquote></blockquote></blockquote></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>