Discuss

discuss@lists.centos.org

1 participants
34753 discussions

RE: [CentOS] Server Crashing
by Ash Christopher 27 Jun '05

27 Jun '05

You could try the following instead of memtest86, since it has numerous limitations. http://people.redhat.com/dledford/memtest.html Memtest86 didn't report any problems on my server, but this script was able to find them. -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Greg Knaddison Sent: Monday, June 27, 2005 10:01 AM To: CentOS mailing list Subject: Re: [CentOS] Server Crashing On 6/27/05, Jay <jaybeattie(a)gmail.com> wrote: > On reboot all is fine. > It's running apache and DNS no SSH access. It passes memory test Memtest86. > How long did you run Memtest86? My understanding is that you can run it and have it work for a couple of hours, but then have it fail after two or three days running. Greg _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

Server Crashing
by Jay 27 Jun '05

27 Jun '05

Greetings. Every couple of day's I have a web server running CentOS 4.1 with all the patches as of Saturday that is crashing every couple of day's. Usualy between 4-6 am. The Console shows: Double Fault gdt at xxxx memory Double Falut tss at xxxx memory On reboot all is fine. It's running apache and DNS no SSH access. It passes memory test Memtest86. I can provide more information if you direct me on what to send. Thanks -Jay

4 3

mythtv on centos4
by Tony 27 Jun '05

27 Jun '05

Has anyone had any success or failures with installing mythtv onto centos4? Even better, has anyone any prebuilt rpms to do this? Looks to me like centos+mythtv is quite an interesting prospect in the always-on single home server environment. -- Cheers, Tony

4 3

Re: CentOS 4.0 -> 4.1 update failing
by Bryan J. Smith <b.j.smith＠ieee.org> 27 Jun '05

27 Jun '05

From: Johnny Hughes <mailing-lists(a)hughesjr.com> > That is by design ... the i686 glibc will not work with the c3 ... the > i686 kernel will. Interesting. Hmmm. > You need to use the i386 glibc. As written, the latest RH glibc SRPM > will not build for --target i486 or --target i586 ... But I've seen several packages where building for --target i386 still results in an --march=i486. In fact, that's probably why they clearly still say ".i386.rpm" despite requiring i486 ISA. > I am close to making it build properly for --target i586, but since > the .i386 glibc works well on i586 and it should build with that > target unmodified in the future, that is the way we will proceed. -- Bryan J. Smith mailto:b.j.smith@ieee.org

2 1

RE: [CentOS] Multiple system updates
by Bryan J. Smith 27 Jun '05

27 Jun '05

From: Peter Arremann > This is a question for you guys out there that have a bunch of similar > configured systems out there... How do you handle your updates? I do not mean > the technical level, but from the logistics. No updates? Just run yum by cron > and grab the latest of the web and trust the developers that it works? > Deploy only certain packages automatically (i.e. omit kernel updates)? > run your own yum/apt/up2date/whatever repos? Unless there are only 2-3 systems, the last option. I _always_ maintain an internal repository that goes through its own "enterprise release." One test system always gets the task of regression testing a new set of updates before it hits production. High security rollouts happen ASAP, other rollouts are far less pressured. For only 2-3 systems, I still have a test system, but it's cheap and its hardware does not match production. So I test on one production as long as I can before upgrading all. If I had a huge client base, I'd just maintain my own repository on the Internet with my releases they feed from. So far, my clients have always had their own resources to maintain the repository and procedures after I setup it up and left.

1 0

CentOS-announce Digest, Vol 4, Issue 11
by centos-announce-request＠centos.org 27 Jun '05

27 Jun '05

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CentOS-4/alpha 4.1beta is there to play (Pasi Pirhonen) 2. CESA-2005:524 Moderate CentOS 3 i386 freeradius - security update (Tru Huynh) 3. CESA-2005:524 Moderate CentOS 3 x86_64 freeradius - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Sun, 26 Jun 2005 18:32:38 +0300 From: Pasi Pirhonen <upi(a)iki.fi> Subject: [CentOS-announce] CentOS-4/alpha 4.1beta is there to play To: centos-announce(a)centos.org Message-ID: <20050626153238.GM21054(a)core.upi.iki.fi> Content-Type: text/plain; charset="us-ascii" Hi, I've always been kind of on/off with alpha. Remember making some kind of debian/alpha installer back -97ish. Lately (like past 2 years), i've been compiling SRPMS on alpha too from time to time. Most of my alpha hardware was pretty much ancient crap, so i wasn't quite confident pushing anything out to public as i wasn't able to test even if EV6 would be ok. Little over week ago i got a AlphaServer ES45, which was the turning point on this all (i thank you whom gave me this box once again even tho i cannot reveal any names). There is lot to personally thank for AlphaCore project as some of the patches i got directly from that work, would have been nasty for me to spot out. I just don't feel that building FC3 for alpha is enought and will be long term maintainable. That's where CentOS-4/alpha should kick in as the basic codebase should be maintained next 7ish years. There are modified SRPMS beoynd the normal CentOS mods, but it's some 30ish of those now, so it's only really few of them all. AVAILABILITY: http://beta.centos.org/centos/4.1beta/isos/alpha/ - which does have ISO-images and .torrent files for CD/DVD-images. - DVD-image does contain full binaries + source - ISOS labeled 'bin' are binaries only - ISOS labeles 'src' are the sources http://beta.centos.org/centos/4.1beta/os/ - which is unpacked, installable tree. http://beta.centos.org/centos/4.1beta/ - generally as this is the point when the yum config should point for updates etc. BETA RELEASE INFO: It ain't perfect. There are lot to improve still. I just wanted to make this public beta now so there might be some community interest/help for making it really smooth. One thing woth of mentining is that CFLAGS have been '-mtune=ev6' for all the packages, that does obey normal rpmbuild process. I am not sure what the impact is in real life, but IMO it won't make a really slow hardware any _slower_ and might even a little faster for anything useable (no pun intended. 'useable' may vary from person to person :) EXPECTED FINAL RELEASE TIME: I'd expect this to be bit much polished up time of CentOS 4.2 will be reality. At least it's where i am aming for final release. TESTED PLATFORMS: - a quad-1GHz ES45 w/ Radeon 9250 (PCI) - a AlphaStation 255/233 (text mode install) - a AlphaStation 1000 (text mode install) - ES45 was trested with console=ttyS0 too from the DVD KNOWN ISSUES: - The kernel isn't stock same one it's in other CentOS-4 releases - The php was replaced with new one - compat-glibc isn't there yet. Neither the later one or the Compaq release Redhat 7.2 one. I've patched the compat-glibc-2.3.2-95.30axp.src.rpm to build, but it was too late to include it to ISOs as i haven't had much time to test it and there is not real needs for this. - anaconda is putting the 'rhgb quiet' on command line even after text installtion, which might just crash the boot as graphics we're asked for first place. - the DVD isn't working at least on my ES45 with IDE-drive. SCSI is fine. I have to look about mkisofs ordering, because that might just be so that those needed files are 'unreachable' for SRM w/ IDE. - the aboot menu lacks the predefined selection for 'text askmethod' for forced text mode instalaltion from net for example. Forgot that one. - SELinux rulesets aren't quite right for everything, so disabling/making it warn level lets it boot better now on installation. - I've built some of the packages by disabling the checks at buildtime, so there might be 'non-working' software. namely gmp, subversion from memory. INVOLVING: - join the mailing lists at http://lists.centos.org/mailman/listinfo/centos http://lists.centos.org/mailman/listinfo/centos-devel - mail me directly to upi(a)iki.fi - more information from http://www.centos.org/ That's about it. I am sure i've already forgotten much i ment to say on this beta release announcement, but now i do push send and worry things later more. -- Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

1 0

Multiple system updates
by Peter Arremann 27 Jun '05

27 Jun '05

This is a question for you guys out there that have a bunch of similar configured systems out there... How do you handle your updates? I do not mean the technical level, but from the logistics. No updates? Just run yum by cron and grab the latest of the web and trust the developers that it works? Deploy only certain packages automatically (i.e. omit kernel updates)? run your own yum/apt/up2date/whatever repos? Thanks for your time, Peter.

2 1

RE: [CentOS] OT: question on setting up an email server
by Bruno S. Delbono 27 Jun '05

27 Jun '05

> Don't know if qmailtoaster already has been mentioned. It's really easy to > setup and > I'm really happy with my setup. > > http://www.qmailtoaster.com/ >From postfix-users@ Georgi Guninski have found a remotely-exploitable security hole in qmail. <http://www.guninski.com/where_do_you_want_billg_to_go_today_4.html> D. Bernstein denied the claim, classified it as "portability problem" and refused to pay the prize. <http://cr.yp.to/qmail/guarantee.html> Qmail's ML responded nervously to Guninski's post. Like everytime when anyone dare to say anything negative about qmail... It's quite interesting: "I said that Guninski's dick isn't half as big as he's trying to claim." "Go masturbate somewhere else." "Learn to read, moron." Link - http://tinyurl.com/caooe ----

7 10

strange problem on regconizing /dev/sda and /dev/hda
by Ceg Ryan 27 Jun '05

27 Jun '05

I installed a 4.1 x86_64 with kernel 2.6.9-11.ELsmp (rpm) initially. My box is tyan 5350 and a SATA harddisk The install was successful and the harddisk was detected as /dev/sdaX But strangely, when I first reboot my machine. The harddisk change to /dev/hdaX What is the problem ? Below are some of dmesg output hda: WDC WD1200JD-00HBB0, ATA DISK drive Probing IDE interface ide1... Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... Using cfq io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: max request size: 1024KiB hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63 hda: cache flushes supported hda: hda1 hda2 hda3 hda4 < hda5 > ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver mice: PS/2 mouse device common for all mice md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 112Kbytes TCP: Hash tables configured (established 524288 bind 37449) Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 ACPI: (supports S0 S1 S5) ACPI wakeup devices: PCE0 PCE1 PCIX PCIB USB1 USB2 USBE KBC0 MSE0 Freeing unused kernel memory: 164k freed SCSI subsystem initialized libata version 1.10 loaded. ata_piix version 1.03 ACPI: PCI interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 193 ata: 0x1f0 IDE port busy PCI: Setting latency timer of device 0000:00:1f.2 to 64 ata1: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 ata1: SATA port has no device. scsi0 : ata_piix

2 3

"vsftpd is dead but subsys is locked"
by Draden 26 Jun '05

26 Jun '05

If someone could give advice - I am running Centos 4 and on it I am running among other things vsftpd. Today I noticed the ftp services wasn't running, when I went to restart it it says it starts, but there is no pid for it. when I do a status on it, it gives a message saying "vsftpd is dead but subsys is locked" I have tried removing the lock file and no joy. I even just resorted to a reboot hoping that would clear the issue and to no avail Draden -- "Delivery yesterday, Code today, Think Tomorrow"

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss