Discuss March 2007

discuss@lists.centos.org

337 participants
401 discussions

Centos 4 on Terminator C3
by centos＠911networks.com 18 Mar '07

18 Mar '07

I am trying to install Centos 4 on an Asus terminator c3 with the via chipset. It keeps on rebooting. It won't install. It's a P3 800Mhz made by Via with 512Mb RAM. I have searched and found nothing about it. Any suggestion? -- Thanks

1 0

This firewall rule will self-destruct
by Benjamin Smith 18 Mar '07

18 Mar '07

Ok, I have a challenge - get two services working over a single port. (!) Sometimes it's a web service, sometimes it's a VNC service. Here's what I had in mind: 1) Server is normally a webserver listening on port 80, and normally has the following rules active: # iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # iptables -t nat -A POSTROUTING -j MASQUERADE 2) Server hosts a special PHP script, that when called correctly, sets rules like # iptables -I PREROUTING -p tcp -s $REMOTE --dport 80 -j DNAT --to-destination $FWIP:$FWPORT # iptables -I FORWARD -p tcp -s $REMOTE --dport 80 -j ACCEPT The *next* tcp connection from their computer to the webserver will get NAT'd to service $FWIP:$FWPORT. But I want this rule cleared out as soon as the connection is made with the latter altered rules. Is there a way to write a rule or set of rules that, when activated, then delete themselves? The "ESTABLISHED,RELATED" rule should keep the connection alive even after the latter rules are killed, right? Is this possible? Am I just out in left field?

3 6

"No space left on device" but there is space
by Leonardo Vilela Pinheiro 17 Mar '07

17 Mar '07

Hi, I've been receiving message "No space left on device" but there is space. I've forced fsck on reboot 2 times but did not solve. # yum rpmdb: /var/lib/rpm/__db.001: No space left on device error: db4 error(28) from dbenv->open: No space left on device error: cannot open Packages index using db3 - No space left on device (28) error: cannot open Packages database in /var/lib/rpm Traceback (most recent call last): <...> # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol01 5.0G 3.6G 1.2G 76% /var /dev/mapper/VolGroup00-LogVol04 1008M 456M 501M 48% /var/log /dev/mapper/VolGroup00-web 4.9G 140M 4.5G 3% /var/www # mount /dev/mapper/VolGroup00-LogVol01 on /var type ext3 (rw) /dev/mapper/VolGroup00-LogVol04 on /var/log type ext3 (rw) /dev/mapper/VolGroup00-web on /var/www type ext3 (rw) # touch /var/test touch: cannot touch `/var/test': No space left on device # mkdir /var/hello mkdir: cannot create directory `/var/hello': No space left on device Please help. Thanks Leonardo

6 7

CentOS-4.3 Install Fails
by Charles Sliger 17 Mar '07

17 Mar '07

I'm using the same CD's that I've used to install CentOS on my other systems. After the first failure I had the installation verify the install media just in case. It passed. I've tried the default install (used for all previous installs) and the i586 option (after googling). They both fail in the same way. Here is a transcript of what is output to the screen: Running anaconda, the CentOS-4 i386 system installer - please wait. Could not find platform independent libraries <prefix> Could not find platform independent libraries <exec_prefix> Consider setting $PYTHONHOME to <prefix>[:exec_prefix] 'import site' failed ; use -v for traceback Traceback (most recent call last): File "/usr/bin/anaconda", line 28, in ? import sys, os ImportError: No module named os install exited abnormally sending termination signals.done sending kill signals.done disabling swap. unmounting filesystems. /mnt/runtime done disabling /dev/loop0 /proc/bus/usb done /proc done /dev/pts done /sys done /tmp/ramfs done /mnt/source done /selinux done you may safely reboot your system Motherboard Intel D945GCL CPU Intel Pentium-4 631 RAM Aeneon 512 Mb 240-pin DDR2 SDRAM DIMM - DDR2 667 PATA Disk IBM 40 Gb PATA Disk (DeskStar) - System Disk SATA Disk Hitachi 80 Gb SATA Disk (DeskStar) - Backup Disk Disk Carrier Vantec MRK-200ST-BK Case Antec TX1050B The system disk (IBM 40Gb DeskStar) was used in a previous system ad has CentOS-4.3 loaded on it. It won't boot in graphical mode due to an X-Windows failure. So I decided to re-install. Any insight would be appreciated. Charles L. Sliger, Information Systems Engineer, chaz(a)bctonline.com "No matter where you go, there you are..."

4 3

Re: [CentOS] sendmail and rbl blocking - generating statistics
by Ryan Simpkins 17 Mar '07

17 Mar '07

On Wed, March 14, 2007 14:08, Will McDonald wrote (trimmed): > On 14/03/07, Ryan Simpkins <centos(a)ryansimpkins.com> wrote: >> Try doing a simple 'cat /var/log/maillog | grep -c check_relay' > > You can avoid the unnecessary 'cat' by just passing the filename to grep directly: > > # grep -c 'checK_relay.*spamhaus' /var/log/maillog > # grep -c 'checK_relay.*spamcop' /var/log/maillog > # grep -c 'checK_relay.*njabl' /var/log/maillog > > Would probably be more efficient and faster, you can test with 'time' to verify this. You're spawning one process 'grep', instead of three seperate processes, 'cat, 'grep' and 'grep' again. Am I using time right to measure it? # time cat /var/log/maillog | grep check_relay | grep -c njabl 8 real 0m0.299s user 0m0.289s sys 0m0.009s # time grep -c 'check_relay.*njabl' /var/log/maillog 8 real 0m0.404s user 0m0.402s sys 0m0.000s Is the first 'time' measuring the whole one-liner, or just the time it takes to 'cat'? I also tried this: time echo `cat /var/log/maillog | grep check_relay | grep -c njabl` 8 real 0m0.325s user 0m0.312s sys 0m0.012s time echo `grep -c 'check_relay.*njabl' /var/log/maillog` 8 real 0m0.411s user 0m0.408s sys 0m0.002s I ran these several times mixed back and forth to try and see if they were flukes, these numbers appear to be representitive of the average. What do you get on your system? Maybe passing the file name to grep gets faster as the file size increases? wc /var/log/maillog 12323 142894 1588860 /var/log/maillog I wonder if the issue here is actually the 'stuff*morestuff' as that might be a more expensive match: time echo `grep -c 'check_relay' /var/log/maillog | grep njabl` real 0m0.269s user 0m0.263s sys 0m0.006s -Ryan

6 11

no=acpi?
by Filianx 17 Mar '07

17 Mar '07

I have a box running suse 10, i want to change it to CentOS 4. The problem i have is that i had to pass the command no=acpi to install suse, so how do I do this with centos. thanks. -- Filianx

3 2

Joomla RPM for CentOS
by Ed Morrison 16 Mar '07

16 Mar '07

Does anyone know of a joomla rpm for CentOS/Red Hat? I see some rpm's on rpmforge but none are for our OS. Thanks!

2 1

Open Office on CentOS
by Mark Hull-Richter 16 Mar '07

16 Mar '07

I notice that the OO that comes with CentOS 4.4 is version 1.1.5, which is fairly ancient. Are there any plans to update this for OO 2.2, or 2.1, or 2.0? Or is this a RH thing exclusively? In which case is CentOS Plus likely to get a more recent version? OO 2.0 is way better.... Mark Hull-Richter Linux Kernel Engineer (949) 680-3082 - Office (949) 680-3001 - Fax (949) 632-8403 - Mobile mhull-richter(a)datallegro.com <mailto:mhull-richter@datallegro.com> www.datallegro.com <http://www.datallegro.com> 85 Enterprise, Second Floor, Aliso Viejo, CA 92656

2 1

CentOS-announce Digest, Vol 25, Issue 8
by centos-announce-request＠centos.org 16 Mar '07

16 Mar '07

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-2007:0066 Low CentOS 4 ia64 wireshark - security update (Pasi Pirhonen) 2. CESA-2007:0066 Low CentOS 3 ia64 wireshark - security update (Pasi Pirhonen) 3. CESA-2007:0066-01: Low CentOS 2 i386 wireshark security update (John Newbigin) 4. CESA-2007:0077-06: Critical CentOS 2 i386 seamonkey security update (John Newbigin) 5. CESA-2007:0066 Low CentOS 3 s390(x) wireshark - security update (Pasi Pirhonen) 6. CESA-2007:0066 Low CentOS 4 s390(x) wireshark - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Fri, 16 Mar 2007 00:38:44 +0200 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2007:0066 Low CentOS 4 ia64 wireshark - security update To: centos-announce(a)centos.org Message-ID: <20070315223843.GF14147(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2007:0066 https://rhn.redhat.com/errata/RHSA-2007-0066.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/wireshark-0.99.5-EL4.1.ia64.rpm updates/ia64/RPMS/wireshark-gnome-0.99.5-EL4.1.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

RE: [CentOS] Replacing a hard drive
by Bowie Bailey 16 Mar '07

16 Mar '07

John R Pierce wrote: > Bowie Bailey wrote: > > I have a CentOS 4.4 system where all of the main filesystems are on > > a single hard drive. This drive is starting to give some errors, > > so I got a new (larger) drive to replace it with. What is the > > easiest way to copy my filesystems over to the new drive? > > > > I considered using dd, but I lose the extra capacity of the new > > drive that way. > > > > I tried using SystemImager, but it is giving me some errors. > > > > I think the easiest way may be to boot from the LiveCD, recreate the > > partitions, copy the info with rsync and then fix the boot > > partition and grub. Any tips or pointers to a good how-to? > > > > I'm assuming you're using straight ext3 without LVM or raid.... > > I'd probably boot the regular CD into rescue mode, without mounting > the file systems, then partition the new disk to suit (making each > partition at least as large as the original drive, and in the same > order, then run something like.... > > this assumes new drive is hda, old drive is hdb > > mkdir /mnt/src /mnt/dst > for f in 1 2 5 6; do > mount /dev/hdb$f /mnt/src > mount /dev/hda$f /mnt/dst > dump 0f - /mnt/src | (cd /mnt/dst; restore rf - ) > umount /mnt/dst /mnt/src > end > mkswap /dev/hda3 > mount /dev/hda2 /mnt/dst && mount /dev/hda1 /mnt/dst/boot > chroot /mnt/dst > grub-install /dev/hda > ^z > umount /mnt/dsk/boot; umount /mnt/dsk > > adjust file and device names to suit. dump to restore like that > creates a very accurate copy of a file system, complete with special > files, links, ACLs, permissions, etc, etc intact. > > now, swap the new drive > > > (where 1, 2, 5, 6 are your file system partitions, leaving out your > swap which I'm guessing is hda3) I attempted this method with a few modifications and I'm mostly done. I partitioned the new drive and created the filesystems. I then mounted them one by one and copied the information over. There is a bad inode that caused 'dump' to crash, so I used 'rsync -a' to make the copy instead. When I tried to do the 'chroot' and 'grub-install', grub complained that it didn't have a device file (which it didn't, /dev/ was empty). So I copied the '/dev/hda*' files from the rescue environment to the destination hard drive and tried again. This time, the 'grub-install' ran fine. Now the problem is that when I try to boot, I get the world's worst error message: "GRUB GRUB GRUB...". I read that this can be fixed by setting your bios to manual rather than auto for the hard drives, but that didn't work for me. What else can I do? I think everything is copied to the new drive, I just need to convince it to boot. -- Bowie

1 0

← Newer
1
...
20
21
22
23
24
25
26
...
41
Older →

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 March 2007