My current hypothesis is that Ubuntu automatic security updates (or
something else stupid) somehow activated some sort of overly aggressive
firewall rules, since I ran into the same problem on four other servers I
have running ubuntu with automatic security updates (I ink). Anyway, the
machines are now way too secure! I'll find out soon enough though (I
should have this fixed in about two hours).
If you are good at using Dell iDrac remote management with Linux, please
email me...
> On Wednesday, 3 October 2012 18:15:47 UTC+8, fhivert wrote:
>> Hi there,
>> The combinat machine seems to ping but doesn't answer neither to the
web, nor
>> to ssh. Can a local guy investigate and maybe relaunch it ?
>> Thanks,
>> Florent
> --
> You received this message because you are subscribed to the Google Groups
"sage-devel" group.
> To post to this group, send email to sage-devel@googlegroups.com.
> To unsubscribe from this group, send email to
combinat.math.washington.edu is now fixed. For some mysterious
reasons the ufw firewall was active, with evidently *no* rules, and it
was blocking most everything. I don't know 100% for certain why this
happened; however, I've just done:
apt-get remove unattended-upgrades ufw
so it is unlikely to happen again.
Note that there was no downtime or interruption of anybody's jobs, and
this was not caused by over-use. (This is the only problem we have
ever had so far with combinat, by the way!)
I will be scheduling some (about 2 minutes -- just the time to reboot
once) of downtime for combinat, since I have to reset the UPS it is
connected to, in order to debug a UPS battery issue. That will
probably be in about a week, and there will be an announcement.
> My current hypothesis is that Ubuntu automatic security updates (or
> something else stupid) somehow activated some sort of overly aggressive
> firewall rules, since I ran into the same problem on four other servers I
> have running ubuntu with automatic security updates (I ink). Anyway, the
> machines are now way too secure! I'll find out soon enough though (I
> should have this fixed in about two hours).
> If you are good at using Dell iDrac remote management with Linux, please
> email me...
>> On Wednesday, 3 October 2012 18:15:47 UTC+8, fhivert wrote:
>>> Hi there,
>>> The combinat machine seems to ping but doesn't answer neither to the web,
>>> nor
>>> to ssh. Can a local guy investigate and maybe relaunch it ?
>>> Thanks,
>>> Florent
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-devel" group.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> To unsubscribe from this group, send email to
>> sage-devel+unsubscribe@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
> --
> William Stein
> Professor of Mathematics
> University of Washington
> http://wstein.org
-- William Stein
Professor of Mathematics
University of Washington
http://wstein.org
> combinat.math.washington.edu is now fixed. For some mysterious
> reasons the ufw firewall was active, with evidently *no* rules, and it
> was blocking most everything. I don't know 100% for certain why this
> happened; however, I've just done:
> apt-get remove unattended-upgrades ufw
> so it is unlikely to happen again.
Thanks !!!
> Note that there was no downtime or interruption of anybody's jobs, and
> this was not caused by over-use. (This is the only problem we have
> ever had so far with combinat, by the way!)
A few weeks ago, due to a huge memory leak in a code running in parallel on 32
core, I had my computation killed due to a failed memory alloc. combinat was
not very responsive for a couple of minutes but I had the impression that
except my computations nothing suffered from it. As a consequence I didn't
mention it. Does someone know if it is possible to know if there were some
other consequences ?
On Wed, Oct 3, 2012 at 12:33 PM, Florent Hivert <Florent.Hiv...@lri.fr> wrote:
> Hi,
>> combinat.math.washington.edu is now fixed. For some mysterious
>> reasons the ufw firewall was active, with evidently *no* rules, and it
>> was blocking most everything. I don't know 100% for certain why this
>> happened; however, I've just done:
>> apt-get remove unattended-upgrades ufw
>> so it is unlikely to happen again.
> Thanks !!!
>> Note that there was no downtime or interruption of anybody's jobs, and
>> this was not caused by over-use. (This is the only problem we have
>> ever had so far with combinat, by the way!)
> A few weeks ago, due to a huge memory leak in a code running in parallel on 32
> core, I had my computation killed due to a failed memory alloc. combinat was
> not very responsive for a couple of minutes but I had the impression that
> except my computations nothing suffered from it. As a consequence I didn't
> mention it. Does someone know if it is possible to know if there were some
> other consequences ?
I wouldn't worry about it at all.
-- William
> Cheers,
> Florent
> --
> You received this message because you are subscribed to the Google Groups "sage-devel" group.
> To post to this group, send email to sage-devel@googlegroups.com.
> To unsubscribe from this group, send email to sage-devel+unsubscribe@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
-- William Stein
Professor of Mathematics
University of Washington
http://wstein.org