DevHeads.net

Postings by Stephen John Smoogen

QA/Development downtime 2018-06-07 2300 UTC - 2018-06-08 0300 UTC

There will be an outage starting at 2018-06-07 23:00 UTC, which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="https://fedoraproject.org/wiki/UTCHowto" title="https://fedoraproject.org/wiki/UTCHowto">https://fedoraproject.org/wiki/UTCHowto</a>
or run:

date -d '2018-06-07 23:00 UTC'

Reason for outage:

Currently the database server on the fedora qa network has only 2 CPUs
and limited ram. This is causing problems with waiverdb/resultsdb and
other tools needing to get builds in place.

Planned Outage - Ibiblio Servers (fedorapeople.org, torrent01.fedoraproject.org) 2018-05-09 12:00 UTC

Planned Outage - Server updates - 2018-05-09 12:00 UTC

There will be an outage starting at 2018-05-09 12:00 UTC,
which will last approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2018-05-09 12:00UTC'

Reason for outage:

Ibiblio is moving systems to a newer rack with 10G SFP+ networks.
Systems will need to be powered down, moved over to the new racks,
powered back up, configured to use the new networks in failover mode.

Affected Services:

download-ib01.fedoraproject.org
pagure-proxy01.fedoraproje

Planned Outage - Ibiblio Servers (fedorapeople.org, torrent01.fedoraproject.org) 2018-05-09 12:00 UTC

Planned Outage - Server updates - 2018-05-09 12:00 UTC

There will be an outage starting at 2018-05-09 12:00 UTC,
which will last approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2018-05-09 12:00UTC'

Reason for outage:

Ibiblio is moving systems to a newer rack with 10G SFP+ networks.
Systems will need to be powered down, moved over to the new racks,
powered back up, configured to use the new networks in failover mode.

Affected Services:

download-ib01.fedoraproject.org
pagure-proxy01.fedoraproje

Outage: Switch Outage - 2018-02-11 15:00 UTC

There will be an outage starting at 2018-02-11 15:00 UTC, which will last
approximately 2 hours.

To convert UTC to your local time, take a look at
<a href="https://fedoraproject.org/wiki/UTCHowto" title="https://fedoraproject.org/wiki/UTCHowto">https://fedoraproject.org/wiki/UTCHowto</a>
or run:

date -d '2018-02-11 15:00 UTC'

Reason for outage: The network switches in our PHX2 colocation
require a firmware upgrade to deal with false overheating problems.
The updates should be short 5 to 10 minute disruptions per switch.

Affected Services:

Bodhi - <a href="https://admin.fedoraproject.org/updates/" title="https://admin.fedoraproject.org/updates/">https://admin.fedoraproject.org/updates/</a>
Buildsystem - <a href="http://koji.fedoraproject.org/" title="http://koji.fedoraproject.org/">http://koji.fedoraproject.org/</a>
GIT / Source Control
Docs - <a href="https://docs.fedoraproject.or" title="https://docs.fedoraproject.or">https://docs.fedoraproject.or</a>

Trying to contact developer Axel Thimm

We have been getting bounced emails from Axel Thimm for a while and I
don't have any other way to contact him.

Re: X86 meeting 1900 UTC 2017-09-06

My apologies. I put in the wrong month.

X86 meeting 1900 UTC 2017-08-06

There will be a meeting in #fedora-meeting-2 on 1900 UTC (1500 EDT for
US timezones) to go over the setup of the x86 group

#startmeeting x86
#meetingname x86
#chair smooge jbackus
#topic Roll Call
#topic What does FESCO want
#info People who know how to advocate to upstreams
#info Advocating does not mean 'whining or begging'.
#info Advocating means working with upstream maintainers (kernel-list,
glibc, etc) to fix bugs.
#info Fedora is always moving forward. What does x86_32 have?
#topic What next?
#info Who will advocate?
#info Who will fix packages?
#info Who will show up?
#endmeeting

Lenovo T460p post 7.4 CR possible problems

I have updated my laptop to 7.4 CR this morning and found that there
have been a lot of logs on two fronts for the first time.

1.

Starting an x86_32 SIG

This is a notice to see if people are really interested in having a
SIG on 32 bit Intel. I haven't created a SIG so I am researching what
is needed but I started with this page

<a href="https://fedoraproject.org/wiki/Architectures/x86" title="https://fedoraproject.org/wiki/Architectures/x86">https://fedoraproject.org/wiki/Architectures/x86</a>

which mirrors the various other Architecture pages I looked at. A
Special Interest Group etc would be founded on this. I don't know if a
'mailing' list is wanted etc.

The steps I see are:
1. Whatever chartering work is needed to get a SIG together.
2. A formal statement as requested by some users about the architecture
3. A survey of problems on the architecture.
4.

Outage of Build Systems 2017-06-24 16:00 UTC

There will be an outage starting at 2017-06-24 16:00UTC, which will
last approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2017-06-24 16:00 UTC

Reason for outage:

There have been some performance problems with the backend switches.
These need an update from juniper and a reboot and possible debugging.

Affected Services:

pkgs.fedoraproject.org
koji
koshei
kojipkgs
pkgdb
bodhi / updates
mdapi service

Services not listed are not affected by this outage.

Contact Information:

Ticket Link: https://

Outage: 2017-03-02 15:00 UTC -> 19:00 UTC

<a href="https://pagure.io/fedora-infrastructure/issue/5862" title="https://pagure.io/fedora-infrastructure/issue/5862">https://pagure.io/fedora-infrastructure/issue/5862</a>

Fedora Project will have a rolling outage of systems due to a switch
upgrade happening in PHX2 on 2017-03-02 15:00UTC -> 19:00 UTC. All
systems in PHX2 will be affected at some point or another for 10
minute downtimes as switches are upgraded to a new security version.

Please join the fun on #fedora-admin to see what is affected and when

Planned Outage: Cloud Environment - 2016-12-01 21:00 UTC

There will be an outage starting at 2016-12-01 21:00 UTC, which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="https://fedoraproject.org/wiki/UTCHowto" title="https://fedoraproject.org/wiki/UTCHowto">https://fedoraproject.org/wiki/UTCHowto</a>
or run:

date -d '2016-12-01 21:00 UTC'

Reason for outage:

We have been in a freeze for the release of Fedora 25 and have
multiple updates across the systems needed to occur.

Planned Outage: General Services Environment - 2016-11-30 21:00 UTC

There will be an outage starting at 2016-11-30 21:00 UTC, which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="https://fedoraproject.org/wiki/UTCHowto" title="https://fedoraproject.org/wiki/UTCHowto">https://fedoraproject.org/wiki/UTCHowto</a>
or run:

date -d '2016-11-30 21:00 UTC'

Reason for outage:

We have been in a freeze for the release of Fedora 25 and have
multiple updates across the systems needed to occur.

Planned Outage: 2016-11-29 21:00 UTC Build Environment

There will be an outage starting at 2016-11-29 21:00 UTC, which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="https://fedoraproject.org/wiki/UTCHowto" title="https://fedoraproject.org/wiki/UTCHowto">https://fedoraproject.org/wiki/UTCHowto</a>
or run:

date -d '2016-11-29 21:00 UTC'

Reason for outage:

We have been in a freeze for the release of Fedora 25 and have
multiple updates across the systems needed to occur.

Planned Outage: Staging Environment - 2016-11-28 21:00 UTC

There will be an outage starting at 2016-11-28 21:00 UTC, which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="https://fedoraproject.org/wiki/UTCHowto" title="https://fedoraproject.org/wiki/UTCHowto">https://fedoraproject.org/wiki/UTCHowto</a>
or run:

date -d '2016-11-28 21:00 UTC'

Reason for outage:

We have been in a freeze for the release of Fedora 25 and have
multiple updates across the systems needed to occur.

Starting non-responsive maintainer process for affix

I have been trying to contact the user affix about nagios for the last
couple of weeks. At first his registered email address was for a
unregistered domain. The domain is re-registered but there has been no
response to direct emails. Last week, I opened
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1389572" title="https://bugzilla.redhat.com/show_bug.cgi?id=1389572">https://bugzilla.redhat.com/show_bug.cgi?id=1389572</a> as per the process
outlined in

<a href="https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers" title="https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers">https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers</a>

This week I am opening this email so if someone knows how to get in
touch with them, that we can try to do so.

Infrastructure Outage: mailman/nagios 2015-12-02 0300 UTC

Planned Outage: Mailman / Nagios - 2015-12-02 03:00 UTC

There will be an outage starting at 2015-12-02 03:00 UTC, which will
last approximately 1 hour.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2015-12-02 03:00 UTC'

Reason for outage:

We will be re-adding a replaced hard drive.

Affected Services:

virthost17:bugzilla2fedmsg01.phx2.fedoraproject.org:running:1
virthost17:db-datanommer02.phx2.fedoraproject.org:running:1
virthost17:ipsilon02.phx2.fedoraproject.org:running:1
virthost17:kerneltest01.phx2.fedoraproje

Unplanned Fedora Outage 2015-01-14 21:30

Fedora had a 35 minutes off the internet outage starting around 21:30 UTC.
This was due to my pushing an incomplete DNS table out causing named to
crash when it got to starting the file getfedora.com and not finding it.
Problem was backed out and changed but because of a bootstrap issue of
needing dns to get to dns in a couple of places it had to be done by hand
to get all DNS servers back up.

I am looking at what I can do to not have this happen again or make backing
out faster.

My apologies for the many many many pages people in sysadmin got.

RFC: Alternative Desktop SIG

I would like to put together an alternative desktop sig which will build,
qa, and support desktops which are not the Enterprise Linux primary or
secondary desktops (GNOME and KDE).

There are a couple of ground rules I would like to propose:

1) Any desktop system needs to have 3 sponsors who are people willing to do
the work of building RPMS, coordinating user bugs with upstream, and fixing
packages.

What do rawhide testers want and expect?

In reading the long trash each other fest that accompanies pre-release
jitters, could we start on a cleaner plate? What do the people who are
using rawhide day-in/day-out expect out of the channel? What level of
pain does someone like Jonathan Corbet expect and how can we better
serve them? [And no this isnt me trying for another distro quote of
the week, he is just my reference point of someone I know who runs
rawhide day in and out.]

In some cases, expectations may be off which means we need to market
our deliverables better.

Outage: Cleanup of Red Hat located systems - 2011-07-11 20:00 UTC

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2011-07-11 20:00 UTC'

Reason for outage:

We will be removing old systems and putting in new ones at the
Red Hat colocation facility in Phoenix.

At the moment outages are planned for 2011-07-12 00:00 UTC
- Secondary Architecutures
- QA systems
- some Fedora community hardware

No other outages are planned, but deracking of old machines and
racking new ones could result in outages or instability in existing
services.

Due to the nature of the work, while we will try

How to best debug kernel problems

I have been having problems with my Lenovo T61 and Rawhide. Currently
the system will do all kinds of watchdog resets when I am booting the
3.0 kernels but not with the 2.6.38 kernel. I am trying to figure out
how to best capture and debug them as they tend to scroll off the
screen faster than I can catch anything. For the rc4 kernels I think
it is dieing when trying to remount the root disk but on the rc5
kernel it gets past that and crashes during nfs or smartd. The funny
thing is..

Outage: hosted servers 2011-04-12 04:00 UTC

There will be an outage starting at 2011-04-12 04:00 UTC, which will last
approximately 6 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d ' 2011-04-12 04:00 UTC'

Reason for outage:

Serverbeach (our service provider for our hosted and other servers)
are upgrading switches in their San Antonio (SAT) Datacenter.

Outage: Upgrading nagios - 2011-03-24 18:00 UTC

There will be an outage starting at 2011-03-24 18:00 UTC, which will last
approximately X hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2011-03-24 18:00 UTC'

Reason for outage:

Moving from EL5 nagios to EL6 nagios

Affected Services:

Nagios
Zodbot
DHCP for PHX2 application network.

Unaffected Services:

BFO - <a href="http://boot.fedoraproject.org/" title="http://boot.fedoraproject.org/">http://boot.fedoraproject.org/</a>
Bodhi - <a href="https://admin.fedoraproject.org/updates/" title="https://admin.fedoraproject.org/updates/">https://admin.fedoraproject.org/updates/</a>
Buildsystem - <a href="http://koji.fedoraproject.org/" title="http://koji.fedoraproject.org/">http://koji.fedoraproject.org/</a>
CVS / Source Control
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
D

Outage: Serverbeach servers downtime 2011-03-16 03:00 UTC -> 2011-03-16 09:00 UTC

There will be an outage starting at 2011-03-16 03:00 UTC, which will last
approximately 6 hours.

Updating SSL keys on fedoraproject.org 2011-03-10

Various SSL keys are aging out so we will be updating them before anyone
gets a <This CERT is not valid.> page.

We have already updated fedorahosted.org and will now be updating the
cert for the main site: fedoraproject.org.

The old certificate came from Equifax, was a 1024 bit key and had the
fingerprint:

SHA1 Fingerprint=E7:6D:26:72:D6:A2:2D:7A:5C:CF:BB:D2:05:B9:8E:7C:49:F5:F8:A8

The new certificate is issued by GeoTrust, Inc and is a 4096 bit key
with the fingerprint:

SHA1 Fingerprint=F6:D6:28:85:64:B1:11:19:38:2A:82:EF:F8:F0:22:E8:27:4F:A5:CF

Please report any problems with these c

Updated: Outage: Ibiblio/ipv6 servers - 2011-03-02 14:00 UTC

There will be an outage starting at UTC, 2011-03-02 14:00 which will last
approximately 4 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a>
or run:

date -d '2011-03-02 14:00 UTC'

Reason for outage:

metalabs is moving facilities and needs for our collocated server to
move with them.

Infrastructure Outage Notification: 2011-03-02 1200 UTC -> 1500 UTC

Tomorrow the services at ibiblio will be moved to a new physical location

ibiblio01.fedoraproject.org
app05
backup02
ns02
proxy04
smtp-mm03
torrent01

Archive Fedora 12

I will be working on archiving fedora release 12 from
/pub/fedora/linux to /pub/archive/fedora/linux. The data should be
mostly across already, but I want to let people know that the changes
are occuring and that we will be making changes to Mirror manager
point from one to the other.