Discuss February 2009

discuss@lists.centos.org

251 participants
224 discussions

Lost konqueror navigation
by Anne Wilson 17 Feb '09

17 Feb '09

I still have some outstanding problems caused by the recent power problems. All my ~/.kde ended up in lost+found, identified by numbered folders. I've gradually managed to trace the origin of all the files and returned them to their correct place. However a few may have been lost, as there are no files left and I still have some problems. I'll post them in separate threads. When I launch konqueror as user I have no Main or Location toolbar. Also, my menu options are Settings, Help, Edit, View and Tools, in that order. Location, Go, Bookmarks and Window are missing. If I knew what provides these I could copy them from another account. Can anyone help, please? Anne

1 0

There was a crash during the distribution installation over PXE using kickstart
by Dotan Barak 17 Feb '09

17 Feb '09

Hi. I configured a remote machine to allow network installation when the machine is being loaded with PXE. I'm using an x86_64 desktop. The installation is almost fully automated with a kickstart file. I enabled PXE in the BIOS, started the installation and in the middle of the installation, i got a crash which reported an error. I opened a bug on this issue: http://bugs.centos.org/view.php?id=3394. Someone, called Tru, kindly gave me the following answer: from your logs: File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1045, in handleRenderCallback self.currentWindow.renderCallback() IOError: [Errno 30] Read-only file system ... which was caused by: <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown ... <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <4>end_request: I/O error, dev hda, sector 344757 <3>hda: no DRQ after issuing MULTWRITE_EXT <4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command .... 4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command <4>ide0: reset: success <3>Aborting journal on device dm-0. <2>ext3_abort called. <2>EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal <2>Remounting filesystem read-only Issue History Date Modified Username Field Change ====================================================================== 2009-02-17 11:30dotan_bar New Issue 2009-02-17 11:30dotan_bar File Added: bug_report.txt 2009-02-17 11:34dotan_bar File Added: default.ks 2009-02-17 11:35dotan_bar Note Added: 0008711 2009-02-17 12:20tru Note Added: 0008713 ====================================================================== Reply Forward noreply(a)centos.org to me show details 2:21 PM (1 hour ago) Reply The following issue has been CLOSED ====================================================================== http://bugs.centos.org/view.php?id=3394 ====================================================================== Reported By: dotan_bar Assigned To: ====================================================================== Project: CentOS-5 Issue ID: 3394 Category: -OTHER Reproducibility: unable to reproduce Severity: crash Priority: normal Status: closed Resolution: open Fixed in Version: ====================================================================== Date Submitted: 2009-02-17 11:30 UTC Last Modified: 2009-02-17 12:21 UTC - Show quoted text - ====================================================================== Summary: There was a crash during the distribution installation over PXE using kickstart Description: I configured a remote machine to allow network installation when the machine is being loaded with PXE. The installation is almost fully automated with a kickstart file. I enabled PXE in the BIOS, started the installation and in the middle of the installation, i got a crash which reported an error. I'm using x86_64 desktop. ====================================================================== ---------------------------------------------------------------------- dotan_bar - 2009-02-17 11:35 ---------------------------------------------------------------------- I attached the kick-start file too. ---------------------------------------------------------------------- tru - 2009-02-17 12:20 ---------------------------------------------------------------------- from your logs: File "/usr/lib/anaconda/iw/progress_gui.py", line 243, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 1045, in handleRenderCallback self.currentWindow.renderCallback() IOError: [Errno 30] Read-only file system ... which was caused by: <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <3>hda: no DRQ after issuing MULTWRITE_EXT <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown ... <4>ide0: reset: success <4>hda: status timeout: status=0xd0 { Busy } <4>ide: failed opcode was: unknown <4>end_request: I/O error, dev hda, sector 344757 <3>hda: no DRQ after issuing MULTWRITE_EXT <4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command .... 4>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest } <4>ide: failed opcode was: unknown <3>hda: drive not ready for command <4>ide0: reset: success <3>Aborting journal on device dm-0. <2>ext3_abort called. <2>EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted journal <2>Remounting filesystem read-only ---------------------------------------------------------------------- tru - 2009-02-17 12:21 ---------------------------------------------------------------------- OP hardware error, not a bug. This is not a support system, but a bug tracker. Please take your questions to either the centos mailing list or the forums. Can anyone help me with this issue? Thanks Dotan

3 3

Re: [CentOS] clamAV problem
by Mail List 17 Feb '09

17 Feb '09

Anne Wilson wrote: > "Clamd successfully notified about the update." > > I hate being beaten! :-) I simply removed the line that mentioned a local > socket. So simple, and so easily missed. Yes, it probably wasn't enabled by > default, but by misunderstanding. > > Thanks to all who helped. > > Anne Anne, Just for the record, I just installed the base packages of clamav, clamav-db using the rpmforge repo on a test machine. The option ... # Send the RELOAD command to clamd. # Default: no NotifyClamd /etc/clamd.conf Is enabled by default. So you did by no means break it. That is it's expected behavior. Also please not that in /etc/cron.daily/freshclam you will have the same option enabled, as follows /usr/bin/freshclam \ --quiet \ --datadir="/var/clamav" \ --log="$LOG_FILE" \ --log-verbose \ --daemon-notify="/etc/clamd.conf" So no you did not break it. it was turned on by default. Brian -- http://wx.Tatorz.com Open WebMail Project (http://openwebmail.org) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

3 2

clamAV problem
by Anne Wilson 17 Feb '09

17 Feb '09

Since my power problems that resulted in a re-install I have a problem which I've failed to locate up to now. The logs show daily.cld updated (version: 8950, sigs: 72593, f-level: 38, builder: ccordes) Database updated (510565 signatures) from db.gb.clamav.net (IP: 163.1.3.8) WARNING: Clamd was NOT notified: Can't connect to clamd through /tmp/clamd.socket I've been through the config files, but obviously there is something in the setup that I've failed to do. Scans are running every night, but service clamd status clamd: unrecognized service It has to be something stupid that I've missed. Can someone kick me in the right direction? Thanks Anne

7 13

MySql server on Centos 5
by Blaž Bogataj 17 Feb '09

17 Feb '09

I have a question about Mysql. I use mysql 5.0.68 on Centos 4 from Centos plus repository. The old hardware steers me to Centos 5, however there is mysql 5.0.45. Some program solutions which we are using on the old server (production for 500 users) do not work properly on new one (some querys producing reports). Is there a source where I can find version for Centos 5 server equal to the Mysql version which I run on the old server. I'd like to use some kind of repository. Looking forward for sugesstions. Blaž

4 4

Suggestion for Server Room monitoring
by Fajar Priyanto 17 Feb '09

17 Feb '09

Hi all, I have a situation like this: Our little server room is always on. It has an air conditioning unit, but barely enough. So sometimes during weekend, the temperature could reach unhealthy level, like 29 degree Celsius. Currently, there's no personnel to monitor it 24 hours a day. I'm thinking of using a tool to monitor the temperature, and then send sms/email when it reaches certain threshold. Anyone has an idea? Could be software based or hardware one. Thank you.

14 16

kickstart driverdisk
by Jerry Geis 17 Feb '09

17 Feb '09

Hi guys, I have my driverdisk created and the files are on a USB pendrive. How do I make the USB pendrive /dev/sdb and not /dev/sda??? I am wanting the installation to take place on sda and the driver disk to be sdb? My driver disk is a network driver disk, r8168. Jerry

3 2

Re: [CentOS] Practical experience with NTLM/Windows Integrated Authentication [Apache]
by Kanwar Ranbir Sandhu 16 Feb '09

16 Feb '09

On Mon, 2009-02-16 at 09:13 +0100, Sorin Srbu wrote: > Probably not, but I was thinking there may be some obscure package somewhere > on the 'net to do this. There is - I found it last year, and it works. I have everything on my work PC, so I'll let the list know tomorrow or later this week. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.27.12-170.2.5.fc10.x86_64 x86_64 GNU/Linux 17:54:53 up 5 days, 19:41, 3 users, load average: 1.20, 1.70, 1.14

2 1

ipsec net-to-net problem
by brad＠bradandkim.net 16 Feb '09

16 Feb '09

I am trying to set up an ipsec net-to-net VPN and am having problems. Here is a diagram of the setup: LAN A --> Host A ----> Internet <---- Host B <-- LAN B LAN A = 10.10.2.0/24 LAN A gateway = 10.10.2.254 Host A internal = 10.10.2.254 Host A external = xx.xx.xx.xx Host B external (see below) Host B internal = 10.10.1.10 LAN B = 10.10.1.0/24 LAN B gateway = 10.10.1.252 (F5 Big IP) Host A is CentOS5 and is a router/firewall for LAN A. Host B is RHEL4 and does not have a public IP. It is behind an F5 BigIP and the BigIP forwards all traffic for yy.yy.yy.yy to Host B. Likewise it masks Host B's outbound traffic as yy.yy.yy.yy. I can get this tunnel to come up but seem to be having problems on the Host A side. If I run 'tcpdump |grep -i esp' on Host A and ping a host on LAN A from a host on LAN B (whose routing table was adjusted to go through Host B for the 10.10.2.0 network), I see ESP traffic on Host A: AH(spi=0x04c98137,seq=0x3): IP 10.10.1.10 > xx.xx.xx.xx: ESP(spi=0x07b6bcd3,seq=0x3), length 116 (ipip-proto-4) If I ping a host on LAN B from a host on LAN A I don't see any ESP traffic on either Host A or Host B and the host doing the ping gets a 'Destination Host Unreachable'. It seems like a problem with the routing on Host A. Here is the result of setkey -D on both hosts: Host A: xx.xx.xx.xx yy.yy.yy.yy esp mode=tunnel spi=169285624(0x0a1717f8) reqid=0(0x00000000) E: 3des-cbc ce370c79 68e74da7 79ba58b9 1605f149 f3e98e5b 9984da9b A: hmac-sha1 ea9dba47 cf6a4c04 7e949d4f a8f304f0 76e006c7 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:46:01 2009 current: Feb 16 12:47:13 2009 diff: 72(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=3 pid=5198 refcnt=0 xx.xx.xx.xx yy.yy.yy.yy ah mode=tunnel spi=173186772(0x0a529ed4) reqid=0(0x00000000) A: hmac-sha1 82aaec77 11dfb67c 7fbb7f7c 152c2764 4445ad8e seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:46:01 2009 current: Feb 16 12:47:13 2009 diff: 72(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=2 pid=5198 refcnt=0 yy.yy.yy.yy xx.xx.xx.xx esp mode=tunnel spi=166536016(0x09ed2350) reqid=0(0x00000000) E: 3des-cbc b63a5538 c6a2dd3b f449df6e c594cd16 644a59d4 cb45dfef A: hmac-sha1 5d8d015c f8e8e12f d117dc5b fc64d2ed f3ca79b5 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:46:01 2009 current: Feb 16 12:47:13 2009 diff: 72(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=1 pid=5198 refcnt=0 yy.yy.yy.yy xx.xx.xx.xx ah mode=tunnel spi=84103999(0x0503533f) reqid=0(0x00000000) A: hmac-sha1 022dbd45 248b1ffa 05d94068 22e3c530 5485a468 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:46:01 2009 current: Feb 16 12:47:13 2009 diff: 72(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=0 pid=5198 refcnt=0 Host B: xx.xx.xx.xx 10.10.1.10 esp mode=tunnel spi=169285624(0x0a1717f8) reqid=0(0x00000000) E: 3des-cbc ce370c79 68e74da7 79ba58b9 1605f149 f3e98e5b 9984da9b A: hmac-sha1 ea9dba47 cf6a4c04 7e949d4f a8f304f0 76e006c7 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:45:57 2009 current: Feb 16 12:47:35 2009 diff: 98(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=3 pid=15049 refcnt=0 xx.xx.xx.xx 10.10.1.10 ah mode=tunnel spi=173186772(0x0a529ed4) reqid=0(0x00000000) A: hmac-sha1 82aaec77 11dfb67c 7fbb7f7c 152c2764 4445ad8e seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:45:57 2009 current: Feb 16 12:47:35 2009 diff: 98(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=2 pid=15049 refcnt=0 10.10.1.10 xx.xx.xx.xx esp mode=tunnel spi=166536016(0x09ed2350) reqid=0(0x00000000) E: 3des-cbc b63a5538 c6a2dd3b f449df6e c594cd16 644a59d4 cb45dfef A: hmac-sha1 5d8d015c f8e8e12f d117dc5b fc64d2ed f3ca79b5 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:45:57 2009 current: Feb 16 12:47:35 2009 diff: 98(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=1 pid=15049 refcnt=0 10.10.1.10 xx.xx.xx.xx ah mode=tunnel spi=84103999(0x0503533f) reqid=0(0x00000000) A: hmac-sha1 022dbd45 248b1ffa 05d94068 22e3c530 5485a468 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Feb 16 12:45:57 2009 current: Feb 16 12:47:35 2009 diff: 98(s) hard: 3600(s) soft: 2880(s) last: hard: 0(s) soft: 0(s) current: 0(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 0 hard: 0 soft: 0 sadb_seq=0 pid=15049 refcnt=0 Here are the ifcfg-ipsec files for each host. Host A: TYPE=IPSEC ONBOOT=NO IKE_METHOD=PSK SRCGW=10.10.2.254 DSTGW=10.10.1.10 SRCNET=10.10.2.0/24 DSTNET=10.10.1.0/24 DST=yy.yy.yy.yy Host B: TYPE=IPSEC ONBOOT=no IKE_METHOD=PSK SRCGW=10.10.1.10 DSTGW=10.10.2.254 SRCNET=10.10.1.0/24 DSTNET=10.10.2.0/24 DST=xx.xx.xx.xx Here are the routes from each host. Host A: 10.10.1.0 10.10.2.254 255.255.255.0 UG 0 0 0 eth1 Host B: 10.10.2.0 yy.yy.yy.yy 255.255.255.0 UG 0 0 0 bond0 Let me know if I should post the racoon.conf files. Thanks, Brad

1 0

INIT: Id "snmp" respawning too fast: disabled for 5 minutes
by David Halik 16 Feb '09

16 Feb '09

Hello all, I recently started seeing these messages on the consoles of three production Centos 5.2 servers. They have been occurring nonstop for the past few days and show up routinely every five minutes. INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes INIT: Id "snmp" respawning too fast: disabled for 5 minutes Despite trying to debug this and googling for the last couple of hours, I haven't had any luck as to why the errors are generated or how to fix them. There are a ton of posts on the web related to other Id's, such as various tty ports and "x", but I haven't seen a single thing related to "snmp". The answer usually seems to be that there are misconfigured lines in /etc/inittab, but in my case there is nothing even remotely related to "Id snmp" in inittab. The make matters more confusing, snmp isn't installed or being used on these machines. I doubled checked and the extent of any snmp packages are these two: # rpm -qa | grep -i snmp perl-Net-SNMP-5.2.0-1.2.el5.rf net-snmp-libs-5.3.1-24.el5_2.1 Both only contain a couple of libraries, so I hardly believe they have anything to do with it. According to what I've learned, this error is usually generated when init tries to continually respawn a process that dies immediately... but as to what process it could possible be I have no idea. I even tried to strace init (-p1), but apparently this is a forbidden operation: # strace -p1 attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted That's a shame too, but at least I could see what init is trying to do. Any ideas? I'm just about stumped as to how to proceed at this point. Thanks in advance. -- ================================ David Halik System Administrator OIT-CSS Rutgers University dhalik(a)jla.rutgers.edu ================================

2 3

← Newer
1
...
8
9
10
11
12
13
14
...
23
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 February 2009