I just made the change in puppet to block port 80 on our publictest
machines. Theoretically, the apps on those servers shouldn't be touching our
production db, but we shouldn't underestimate human stupidity.
Let us know if stuff breaks.
It's been a little over a year since I claimed the self-appointed
title of Fedora Mirror Wrangler. I have received quite a few kudos for
doing it - and it's fun coordinating a few hundred mirrors, providing
the best download experience for a few hundred thousand users.
For the benefit of Fedora as a whole, I'd like additional people to
step up and become Mirror Wranglers too. Tasks include:
* understanding the database schema and code behind MirrorManager, and
being able to enhance it as necessary
* moderating new mirror requests
* moderating the mirror-list and mirror-list-d requests
* participating on these lists
* manually scrubbing the database occasionally (I added ~30 F8 mirrors
a few weeks ago where they were mirrors at some point, but hadn't
added themselves into MM, or had added themselves incorrectly).
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
I've added excludes and weeded out a ton of crap from the epylog
reports. You'll note that:
1. the report is now down to about 1/6th the size it was
2. there is still an metric buttload of stuff coming in the logs
The stuff showing up there now are legitimate reports. If you see
something in the sections at the bottom then it needs to be fixed.
Please do so. :)
I'm nearing completion of the hosted setup and I'm at a point where I
can either make some temporary convoluted puppet configs, or I can just
disable the puppet configs for the production instance and get started
on the new instance. I've chosen the latter. If you have any changes
to make to hosted please coordinate it with me. I expect the new site
to be up by the end of the week at the latest.
Anyone know of any mail list software besides mailman that they've used
and like? I ask because I'm not a huge fan of mailman. The hosted
mailing list will probably have precedence and I think it is likely that
whatever we do in hosted is what we'll end up doing with the rest of
Fedora's mail lists when the time comes.
Looks like smolt is hitting the limit of 700MB pretty easily. I was
going to up the limit but I found that smolt was timing out even when
running with less than 700MB of memory. Restarting the server stopped
that from happening.
So one possibility is that once smolt allocates so much memory, some
portion of what it does takes too much time to scan through that memory.
If that's so we actually want to decrease the amount of memory smolt
can allocate before being restarted.
Another possibility is that the smolt server is getting stuck somewhere
in processing and that's preventing either the smolt server or the
database from processing future sendProfile's correctly. In this
scenario, restarting the server due to memory usage is fixing this as a
side effect. We really want to find and fix the bug if this is the case.
-------- Original Message --------
Subject: Cron <root@app4> /usr/local/bin/restart-memhogs.sh
Date: Sat, 1 Dec 2007 18:30:02 -0700
From: root(a)app4.fedora.phx.redhat.com (Cron Daemon)
Restarting smolt 31069 RSS: 691732