infrastructure October 2006

infrastructure@lists.fedoraproject.org

49 participants
77 discussions

[Fedora-infrastructure-list] a simple request (i hope) about f.r.c
by Max Spevack 23 Oct '06

23 Oct '06

As much as I'd like to simply pull the plug on f.r.c completely, can we (at the very least, for now) simply but a redirect in place for the root of the site -- http://fedora.redhat.com -- that will just instantly send someone over to fedoraproject.org instead. We'll get a lot of traffic come Tuesday -- I'd like it all to land in the right place. Deeper links into f.r.c, I'm not too worried about. I'd like to fix the whole thing, but let's just take this first step for now. Complaints? Concerns? --Max -- Max Spevack + http://fedoraproject.org/wiki/MaxSpevack + gpg key -- http://spevack.org/max.asc + fingerprint -- CD52 5E72 369B B00D 9E9A 773E 2FDB CB46 5A17 CF21

5 7

[Fedora-infrastructure-list] Re: lockbox.fedora.phx.redhat.com system events: Mon Oct 23 04:03:29 2006
by seth vidal 23 Oct '06

23 Oct '06

On Mon, 2006-10-23 at 04:04 -0700, root wrote: Questions below: > Oct 22 04:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 04:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 04:10:02 bastion sendmail: sm-client -HUP succeeded > Oct 22 04:10:02 bastion sendmail: sm-client -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sendmail -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sm-client -HUP succeeded > Oct 22 05:10:02 bastion sendmail: sm-client -HUP succeeded Why is sendmail being restarted every hour on bastion? Better yet, why is it running sendmail? > Oct 22 05:11:49 cvs-int rhnsd[10625]: running program /usr/sbin/rhn_check > Oct 22 05:15:19 proxy4 rhnsd[1224]: running program /usr/sbin/rhn_check > Oct 22 05:17:16 proxy2 rhnsd[12819]: running program /usr/sbin/rhn_check > Oct 22 05:44:57 proxy1 rhnsd[1686]: running program /usr/sbin/rhn_check > Oct 22 05:45:19 proxy4 rhnsd[1227]: running program /usr/sbin/rhn_check > Oct 22 05:56:50 cvs-int rhnsd[11010]: running program /usr/sbin/rhn_check > Oct 22 06:00:18 db1 rhnsd[5452]: running program /usr/sbin/rhn_check > Oct 22 06:01:17 bastion rhnsd[11168]: running program /usr/sbin/rhn_check > Oct 22 06:02:14 proxy3 rhnsd[27507]: running program /usr/sbin/rhn_check > Oct 22 06:05:38 app2 rhnsd[4430]: running program /usr/sbin/rhn_check I can think of something to add to the epylog weed list, can you? :) -sv

3 3

[Fedora-infrastructure-list] Introduction
by Mel 23 Oct '06

23 Oct '06

* Name: Mel Adams * Profession: 1) Retired 2) English Tutoring 3) Web Services * Your goals in the Fedora Project: Simply to contribute what I can and learn a little. * Languages: English * What level and type of computer skills do you have? I have done some programing but I do not consider myself a programmer. I do have system level analytical skills having been paid to do that as one of my old jobs. I can do the hardware bit OK though. * What other skills do you have that might be applicable? I can edit and proof read pretty well. * What makes you an excellent match for the project? Not sure. That is why I am here. To find out if there is a match. * GPG KEYID = D0B495D0 * fingerprint = 7846 DA74 A422 77C7 D32C 6079 D86C D1CF D0B4 95D0

1 0

[Fedora-infrastructure-list] mirrors cgi and load
by seth vidal 22 Oct '06

22 Oct '06

So, In a bit of a concern I was thinking about the response time from the mirror cgi and also other load concerns. I was wondering if we had considered making mirrors.fedoraproject.org a round robin or load-balanced location between the duke site its on now and another site, possibly at PHX. The sqlite db of the data after a check should be small enough to quickly rsync between the two sites and this would help with load on the main fedoraproject.org system I would think. What do y'all think about implementing something like that in the next few days before FC6 final? It feels like it is just: 1. dns entry addition 2. vhost addition on one of the phx boxes 3. an rsync+ssh key at the end of the checker cron job -sv

3 2

[Fedora-infrastructure-list] Self Introduction: Paulo Santos
by Paulo Santos 22 Oct '06

22 Oct '06

Hi everyone, I'm new to the list, so this is my introduction. * Name: Paulo Santos * Profession: System Engineer * Your goals in the Fedora Project: System admin, help whenever and where i can and learn. * Languages: Portuguese, English * What level and type of computer skills do you have? Using Red Hat since 96/97 (can't remember), professionally since 2001. I'm not a programmer but i can do some usefull stuff in SQL, PHP and Bash. I'm completly focused on sys admin. Worked for Vodafone UK in the Vodafone Live! portal, so i have a good knowledge of Apache, tomcat, etc. * What other skills do you have that might be applicable? I already worked with RHEL, and currently work in a unix systems integrator. Mainly Sun Sparc, so i have access to sparc platforms (nothing midrange or high-end though, those are for clients only) if needed. * What makes you an excellent match for the project? System administration, and a completly self learner person. Give me a challenge, and i'll (try to) give you results :) Many thanks Regards, PS

1 0

[Fedora-infrastructure-list] PPC builder outage?
by Jesse Keating 21 Oct '06

21 Oct '06

A couple of builds are stacking up on the ppc hosts, and not finishing. Is something going on with them? -- Jesse Keating Release Engineer: Fedora

1 0

[Fedora-infrastructure-list] Account System 2 Update
by TomLy 20 Oct '06

20 Oct '06

Thanks go out to Jeffery for setting up the Xen box for me and helping me with my ssh inadequacies. I've been able to translate the LDAP schema to FDS LDIF format and imported it into the FDS on test5.fedora.phx.redhat.com . I've attached a screenshot for your viewing pleasure (notice the sshkey and bugzillaemail attributes on the properties page) . I'm calling this stage almost done. I'm sure that there will be more tweaking of the schema later, but the base is set. The next step, as I see it, is to develop a ldif export from the current account system's database. I will start work on this today. This would be a good project for one of the new members to help out with. If you can help, send me an email. ~tom

1 0

[Fedora-infrastructure-list] fpserv time problem
by seth vidal 20 Oct '06

20 Oct '06

The clock on fpserv appears to have gone all to hell. I couldn't get it to report in the kernel correctly, only from glibc. Which suggested something deeper going on. I've been going through the logs but not found anything yet. I've rebooted the box in the immediate term to get the wiki and friends working again. -sv

1 0

[Fedora-infrastructure-list] [Fwd: Cron <root@fpserv> run-parts /etc/cron.hourly]
by seth vidal 20 Oct '06

20 Oct '06

umm, wtf. -sv -------- Forwarded Message -------- From: Cron Daemon <root(a)fpserv.linux.duke.edu> To: root(a)fpserv.linux.duke.edu Subject: Cron <root@fpserv> run-parts /etc/cron.hourly Date: Tue, 10 Sep 611 04:18:02 -0500 (EST) /etc/cron.hourly/make-shell-accounts: /bin/tar: ./jeffreyt.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./jeffreyt.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./wtogami.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./wtogami.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./jtr.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./jtr.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./ja8sun.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./ja8sun.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./mmcgrath.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./mmcgrath.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./nman64.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./nman64.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./lmacken.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./lmacken.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./mschwendt.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./mschwendt.pub: time stamp 2006-10-20 11:01:02 is 44025486180 s in the future /bin/tar: ./katzj.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./katzj.pub: time stamp 2006-10-20 11:01:02 is 44025486180 s in the future /bin/tar: ./passwd: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./passwd: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./toshio.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./toshio.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./notting.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./notting.pub: time stamp 2006-10-20 11:01:02 is 44025486180 s in the future /bin/tar: ./scop.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./scop.pub: time stamp 2006-10-20 11:01:02 is 44025486180 s in the future /bin/tar: ./damian.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./damian.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./ausil.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./ausil.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./sopwith.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./sopwith.pub: time stamp 2006-10-20 11:01:02 is 44025486180 s in the future /bin/tar: ./shadow: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./shadow: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./rordway.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./rordway.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./spot.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./spot.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./skvidal.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./skvidal.pub: time stamp 2006-10-20 11:01:02 is 44025486180 s in the future /bin/tar: ./group: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./group: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: ./berrange.pub: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: ./berrange.pub: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future /bin/tar: .: implausibly old time stamp 0611-09-10 04:18:02 /bin/tar: .: time stamp 2006-10-20 11:01:03 is 44025486181 s in the future

1 0

[Fedora-infrastructure-list] Wiki Logs
by Damian Myerscough 20 Oct '06

20 Oct '06

Hi, I just wanted some confermition, is the fedoraproject.org site hosted on fpserv? and also does it have direct access to the lockbox machine e.g. it dosnt have to go through bastion?

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure October 2006