public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: law@redhat.com
To: Matthew Galgoci <mgalgoci@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: outage window
Date: Thu, 02 Oct 2003 16:21:00 -0000	[thread overview]
Message-ID: <200310021621.h92GL9ZT009648@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "Thu, 02 Oct 2003 12:12:25 EDT." <Pine.LNX.4.44.0310021204130.22529-100000@lacrosse.corp.redhat.com>

In message <Pine.LNX.4.44.0310021204130.22529-100000@lacrosse.corp.redhat.com>,
 Matthew Galgoci writes:
 >
 >I need to replace the layer 2 switch that sources.redhat.com hangs off of, an
 >d
 >I'd like to do it tomorrow, oct 3, 2003 between 9am and 10am EDT. The current
 >switch is failing (though it still switching packets). It's a cisco 2900 seri
 >es
 >that's expereincing memory errors, like the following:
 >
 >%SYS-2-MALLOCFAIL: Memory allocation of 192 bytes failed from 0xE847C, pool P
 >ro0-Process= "LED Control Process", ipl= 0, pid= 19
 >-Traceback= 1CACB8 1CC7AC E8480 103DE4 103FD8 E574C 1F1F68 1F7268 1F1F68 1F30
 >300
 >%SYS-2-MALLOCFAIL: Memory allocation of 128 bytes failed from 0x1CCFCC, pool 
 >Pr0-Process= "Broadcast Storm Control", ipl= 0, pid= 32
 >-Traceback= 1CACB8 1CC7AC 1CCFD0 1D90AC 1D913C E8570 103DE4 103FD8 E574C 1F1F
 >680
 >
 >The connectivity interruption should be very minor. I expect it to take all o
 >f 10 minutes
 >for the entire operation.
 >
 >If anyone objects to the time please speak up now, else I'm just going to 
 >go ahead as stated above.
Go for it.
jeff

      reply	other threads:[~2003-10-02 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-02 16:12 Matthew Galgoci
2003-10-02 16:21 ` law [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200310021621.h92GL9ZT009648@speedy.slc.redhat.com \
    --to=law@redhat.com \
    --cc=mgalgoci@redhat.com \
    --cc=overseers@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).