Please delete something or buy another disk :)
We got there email hook, which probobly do not have enough disk space on
some mount.
[msu...@dri/~/rhn/spacewalk.pub/schema/spacewalk]$ git push --tags
Counting objects: 1, done.
Writing objects: 100% (1/1), 229 bytes, done.
Total 1 (delta 0),
Last I looked there were hundreds of gigs free there. I know you spacewalk
folks are space hogs, but not to the tune of hundreds of gigs :) I think
from the alerts I've been getting that hosted has other problems right at
the moment, but I'm at work and can't get in to look at it right now.
On
On Mon, 12 Apr 2010, Miroslav Suchý wrote:
Please delete something or buy another disk :)
We got there email hook, which probobly do not have enough disk space on
some mount.
I suspect this error came from smtp itself but I don't see any disks that
are full on space. The only thing I can
On Mon, 12 Apr 2010, Mike McGrath wrote:
On Mon, 12 Apr 2010, Miroslav Suchý wrote:
Please delete something or buy another disk :)
We got there email hook, which probobly do not have enough disk space on
some mount.
I suspect this error came from smtp itself but I don't see any
On Mon, 12 Apr 2010, Stefan Schlesinger wrote:
On 12.04.2010, at 16:10, Mike McGrath wrote:
Nope, that disk certainly filled up:
https://admin.fedoraproject.org/collectd/bin/index.cgi?hostname=hosted1plugin=dftimespan=86400action=show_selectionok_button=OK
Hey,
just a short question
Mike McGrath wrote:
On Mon, 12 Apr 2010, Mike McGrath wrote:
On Mon, 12 Apr 2010, Miroslav Suchý wrote:
Please delete something or buy another disk :)
We got there email hook, which probobly do not have enough disk space on
some mount.
I suspect this error came from
Between alpha and beta freezes, I decreased the MM config value
max_stale_days from 7 to 2. This causes MM to forget about old
repomd.xml data after 2 days instead of 7, which reduces how long a
mirror can be stale before being ignored by yum.
As we've slowed down releasing updates for existing
On 2010-04-12 11:03:17 PM, Matt Domsch wrote:
As we've slowed down releasing updates for existing releases, it can
be longer than 2 days between pushing updates. In this case, we run
into the propogation delay between when content gets posted on the
master, MM picking it up an hour later, and
On Tue, Apr 13, 2010 at 12:16:47AM -0400, Ricky Zhou wrote:
On 2010-04-12 11:03:17 PM, Matt Domsch wrote:
As we've slowed down releasing updates for existing releases, it can
be longer than 2 days between pushing updates. In this case, we run
into the propogation delay between when content
