Discuss September 2008

discuss@lists.centos.org

264 participants
315 discussions

OT: Migration from Evolution to Thunderbird (Thunderbird mbox files)
by Lanny Marcus 08 Sep '08

08 Sep '08

Background is that I have been using Evolution for my MUA for a number of years. Migrated to Evolution from Mozilla Mail. I only use Evolution for email and contacts. Getting bored with the issues (frequently not being able to exit and needing to kill it; Bug Buddy popping up in GNOME, etc) that Mark (MHR) and I and I'm sure others have experienced. About 24 hours ago, I installed Thunderbird (on CentOS 5.2 32 bit) and am testing it with this mailing list. So far, Thunderbird doesn't seem to have any issues, based on this very quick trial. The Thunderbird documentation says that it uses mbox files, but if so, where_are_they? Here's what it says: > http://www.mozilla.org/support/thunderbird/faq#import > > Thunderbird's mail files are in the standard plain text "mbox" format, which almost all mail programs can use or import. Many proprietary mail programs have a function to import from Eudora, which also uses the "mbox" format; this function should read your Mozilla mail files properly. > > Your mail files are inside your profile (see the Profile Folder), in the Mail and (if you use IMAP) ImapMail folders. Each mail folder (Inbox, Sent, etc.) is stored as two files — one with no extension (e.g. INBOX), which is the mail file itself (in "mbox" format), and one with an .msf extension (e.g. INBOX.msf), which is the index (Mail Summary File) to the mail file. Tell the other program to import mail from the file with no extension. However, in the imap.gmail.com folder INBOX.msf file properties, Type is shown as C source code and MIME type is shown as text/x-csrc and I cannot find the mbox files.... In Evolution: Inbox has type: Mailbox file and is shown as MIME type: application/mbox If someone on the list can point me to where the mbox files for Thunderbird on Linux are located, that will be much appreciated. I do not want to migrate from Evolution to Thunderbird, unless my email will continue to be in the mbox format, in case I eventually decide to migrate from Thunderbird, to another MUA. TIA!

6 18

check mal server speed n performance
by fabian dacunha 08 Sep '08

08 Sep '08

Dear All, I have Centos 5.1 and sendmail mail server running for over a year and been workin fine i also use mailscanner + clamav now some remote users have been complaing that the mail sometimes time out i have even tried to stop the mail scanner and jus test my sendmail but the problem exists now i would apprecite if someone cd help me or let me know of a link where i could test the mail server performance and know if its working fine so to rule out the possibility of any problem with my mail server software the mail logs r normall and dont show any different thing thanks and regards apprecite ur help regards Fabian -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 4

Weird TCP problem
by Gordon Messmer 08 Sep '08

08 Sep '08

Last week, I started seeing very strange behavior in one of the networks that I manage. The office LAN uses a Linux firewall which masquerades their workstations over their DSL connection. There are probably ~75 workstations in the office LAN. Their mail server is in a collocated facility nearby. That server has an RFC1918 address; its router does SNAT to forward packets to the system. Both the office firewall and the mail server are currently running fully patched CentOS 5.2. Here's the weird part: If a machine running Linux in the office lan attempts to connect to the mail server on any TCP port, there's a small chance that the server will simply ignore the SYN packets. It doesn't log any errors. If I'm running tcpdump, I see the incoming SYN packets, but no reply. If I use iptables to log the packets, information about the packet is saved in the messages file. If I capture the packets and use wireshark to analyze them, I don't see anything odd: the checksums are good and I can't see any difference between a SYN packet that gets a SYN+ACK and one that's ignored (beyond the obvious: different timestamps and checksums). The problem doesn't seem to affect Windows workstations in the office LAN. As far as I can tell, only SYN packets are dropped. I don't see delays in established connections. I've attached a file that contains, first, the output of tcpdump which shows packets to or from the office's firewall address, as recorded by the destination server. The first four SYN packets are ignored, but the kernel proceeds with the TCP handshake after the fifth SYN packet. Second, the file contains the log messages which are recorded as a result of these iptables rules: iptables -A INPUT -p tcp -s officefw --dport 22 -j LOG iptables -A INPUT -p tcp -s officefw --dport 22 -j ACCEPT Those are the only iptables rules present on the server accepting the connections. Both of those appear to indicate that the server in the colo facility is receiving the SYN packets. What possible reasons are there that it would not reply with SYN+ACK? 19:08:43.751579 IP officefw.57948 > remoteserver.ssh: S 3347102294:3347102294(0) win 5840 <mss1460,sackOK,timestamp 2705398041 0,nop,wscale 7> 19:08:46.751136 IP officefw.57948 > remoteserver.ssh: S 3347102294:3347102294(0) win 5840 <mss1460,sackOK,timestamp 2705401041 0,nop,wscale 7> 19:08:52.749305 IP officefw.57948 > remoteserver.ssh: S 3347102294:3347102294(0) win 5840 <mss1460,sackOK,timestamp 2705407041 0,nop,wscale 7> 19:09:04.747287 IP officefw.57948 > remoteserver.ssh: S 3347102294:3347102294(0) win 5840 <mss1460,sackOK,timestamp 2705419041 0,nop,wscale 7> 19:09:28.741854 IP officefw.57948 > remoteserver.ssh: S 3347102294:3347102294(0) win 5840 <mss1460,sackOK,timestamp 2705443041 0,nop,wscale 7> 19:09:28.742540 IP remoteserver.ssh > officefw.57948: S 3324501337:3324501337(0) ack 3347102295 win 5792 <mss1460,sackOK,timestamp 15960089 2705443041,nop,wscale 7> 19:09:28.783886 IP officefw.57948 > remoteserver.ssh: . ack 1 win 46 <nop,nop,timestamp 2705443083 15960089> 19:09:28.789814 IP remoteserver.ssh > officefw.57948: P 1:21(20) ack 1 win 46 <nop,nop,timestamp 159601372705443083> 19:09:28.829114 IP officefw.57948 > remoteserver.ssh: . ack 21 win 46 <nop,nop,timestamp 2705443129 15960137> Sep 4 19:08:43 remoteserver kernel: IN=eth0 OUT= MAC=00:30:48:97:5a:3a:00:0a:b8:8e:53:29:08:00 SRC=officefw DST=remoteserver LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=41807 DF PROTO=TCP SPT=57948 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 Sep 4 19:08:46 remoteserver kernel: IN=eth0 OUT= MAC=00:30:48:97:5a:3a:00:0a:b8:8e:53:29:08:00 SRC=officefw DST=remoteserver LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=41808 DF PROTO=TCP SPT=57948 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 Sep 4 19:08:52 remoteserver kernel: IN=eth0 OUT= MAC=00:30:48:97:5a:3a:00:0a:b8:8e:53:29:08:00 SRC=officefw DST=remoteserver LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=41809 DF PROTO=TCP SPT=57948 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 Sep 4 19:09:04 remoteserver kernel: IN=eth0 OUT= MAC=00:30:48:97:5a:3a:00:0a:b8:8e:53:29:08:00 SRC=officefw DST=remoteserver LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=41810 DF PROTO=TCP SPT=57948 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 Sep 4 19:09:28 remoteserver kernel: IN=eth0 OUT= MAC=00:30:48:97:5a:3a:00:0a:b8:8e:53:29:08:00 SRC=officefw DST=remoteserver LEN=60 TOS=0x00 PREC=0x00 TTL=56 ID=41811 DF PROTO=TCP SPT=57948 DPT=22 WINDOW=5840 RES=0x00 SYN URGP=0 Sep 4 19:09:28 remoteserver kernel: IN=eth0 OUT= MAC=00:30:48:97:5a:3a:00:0a:b8:8e:53:29:08:00 SRC=officefw DST=remoteserver LEN=52 TOS=0x00 PREC=0x00 TTL=56 ID=41812 DF PROTO=TCP SPT=57948 DPT=22 WINDOW=46 RES=0x00 ACK URGP=0 Sep 4 19:09:28 remoteserver kernel: IN=eth0 OUT= MAC=00:30:48:97:5a:3a:00:0a:b8:8e:53:29:08:00 SRC=officefw DST=remoteserver LEN=52 TOS=0x00 PREC=0x00 TTL=56 ID=41813 DF PROTO=TCP SPT=57948 DPT=22 WINDOW=46 RES=0x00 ACK URGP=0

4 9

Problem with running Centos 5.2 on Dell Optiplex 330
by Pete Kay 08 Sep '08

08 Sep '08

Hi, I am havind deep trouble with a bunch of our newly arrived Optiplex 330 as it can't run Centos 5.2 property. The installation works fine, but when it boots up, it can't be connected to the network. I am getting error saying " link is not ready" when doing system-config-network. I check lspci and it can detect the network controller no problem. The light next to the cable is also on as well. Does anyone know how I can fix this problem? We should have bought just one and see if it works before buying more, and now we are stuck. Could someone please kindly give any suggestion? Any help will be greatly appreciated. Best Regards, Pete

6 9

USB drive fails at sector 0xFFFFFFF
by Kenneth Porter 08 Sep '08

08 Sep '08

I'm backing up to a NTFS partition on an external USB drive with dump. I'm seeing failures in /var/log/messages reading sector 0xFFFFFFF that cause the verify pass to fail. Are there any known problems in the USB driver? Kernel via uname -a: Linux segw2.mpa.lan 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT 2008 i686 i686 i386 GNU/Linux Message reported. (Note the number 268435455, which is 0xFFFFFFF, and occurs every time I see this happen. But a subsequent attempt to read this region with dd succeeds, so it appears to be intermittent, or dependent on some other precondition.) Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause not reportable Sep 7 10:48:39 segw2 kernel: Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector 268435455 Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block 33554424 Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: sense key: Not Ready Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause not reportable Sep 7 10:48:39 segw2 kernel: Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector 268435455 Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block 33554424

2 1

Re: [CentOS] USB drive fails at sector 0xFFFFFFF
by Lanny Marcus 08 Sep '08

08 Sep '08

On Sun, Sep 7, 2008 at 6:44 PM, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > I'm backing up to a NTFS partition on an external USB drive with dump. I'm > seeing failures in /var/log/messages reading sector 0xFFFFFFF that cause the > verify pass to fail. Are there any known problems in the USB driver? > > Kernel via uname -a: > > Linux segw2.mpa.lan 2.6.18-92.1.6.el5 #1 SMP Wed Jun 25 13:49:24 EDT 2008 > i686 i686 i386 GNU/Linux > > Message reported. (Note the number 268435455, which is 0xFFFFFFF, and occurs > every time I see this happen. But a subsequent attempt to read this region > with dd succeeds, so it appears to be intermittent, or dependent on some > other precondition.) > > Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: > sense key: Not Ready > Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause > not reportable > Sep 7 10:48:39 segw2 kernel: > Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector > 268435455 > Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block > 33554424 > Sep 7 10:48:39 segw2 kernel: sd 5:0:0:0: Device not ready: <6>: Current: > sense key: Not Ready > Sep 7 10:48:39 segw2 kernel: Add. Sense: Logical unit not ready, cause > not reportable > Sep 7 10:48:39 segw2 kernel: > Sep 7 10:48:39 segw2 kernel: end_request: I/O error, dev sdb, sector > 268435455 > Sep 7 10:48:39 segw2 kernel: Buffer I/O error on device sdb1, logical block > 33554424 My Newbie guess is that the device has an intermittent problem at sector 268435455 and it is failing intermittently at that location. Hopefully someone more knowledgeable can answer your question about the USB driver. Do you have any Diagnostics for that USB drive that you can run on it? If not, see if you can download diagnostics from the web site of the manufacturer. Maybe a problem at 33554424 also?

1 0

Time delaying (or time lagging)
by happymaster23 07 Sep '08

07 Sep '08

Hello everyone, I have problem with time delaying on my CentOS powered server. I have tried to set time in BIOS and in OS (with saving time to BIOS), but time still delaying, so after month is about five minutes delayed. In past I was using this box with Windows and there wasn´t this time problem, but I cant warrant, that there are no hardware issues. So I was decided, that easiest way to fix this problem will be setting up the NTP. I have found many howtos, but I don´t believe them. So my question is: How to clearly set NTP in CentOS 5? Thanky you very much

2 3

Troubles with NetworkManager
by ABBAS KHAN 07 Sep '08

07 Sep '08

NetworkManager used to work fine for me but during the last few installations its a big hurdle in the wireless connectivity. I'm using Madwifi and its interface is correctly listed and working but I cannot connect to any wifi AP without NetworkManager. I've two interfaces: eth0 and wifi0. Starting NetworkManager doesn't show any notification icon in the top right in gnome and I believe its only activating the ath0 instead of wireless interface wifi0 but still I am unable to see any of the notification icon in the gnome as I was used to in past for any of the NICs. The error which I recieve upon logging into the gnome is: "The NetworkManager applet could not find some required resources. It cannot conitnue". But still, there are no errors in the syslogs besides the below ones particularly *"localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down*". Thanks in advance for the helpout. [root@localhost abbask]# grep -A 2 -B2 NetworkManager /var/log/messages | tail -60 Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Jan 15 05:35:31 localhost NetworkManager: <information> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Jan 15 05:35:31 localhost dhclient: wifi0: unknown hardware address type 801 Jan 15 05:35:31 localhost dhclient: wifi0: unknown hardware address type 801 -- Jan 15 05:35:31 localhost NET[6581]: /sbin/dhclient-script : updated /etc/resolv.conf Jan 15 05:35:31 localhost dhclient: bound to 13.13.13.4 -- renewal in 1581 seconds. Jan 15 05:35:32 localhost NetworkManager: <information> Activation (eth0) Beginning DHCP transaction. Jan 15 05:35:32 localhost dhclient: wifi0: unknown hardware address type 801 Jan 15 05:35:32 localhost NetworkManager: <information> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Jan 15 05:35:32 localhost NetworkManager: <information> DHCP daemon state is now 12 (successfully started) for interface eth0 Jan 15 05:35:32 localhost NetworkManager: <information> DHCP daemon state is now 1 (starting) for interface eth0 Jan 15 05:35:32 localhost dhclient: wifi0: unknown hardware address type 801 Jan 15 05:35:32 localhost avahi-daemon[5154]: New relevant interface eth0.IPv6 for mDNS. -- Jan 15 05:35:32 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255port 67 Jan 15 05:35:32 localhost dhclient: DHCPACK from 13.13.13.3 Jan 15 05:35:32 localhost NetworkManager: <information> DHCP daemon state is now 4 (reboot) for interface eth0 Jan 15 05:35:32 localhost NetworkManager: <information> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Jan 15 05:35:32 localhost NetworkManager: <information> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Jan 15 05:35:32 localhost dhclient: bound to 13.13.13.4 -- renewal in 1438 seconds. Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name -- Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain Jan 15 05:35:32 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers Jan 15 05:35:32 localhost NetworkManager: <information> Retrieved the following IP4 configuration from the DHCP daemon: Jan 15 05:35:32 localhost NetworkManager: <information> address 13.13.13.4 Jan 15 05:35:32 localhost NetworkManager: <information> netmask 255.255.255.0 Jan 15 05:35:32 localhost NetworkManager: <information> broadcast 13.13.13.255 Jan 15 05:35:32 localhost NetworkManager: <information> gateway 13.13.13.3 Jan 15 05:35:32 localhost NetworkManager: <information> nameserver 13.13.13.3 Jan 15 05:35:32 localhost NetworkManager: <information> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Jan 15 05:35:32 localhost NetworkManager: <information> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Jan 15 05:35:32 localhost NetworkManager: <information> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Jan 15 05:35:32 localhost avahi-daemon[5154]: Withdrawing address record for 13.13.13.4 on eth0. Jan 15 05:35:32 localhost avahi-daemon[5154]: Leaving mDNS multicast group on interface eth0.IPv4 with address 13.13.13.4. -- Jan 15 05:35:33 localhost dnsmasq[5162]: reading /etc/resolv.conf Jan 15 05:35:33 localhost dnsmasq[5162]: using nameserver 13.13.13.3#53 Jan 15 05:35:33 localhost NetworkManager: <information> Activation (eth0) successful, device activated. Jan 15 05:35:33 localhost NetworkManager: <information> Activation (eth0) Finish handler scheduled. Jan 15 05:35:33 localhost NetworkManager: <information> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. Jan 15 05:35:35 localhost avahi-daemon[5154]: New relevant interface eth0.IPv6 for mDNS. Jan 15 05:35:35 localhost avahi-daemon[5154]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::21c:c0ff:fe4f:f2cf. -- Jan 15 05:35:35 localhost dnsmasq[5162]: using nameserver 13.13.13.3#53 Jan 15 05:35:35 localhost avahi-daemon[5154]: Registering new address record for fe80::21c:c0ff:fe4f:f2cf on eth0. Jan 15 05:37:11 localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down Jan 15 05:39:11 localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down Jan 15 05:41:11 localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down Jan 15 05:43:11 localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down Jan 15 05:45:11 localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down Jan 15 05:47:11 localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down Jan 15 05:49:11 localhost NetworkManager: <WARNING> nm_device_802_11_wireless_scan (): could not trigger wireless scan on device ath0: Network is down [root@localhost abbask]#

2 1

xulrunner-devel package missing many header files
by hce 07 Sep '08

07 Sep '08

Hi, I've just installed xulrunner-devel from yum, but there are following header files cannot be found in xulrunner-sdk-1.9/sdk/include: mozilla-config.h mozilla-config32.h prtypes.h The include/xulrunner-sdk-1.9 constains those above header files, I did link to them, but xulrunner-sdk-1.9/system_wrappers/prtypes.h has a problem as well: #pragma GCC system_header #pragma GCC visibility push(default) #include_next <prtypes.h> #pragma GCC visibility pop At final, I could not compile VLC plugin with the xulrunner-sdk-1.9/sdk. Please advice how to fix it and where could I install a proper sdk? Thank you. Kind regards, Jim

2 2

Kernel panic installing CentOS 5.2 in Parallels on iMac
by Bart Schaefer 06 Sep '08

06 Sep '08

I'm unable to get much past the "boot:" prompt in the installer. The panic appears to be in powernowk8_init which according to http://rhn.redhat.com/errata/RHSA-2008-0612.html has a recently-fixed null-pointer dereference. That errata is from August 4; the latest CentOS install ISOs are from June. I tried the agp=off suggestion from e.g. http://www.centos.org/modules/newbb/viewtopic.php?topic_id=13512 with no success. Is there a good way to proceed here? Will there be new install media with the more recent kernel?

2 3

← Newer
1
...
23
24
25
26
27
28
29
...
32
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 September 2008