Discuss

discuss@lists.centos.org

34753 discussions

PHP question
by William Warren 06 Sep '06

06 Sep '06

I installed a new server a few days ago with a LAMP stack. It runs very well but GD based images(like the ones used for registration verification on the forums) aren't working. I can post my php diagnostic ouput..i wanted to see if anyone had nay ideas before i posted that large amount of stuff. -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is the heritage of the servants of the LORD, and their righteousness is of me, saith the LORD. -- carpe ductum -- "Grab the tape" CDTT (Certified Duct Tape Technician) Linux user #322099 Machines: 206822 256638 276825 http://counter.li.org/

2 1

CentOS-announce Digest, Vol 19, Issue 3
by centos-announce-request＠centos.org 06 Sep '06

06 Sep '06

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. CESA-2006:0633 Moderate CentOS 4 ia64 ImageMagick - security update (Pasi Pirhonen) 2. CESA-2006:0617 Important CentOS 4 ia64 kernel - security update (Pasi Pirhonen) 3. CESA-2006:0634 Important CentOS 4 ia64 xorg-x11 - security update (Pasi Pirhonen) 4. CESA-2006:0617 Important CentOS 4 s390(x) kernel - security update (Pasi Pirhonen) 5. CESA-2006:0633 Moderate CentOS 3 ia64 ImageMagick - security update (Pasi Pirhonen) 6. CESA-2006:0635 Important CentOS 3 ia64 XFree86 - security update (Pasi Pirhonen) 7. CESA-2006:0648 Moderate CentOS 3 ia64 kdegraphics - security update (Pasi Pirhonen) 8. CESA-2006:0633 Moderate CentOS 3 s390(x) ImageMagick - security update (Pasi Pirhonen) 9. CESA-2006:0635 Important CentOS 3 s390(x) XFree86 - security update (Pasi Pirhonen) 10. CESA-2006:0648 Moderate CentOS 3 s390(x) kdegraphics - security update (Pasi Pirhonen) 11. CESA-2006:0633 Moderate CentOS 4 s390(x) ImageMagick - security update (Pasi Pirhonen) 12. CESA-2006:0634 Important CentOS 4 s390(x) xorg-x11 - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Wed, 6 Sep 2006 00:45:49 +0300 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2006:0633 Moderate CentOS 4 ia64 ImageMagick - security update To: centos-announce(a)centos.org Message-ID: <20060905214549.GA17753(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2006:0633 https://rhn.redhat.com/errata/RHSA-2006-0633.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/ImageMagick-6.0.7.1-16.ia64.rpm updates/ia64/RPMS/ImageMagick-c++-6.0.7.1-16.ia64.rpm updates/ia64/RPMS/ImageMagick-c++-devel-6.0.7.1-16.ia64.rpm updates/ia64/RPMS/ImageMagick-devel-6.0.7.1-16.ia64.rpm updates/ia64/RPMS/ImageMagick-perl-6.0.7.1-16.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

new Centos 4.4 install--display update very SLOW
by fredex 06 Sep '06

06 Sep '06

Hi! I just installed Centos 4.4 on a machine at work, yesterday. Mostly it went well with just a couple of glitches. One of them is slow video performance. No, I'm not playing 3d games at work! :) Scrolling/repainting terminal windows is plainly MUCH slower than it is on my Centos 4.4 desktop at home. Machine at home is an Athlon XP 2600+ with one gig of RAM. Machine at work is a P4 2.26 Ghz with a gig of RAM. Before Centos, the one at work had RHEL WS 2.1, which did not exhibit the same issue. It was using KDE as the main desktop, while this time it is (so far) set to use Gnome (as is the box at home). Scrolling through a big file with less, for example, you can watch it paint the screen. Hitting 'B' to go back a screen is almost painful, you see it scroll part of the screen down, slowly, then fill in each line above that. It's the same hardware that was there before, the only thing that has changed is the OS. Clues? Thanks! -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The eyes of the Lord are everywhere, keeping watch on the wicked and the good. ----------------------------- Proverbs 15:3 (niv) -----------------------------

2 4

RE: [CentOS] very new user having problems
by Thompson Harmon [US], Stanley W. 06 Sep '06

06 Sep '06

> -----Original Message----- > From: centos-bounces(a)centos.org > [mailto:centos-bounces@centos.org] On Behalf Of William L. Maltby > Sent: Wednesday, September 06, 2006 1:29 AM > To: CentOS General List > Subject: Re: [CentOS] very new user having problems > > On Tue, 2006-09-05 at 19:05 -0700, barbaara fberg wrote: > > <snip> > > > 24 years ago just before he got out of the service they > found cancer and > > fixed it. > > It came back more aggressively and he has had chemo each > week. 4 more weeks > > to go. so he was resting a lot over the holiday before he > has to do it > > again. > > Many prayers are with you and for you and your hsuband. > > -- > Bill > Barbaara, Bill is correct - "many prayers are with you ..." I have added you and your husband to my prayer list and I am sure others will do the same. -- Stan

1 0

mount ntfs file system
by dxuranus 06 Sep '06

06 Sep '06

i learned that ntfs file system not supported by centos. and i try to tell my system version with uname -r and find my version is 2.6.9-22.EL so i download the kernel-module-ntfs-2.6.9-22.ELsmp-2.1.20-0.rr.9.10.i686.rpm but after rpm -ivh ..................... i do't know how to do? a article told me go to /usr/src/2.......... but i can't even find the dir . thanks for any help.

3 2

centos minimal install???
by Email Lists 06 Sep '06

06 Sep '06

I was doing an Internet facing server reload for a client today and he mentioned that there is a minimal install selection somewhere and that I should take a disk 1 of centos 4.4 and it would be under custom Is this the case? How? I couldn't find it, nor could he after the fact. If it exists, where is it, or how do I get to it for future reference please? I usually use a centos server cd myself. :-) Thanks and kind regards! - rh -- Robert - Abba Communications Computer & Internet Services (509) 624-7159 - www.abbacomm.net

4 6

Anyone seeing mock breakage after updating to 4.4?
by Ralph Angenendt 06 Sep '06

06 Sep '06

Morning, somehow the upgrade to 4.4 broke mock on my system: | [angenenr@shutdown SPECS]$mock -r c3-i386 /home/angenenr/redhat/SRPMS/apache-ssl-2.8.28-2el4.src.rpm | init | clean | prep | This may take a while | Could not find useradd in chroot, maybe the install failed? Nope, it's not the config_opts['chroot_setup_cmd'] = 'groupinstall build' issue, as I'm still using mock 0.4 (from kbs-CentOS-extras). I'm seeing this in the root.log in result/: | Executing /usr/sbin/mock-helper mount -t proc proc | /var/lib/mock/c3-i386/root/proc | mount: proc already mounted or /var/lib/mock/c3-i386/root/proc busy | mount: according to mtab, proc is already mounted on | /var/lib/mock/c3-i386/root/proc | | Executing /usr/sbin/mock-helper mount -t devpts devpts | /var/lib/mock/c3-i386/root/dev/pts | mount: devpts already mounted or /var/lib/mock/c3-i386/root/dev/pts busy | mount: according to mtab, devpts is already mounted on | /var/lib/mock/c3-i386/root/dev/pts When mock is trying to install the rpms for the buildroot then, I see: | error: can't create transaction lock on /var/lib/mock/c3-i386/root/var/lock/rpm/transaction And my root/ directory is missing usr/. Anyone else seeing this? Regards, Ralph -- Ralph Angenendt......ra(a)br-online.de | .."Text processing has made it possible Bayerischer Rundfunk...80300 München | ....to right-justify any idea, even one Programmbereich.Bayern 3, Jugend und | .which cannot be justified on any other Multimedia.........Tl:089.5900.16023 | ..........grounds." -- J. Finnegan, USC

5 17

Server closing all the ports after inactivity Could not connect to webserver
by Anil 06 Sep '06

06 Sep '06

Hi All I am running Centos -4.4 final with all the updates My webserver stop responding after about half an hour od inactivity.I just gets a timeout message. When I try to refresh the page 3-4 times it start active again. Infact all the ports on the server are closed during the inactive period even though I have ssh,ftp and http enabled on it. When the server is responding I can see (with a port scan)the ports are open. I tried disabling the firewall(on the centos server) altogether because the server sits behind another firewall. If I do a restart of the httpd or do any other network related stuff on the server it opens the ports again. Any help is appreciated Regards Anil -- Most operating systems were developed for commercial or technical motives, but GNU was developed for the sake of giving users the freedom to cooperate in a community. And if users don't know this, they will be in danger of losing their freedom. --Richard Stallman Public Key -------xxxxx cut here xxx-------- AAAAB3NzaC1kc3MAAACBAOJrx7vi+A+tR0pz/nwP8StnPJUOLmwXnxpvb0ty4qyiTzIY3wBmAr37OIccs0+JWT+mXi4mnaFCqoh7YRuhaBhIZ9lqxXGb1r8QnAiEDlrOtjVZTebyrP48awYilSE990/9Mt2ndflcWKoY0Jw1QcsZBCxctOj9sMIFr295xCcLAAAAFQDueRoBYb9ieF7KwvhZ9SlA92BFcQAAAIAY4QidL/eu15JaVWwNrs6Xys8+t2+1h331+G88guxl2q6AMCqgtuZMGomLNVIDN6plZPfxRB6UZYN8q+i03hFErCtX8sk9xO+g5RV8BrC0n87RohNVxm/++fblJ7sNxGYW/eIIm/AduLBhIPe11GDVFA5Km+hxGQSbjLWLVOw5VQAAAIEAvCFtqTOE4XP2n0Ppg6yyXJ/xwwKcJWFRpj7xILkBgTb8E+qeCv2tEgz/67SHTWy3PUG63LLW5cGDANe6Virc1W92y+4v1yFbmcTRHYDm4hI4CgOd/dIrJrkQ3iDj/M84x60uAJ7RYdtoHjDv/phXua02Xl9OMa7Zi79emxZtzPI= Anil@cuty -------xxxxx cut here xxx--------

3 3

OT - backup question/advice
by Thomas E Dukes 06 Sep '06

06 Sep '06

Hello, I have been using mondorescue to backup to dvd for several months now without any problems. Since upgrading to Centos 4.4, I now receive a few errors. The errors are for files in /var/named/chroot/proc. I guess these files change so when I do a differntial backup they aren't there and result in errors. (Never got any errors before and I think these files were there in 4.3) If I exclude the files from the backup, no errors. My question is what, if any problems would I run into not backing these files up and having to do a complete system restore? TIA, Eddie

6 11

Bug: lvchange delayed until re-boot. System lock up experienced.
by William L. Maltby 06 Sep '06

06 Sep '06

Did a search for LVM at the CentOS bugzilla. Nothing seems to match this scenario. If no one contradicts me, I'll also post this in the bug reporting system. Wanted to a) get confirmation, if possible before bugging it and b) warn other souls that may be adventurous too! Summary: failings in LVM and kernel(?) seem to make a "freeze" possible. 1) Lvchange --permission=r seems to not take effect until re-boot even though lvdisplay says it has taken effect; 2) Prior to reboot, mount will mount a read-only LV and give no warning that it is read-only and will mount it r/w. The opposite also occurs: if the LV was ro and it is changed to r/w, mount still acts as if read-only is in effect. 3) If these steps are done, *ALL* commands work as if everything is normal *except* "ro" seems to have no effect: - lvchange --permission=r # Seems OK - lvdisplay # Seems OK, says "r" - mount <normal mount args> # Only "t -ext2" extra, no "read # only" warning from mount command - >/mnt/the_mount_point/test # Seems OK, ls shows it - rm /mnt/the_mount_point/test # Seems OK, ls doesn't show it What would happen if I did not umount it here? I guess it would run for at least some time without problem. Then, if LVM truly has it ro, when buffer flush time came there should be some undesirable results. At this point, I issued a umount for the volume and the system froze with blinking keyboard LED. Subsequent re-boot and investigation added the knowledge that the change in lv status was delayed until reboot. Can/will anyone confirm/deny this for me? Thx. Node: Athalon, CentOS-4.3. fully updated, all normal components from base (wine and a few odds and ends from rpmforge). ============ Gory Details Below ====================================== Progressing on LVM education and simplified b/u procedure using it. Covered my butt by setting the lv to read only. Got the hare-brained idea to see what would happen if... >>:-( # Protect fools from themselves. # umount /dev/VolGroupAA/lvol1 # lvchange --permission r VolGroupAA/lvol1 Logical volume "lvol1" changed # lvdisplay VolGroupAA/lvol1 # Edited below to items of interest --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV Write Access read only LV Status available # open 0 LV Size 9.31 GB Current LE 298 Block device 253:3 # Notice: no read-only this mount & no warning from mount command # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 # > /mnt/VolGroupAA_lvol1/test # ls show file created # rm /mnt/VolGroupAA_lvol1/test # ls shows file gone # umount /dev/VolGroupAA/lvol1 # Instant petrification! Purgatory entered: flashing keyboard LED and the usual three-fingered salute and destructive pounding on attached peripherals had the expected results! NADA! Googled here (it wrapped, sorry) http://groups.google.com/groups/search?hl=en&lr=&q=read-only+mount +write+LVM2+kernel+2.6+2006+lock+OR+crash&qt_s=Search Didn't see anything that looks like it. Saw a drbd related elsewhere that might come close... but NOPE! Anyway, since it seems (according to the HOWTO) that only mailing list activities report and address bugs (didn't see a bugzilla: did I look too casually?) I would like to confirm this is not peculiar to my node. I prefer not to subscribe to another list just to belatedly discover nothing of value after searching their archives too! If anyone else has a test machine and time, I will take the trouble to report this if it is confirmed. Subsequent reboot and test from the console gave this surprise. # lvchange --permission rw VolGroupAA/lvol1 Logical volume "lvol1" changed # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 mount: block device /dev/VolGroupAA/lvol1 is write-protected, mounting read-only # There I realized that the status change was not propagated to the system until a re-boot. Later I tried adding a "lvchange --refresh" although the docs didn't seem promising. It had no effect. Confiming again, re-booted and did this. Note the read/write access. # lvdisplay /dev/VolGroupAA/lvol1 --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV UUID jDoW7T-e7IS-Z5Zd-F1lG-3E6S-DvDl-bxYq7d LV Write Access read/write LV Status available # open 0 LV Size 9.31 GB Current LE 298 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:3 # lvchange --permission r VolGroupAA/lvol1 Logical volume "lvol1" changed # lvdisplay /dev/VolGroupAA/lvol1 --- Logical volume --- LV Name /dev/VolGroupAA/lvol1 VG Name VolGroupAA LV UUID jDoW7T-e7IS-Z5Zd-F1lG-3E6S-DvDl-bxYq7d LV Write Access read only LV Status available # open 0 LV Size 9.31 GB Current LE 298 Segments 1 Allocation inherit Read ahead sectors 0 Block device 253:3 # mount -t ext2 /dev/VolGroupAA/lvol1 /mnt/VolGroupAA_lvol1 # Note: no warning about read-only issued. # mount <snip uninteresting stuff> /dev/mapper/VolGroupAA-lvol1 on /mnt/VolGroupAA_lvol1 type ext2 (rw) # >/mnt/VolGroupAA_lvol1/test # ls -ltr /mnt/VolGroupAA_lvol1 total 6486852 -rw-r--r-- 1 <snip> 290155835 Jul 25 12:25 ImportedHardDisks.tar.bz2 drwx------ 2 <snip> 16384 Jul 25 16:53 lost+found -rw-r--r-- 1 <snip> 6345862846 Jul 25 20:49 TestDisk_Test.tar.bz2 -rw-r--r-- 1 root root 0 Jul 27 11:56 test # umount here will lock machine. I'll finish mail first. TIA -- Bill

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss