Discuss

discuss@lists.centos.org

34758 discussions

xendomains not starting at boot
by Theo Band 31 Aug '11

31 Aug '11

On one of my xen hosts a virtual machine does not start at boot. I can see that xendomains gives an error: service xendomains start Starting auto Xen domains: fszeleNo handlers could be found for logger "xend" Error: Disk isn't accessible No handlers could be found for logger "xend" Error: Disk isn't accessible An error occured while creating domain fszele: Usage: xm create <ConfigFile> [options] [vars] Create a domain based on <ConfigFile>. Options: -h, --help Print this help. --help_config Print the available configuration variables (vars) for the configuration script. -q, --quiet Quiet. --path=PATH Search path for configuration scripts. The value of PATH is a colon-separated directory list. -f=FILE, --defconfig=FILE Use the given Python configuration script.The configuration script is loaded after arguments have been processed. Each command-line option sets a configuration variable named after its long option name, and these variables are placed in the environment of the script before it is loaded. Variables for options that may be repeated have list values. Other variables can be set using VAR=VAL on the command line. After the script is loaded, option values that were not set on the command line are replaced by the values set in the script. -F=FILE, --config=FILE Domain configuration to use (SXP). SXP is the underlying configuration format used by Xen. SXP configurations can be hand-written or generated from Python configuration scripts, using the -n (dryrun) option to print the configuration. -n, --dryrun Dry run - prints the resulting configuration in SXP but does not create the domain. -p, --paused Leave the domain paused after it is created. -c, --console_autoconnect Connect to the console after the domain is created. ! [failed] [FAILED] The actual command executed turns out to be: XMC=`xm create --quiet --defconfig $dom` where dom=/etc/xen/auto/fszele If I issue the command from the command line, the dom starts as expected. After some debugging on /etc/init.d/xendomains it turns out to work if I change this line: diff xendomains* 283c283 < XMC=$(xm create --quiet --defconfig $dom) --- > XMC=`xm create --quiet --defconfig $dom` or diff xendomains* 283c283 < XMC=`echo debug;xm create --quiet --defconfig $dom` --- > XMC=`xm create --quiet --defconfig $dom` So I fixed the problem using $() instead of back-ticks, but I like to understand what can be the root cause of this problem. It seems to happen on only one of my hosts. cat /etc/redhat-release CentOS release 5.6 (Final) rpm -qf xendomains xen-3.0.3-120.el5_6.3 uname -a Linux xenzele.greenpeak.com 2.6.18-238.19.1.el5xen #1 SMP Fri Jul 15 08:16:59 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux Theo

1 0

Apache warns Web server admins of DoS attack tool
by m.roth＠5-cent.us 31 Aug '11

31 Aug '11

Anyone have any idea how soon RHEL and CentOS will be releasing the patch package? Excerpt: Computerworld - Developers of the Apache open-source project today warned users of the popular Web server software that a denial-of-service (DoS) tool is circulating that exploits a bug in the program. The tool, called "Apache Killer," showed up last Friday in a post to the "Full Disclosure" security mailing list. Today, the Apache project acknowledged the vulnerability that the attack tool exploits, and said it would release a fix for Apache 2.0 and 2.2 in the next 48 hours. --- end excerpt --- <http://www.computerworld.com/s/article/9219471/Apache_warns_Web_server_admi…> mark

16 52

selinux & iptables
by Michael D. Berger 30 Aug '11

30 Aug '11

In setting up my new CentOS 6 laptop, I replaced /etc/sysconfig/iptables with my own, very restrictive version. I then tried to restart the iptables daemon, but it reported that my new iptables was unreadable. On a guess, I disabled selinux, and my problem was solved. Later, I re-enabled selinux and on reboot, it had to go through a very long setup procedure. Is there something better I could have done when replacing iptables, so that I would not have to disable selinux? Thanks for your help. Mike.

5 4

6.0 Media problems
by ken 30 Aug '11

30 Aug '11

When I downloaded the iso for 6.0 install, K3b said the iso wouldn't fit on the blank DVD. So I downloaded and burned the LiveDVD. When I boot it, I get the blue splash screen (it says "CentOS... Community Enterprise OS on the bottom, logo to the right), but nothing else comes up. Hitting various keys does nothing. Downloaded and burned the Netinstall CD. It gives an error message that it can't install because the machine's CPU doesn't have pae. So is it the end of CentOS/RH for this machine? (I can't believe that. One of the great things about Linux has always been that it'll run on old hardware.) Or are these fixable problems? Or are there workarounds? Or should I go for a different distribution? -- War is a failure of the imagination. --William Blake

10 26

Secure a python http server
by admin lewis 30 Aug '11

30 Aug '11

Hi, I want to make secure my python http server.. what should i use ? chroot ? there are something more secure ? On my centos server I've SE enabled..then .. sandboxing ? Thanks very much lewis -- Linux and Windows 2003/2008 Server. http://predellino.blogspot.com/

2 2

change LUKS filesystem password
by ken 30 Aug '11

30 Aug '11

How do you change the LUKS filesystem password?

4 3

CentOS-announce Digest, Vol 78, Issue 6
by centos-announce-request＠centos.org 30 Aug '11

30 Aug '11

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. CEEA-2011:1214 CentOS 4 i386 tzdata update (Tru Huynh) 2. CEEA-2011:1214 CentOS 4 x86_64 tzdata update (Tru Huynh) 3. CESA-2011:1219 Moderate CentOS 4 i386 samba - security update (Tru Huynh) 4. CESA-2011:1219 Moderate CentOS 4 x86_64 samba - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 29 Aug 2011 23:11:43 +0200 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CEEA-2011:1214 CentOS 4 i386 tzdata update To: centos-announce(a)centos.org Message-ID: <20110829211143.GA25427(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Enhancement Advisory CEEA-2011:1214 tzdata bugfix update for CentOS 4 i386: https://rhn.redhat.com/errata/RHEA-2011-1214.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/tzdata-2011h-2.el4.noarch.rpm source: updates/SRPMS/tzdata-2011h-2.el4.src.rpm You may update your CentOS-4 i386 installations by running the command: yum update tzdata Tru -- Tru Huynh (mirrors, CentOS i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

Upstart file format
by Michael D. Berger 30 Aug '11

30 Aug '11

Where can I find documentation on the new format of the files in /etc/init.d/? Thanks, Mike.

5 7

resize2fs
by Ed Morrison 30 Aug '11

30 Aug '11

Hi All: I am trying to resize a centos (5.2) VM drive. I use VMware and I have increased the size of the drive by 40G. I am running resize2fs on /dev/sdb1 (which is my root partition) but when I do I get this error: [root@centos ~]# resize2fs /dev/sdb1 120G resize2fs 1.39 (29-May-2006) The containing partition (or device) is only 19970795 (4k) blocks. You requested a new size of 31457280 blocks. How can I change the block size? I have also tried to use gparted live cd but it will not allow me to increase the size even though it sees 40g of unused space. I can only create a new partition. Any help would be appreciated. Thanks, Ed

4 3

Installing 6.0 via USB
by Kenneth Porter 30 Aug '11

30 Aug '11

I'm using LiveUSB-Creator to create a bootable USB drive from CentOS-6.0-i386-netinstall.iso, and it gives me an error at startup: vesamenu.c32: Not a COM32R image I can hit tab and select "linux" and then it loads vmlinux and the initrd, says "Ready", and then just hangs. I'm not sure what's supposed to happen next. "vesa" and "rescue" do the same thing. The error message above apparently is caused by the syslinux in the ISO not matching the one that LiveUSB-Creator installs to boot from: <https://bugzilla.redhat.com/show_bug.cgi?id=662557> The system has 512 MB of memory. Is that enough to boot the installer?

3 3

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