Discuss June 2006

discuss@lists.centos.org

217 participants
235 discussions

Help debugging superodoctor
by Sam Drinkard 13 Jun '06

13 Jun '06

I've tried several times to get superOdoctor to run on this machine, and have had no luck yet. Aside from this error message, # superodoctor ***************************************************************************** Supero Doctor II - Linux version 2.24(060523) Copyright(c) 1993-2006 by Super Micro Computer, Inc. http://supermicro.com/ ***************************************************************************** (superodoctor:7713): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. The application appears to open, then just crashes, never producing any output or anything. I've included a backtrace, just in case someone could help me out. The thing that worries me is the lib64/tls/libpthread.so.0. That same library gave me problems when I was setting up the WRF weather model to run, and was forced to use LD_ASSUME_KERNEL = 2.4 in order to get it to run. I tried the same trick with superodoctor, but did not work. Any and all help appreciated... I've sent requests for help to super micro, but have not gotten any response from them. This is an x86_64 machine, and the version of superodoctor is for the x86_64. AFIK, the installation was OK, with no problems. Regards, Sam Backtrace was generated from '/usr/sbin/superodoctor' Using host libthread_db library "/lib64/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 182894241344 (LWP 6993)] 0x0000003b4b00bfc4 in waitpid () from /lib64/tls/libpthread.so.0 #0 0x0000003b4b00bfc4 in waitpid () from /lib64/tls/libpthread.so.0 #1 0x000000375d458c04 in libgnomeui_module_info_get () from /usr/lib64/libgnomeui-2.so.0 #2 <signal handler called> #3 0x0000003b4a5706c3 in strstr () from /lib64/tls/libc.so.6 #4 0x000000000042e8f8 in smbus_byte_data_read (bustype=0, smb_base_io_addr=4352, slave=47, offset=40, data=0x7fbffff45c) at smbus.c:636 #5 0x000000000042c00f in get_item_reading (sThis_System=0x63e010, thisitem=0x63e480, parameters=0x63f910, iParameter_Count=38, cRet=0x7fbffff4f0 "0§s") at sd.c:2131 #6 0x000000000040b411 in create_SD_Table (sThis_System=0x63e010, spItem=0x63e480, iItem_Count=19, spParameter=0x63f910, iParameter_Count=38) at main.c:1798 #7 0x000000000040c146 in main (argc=7007456, argv=0x6aece0) at main.c:2471 Thread 1 (Thread 182894241344 (LWP 6993)): #0 0x0000003b4b00bfc4 in waitpid () from /lib64/tls/libpthread.so.0 No symbol table info available. #1 0x000000375d458c04 in libgnomeui_module_info_get () from /usr/lib64/libgnomeui-2.so.0 No symbol table info available. #2 <signal handler called> No symbol table info available. #3 0x0000003b4a5706c3 in strstr () from /lib64/tls/libc.so.6 No symbol table info available. #4 0x000000000042e8f8 in smbus_byte_data_read (bustype=0, smb_base_io_addr=4352, slave=47, offset=40, data=0x7fbffff45c) at smbus.c:636 errNo = 0 i = 0 init_done = -1 res = 0 file = 0 filename = '\0' <repeats 19 times> test_addr = 1685017119 #5 0x000000000042c00f in get_item_reading (sThis_System=0x63e010, thisitem=0x63e480, parameters=0x63f910, iParameter_Count=38, cRet=0x7fbffff4f0 "0§s") at sd.c:2131 iRet = 0 dataH = 0 dataL = 0 data = 0 errNoL = 10154652 errNo = 0 div = 1 bitmask = 4406925 _v = 0 '\0' #6 0x000000000040b411 in create_SD_Table (sThis_System=0x63e010, spItem=0x63e480, iItem_Count=19, spParameter=0x63f910, iParameter_Count=38) at main.c:1798 thisitem = (ITEMS *) 0x63e480 spSD_Table = (SD_TABLE *) 0x9af270 i = 0 div = 0 errNo = 0 Read = "0§s\000\000\000\000\0000§" High = "0§s\000\000\000\000\000®Q" Low = "0§s\000\000\000\000\000û%" #7 0x000000000040c146 in main (argc=7007456, argv=0x6aece0) at main.c:2471 app1 = (GtkWidget *) 0x6aece0 about2 = (GtkWidget *) 0x0 windowAlertMessage = (GtkWidget *) 0x73a730 arg = 6853872 interval = 400 bReset_Status = 0 cpStatus = 0x0 sThis_System = (SYSTEM_VARS *) 0x63e010 spItem = (ITEMS *) 0x63e480 spParameter = (PARAMETERS *) 0x63f910 iItem_Count = 19 cMB_Manufacturer = "Supermicro", '\0' <repeats 19 times> cMB_Product = "X6DA8", '\0' <repeats 24 times> cMB_Version = "PCB Version", '\0' <repeats 18 times> spSD_Table = (SD_TABLE *) 0x73a730

1 0

SSL: Server CommonName mismatch: localhost.localdomain
by M. Fioretti 13 Jun '06

13 Jun '06

Greetings, I have seen via google that this very problem was already discussed on several lists some months ago, but the archives report no solution. I have a remote server with dovecot 1.0-0_12.beta8 on Centos 4.3. IMAP works just fine: I can read email from both Squirrelmail via web and Kmail. Now I have created an ssl certificate on the server, and I'm trying to retrieve email via pop3s from my home PC (running suse, if this matters) When I launch fetchmail here at home I get the error below. Is it caused by dovecot, or something else on the server, like some error I could have made when generating and copying certificates? TIA, Marco marco@polaris:~> fetchmail -vv fetchmail: 6.3.2 querying my.vps.fqdn.name (protocol POP3) at Tue 13 Jun 2006 05:22:50 PM CEST: +poll started fetchmail: Issuer Organization: SomeOrganization fetchmail: Issuer CommonName: localhost.localdomain fetchmail: Server CommonName: localhost.localdomain fetchmail: Server CommonName mismatch: localhost.localdomain != my.vps.fqdn.name fetchmail: my.vps.fqdn.name key fingerprint: 20:93:B4:D8:CB:75:AD:72:F6:00:A8:DC:CE:F2:53:6E fetchmail: my.vps.fqdn.name fingerprints do not match! 23942:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify +failed:s3_clnt.c:894: fetchmail: SSL connection failed. fetchmail: socket error while fetching from remoteuser(a)my.vps.fqdn.name -- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/ Only boring people ever get bored Anonymous ----- End forwarded message ----- -- Marco Fioretti mfioretti, at the server mclink.it Fedora Core 3 for low memory http://www.rule-project.org/ There is hopeful symbolism in the fact that flags do not wave in a vacuum. -- Arthur C. Clarke

2 4

Re: Re: [CentOS] Changing from dynamic ip to static ip
by edukes＠alltel.net 13 Jun '06

13 Jun '06

> > From: "Joshua Gimer" <jgimer(a)gmail.com> > Date: 2006/06/13 Tue AM 08:39:36 EDT > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] Changing from dynamic ip to static ip > > IPADDR=71.30.117.2 > NETMASK=255.255.255.252 > NETWORK=71.30.117.0 <http://71.30.117.0/30> > GATEWAY=71.30.117.1 > > Add this to your /etc/sysconfig/networking/devices/ifcfg-eth0 > And take out > > BOOTPROTO=dhcp Great! Thanks, Eddie > > On 6/13/06, Thomas E Dukes <edukes(a)alltel.net> wrote: > > > > > > > > > -----Original Message----- > > > From: centos-bounces(a)centos.org > > > [mailto:centos-bounces@centos.org] On Behalf Of William L. Maltby > > > Sent: Tuesday, June 13, 2006 7:41 AM > > > To: CentOS General List > > > Subject: Re: [CentOS] Changing from dynamic ip to static ip > > > > > > On Mon, 2006-06-12 at 18:53 -0400, Thomas E Dukes wrote: > > > > Hello, > > > > > > > > I have been on a dynamic ip for about 5 years and have just > > > upgraded > > > > to a static ip. > > > <snip> > > > > > > I almost didn't mention it because it's so common a concern > > > now, but just in case. > > > > > > Static IP gives attackers a lot more leeway in their attempts > > > to penetrate. Be sure your firewall (from ISP and iptables on CentOS > > > machine) are now appropriate for your situation. With port 80 > > > open, make sure your server stuff is kept up-to-date with > > > security fixes. Make sure all services not needed are > > > disabled. TCP wrappers (hosts.deny and > > > hosts.allow) are up to snuff. > > > > Hi Bill, > > > > Thanks, > > > > Yes, I have a firewall setup and also use denyhosts and fail2ban. > > > > Thanks > > > > > > HTH > > > -- > > > Bill > > > > > > > > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > > > > -- > Thx > Joshua Gimer > > _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

1 0

Centos 4.3 & drbd
by centos＠bathnetworks.com 12 Jun '06

12 Jun '06

Hiya, I'm new to Centos but learning rapidly but I have been using FreeBSD. I'm trying to setup a HA NFS server using 2 machines. Both machines are running 4.3 updated to the latest via Yum. I did yum groupinstall drbd-heartbeat and yum install kernel-module-drbd-kernel-module-drbd-2.6.9-34.EL to match my kernel. The problem I have is that on 1 machine drbd works fine, but when I start drbd on the other I get an error: Starting DRBD resources: [ d0 ioctl(,SET_DISK_CONFIG,) failed: Invalid argument Lower device is already mounted. cmd /sbin/drbdsetup /dev/drbd0 disk /dev/hde1 internal -1 failed! It is not mounted as far as I can tell - df -a only shows /dev/hda and fstab has no entry for /dev/hde1. I have also tried deleting the partion with parted and recreating it. I have also tried using just /dev/hde. The /etc/drbd.conf is: resource drbd0 { protocol C; on fs1.bathnetworks.local { device /dev/drbd0; disk /dev/hde1; address 10.0.0.1:7788; meta-disk internal; } on shorty.bathnetworks.local { device /dev/drbd0; disk /dev/hdc1; address 10.0.0.2:7788; meta-disk internal; } } fs1 is the machine I am having trouble with. Any help with fixing this would be appreciated. Rob

3 4

even if I do not choose the Xwindows it still installs x ?
by Sentissi, Mohamed 12 Jun '06

12 Jun '06

Hello there I chose not to install the Xwindows and it still did ? a very minimal one (maybe xfce) any idea why ? I installed version 4 Thanks

3 2

Root filesystem is suddenly mounted read-only
by Alfred von Campe 12 Jun '06

12 Jun '06

This is very strange. Everything was running fine Friday night. This morning I walk into work and find that my root file system (which is actually the only filesystem besides /boot) is not writable. Yet mount thinks it's mounted read/write: # mount /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) [snip] # touch foo touch: cannot touch `foo': Read-only file system Anyone else seen this? This is on a relatively recently fresh CentOS 4.3 install. Alfred

2 2

Problems with csgfs after update
by C. L. Martinez 12 Jun '06

12 Jun '06

Hi all, Today I have update Centos cluster suite and my test cluster does not startup. When ccsd service tries to start returns this error: [root@srvimss1 lib]# ccsd Failed to connect to cluster manager. Hint: Magma plugins are not in the right spot. When I run magma_tools config plugindir returns me this setup: /lib/magma. This directory does not exists. How can I fix this problem??? Somebody have this problem?? Many thanks. -- C.L. Martinez clopmart(a)gmail.com

1 0

Failed VNC Install
by Brett Serkez 12 Jun '06

12 Jun '06

Installing a new system, I launched the install: linux vnc I was then able to connect with a VNC client and run the install, really cool. All went well until the actual installation started. I saw the formatting of the swap partition, then the root file system and then I was suddenly disconnected. On the console was the following message: *** glibc detected *** double free or corruption (!prev): 0x09baf620 *** install exited abnormally Any ideas as to what to look for? Has anyone used the VNC installation with V4.3? Thanks! Brett

2 2

Deleted my PATH
by Niels Przybilla 11 Jun '06

11 Jun '06

Hi, I have been logged in as root, and it seems to me that i destroyed all my PATh Variables. How can I restore them ? Thnaks for your help and best regards Niels

2 1

PXE booting HP BL25p - Smart Array extended bios data area problem
by Miskell, Craig 11 Jun '06

11 Jun '06

Hi, I recently took delivery of a bunch of HP BL25p blades to add to my collection. I am attempting to install Centos4 x86_64 using PXE - the initial PXE DHCP stuff works, and the kernel and initrd are downloaded, but the server then immediately clears the screen and displays: "1706-Smart Array Controller Extended BIOS Data Area Memory Corrupted Array Controller Interrupt 14h BIOS Cannot Continue System Halted" It's pretty obvious what the problem probably is (the kernel nukes some bit of memory that it shouldn't, or that the smart array hasn't properly marked as reserved), but I don't know what to do to fix it. I have also tried: 1) The i386 kernel and initrd images 2) The RedHat AS4 kernel/initrd images 3) The Centos3 i386 kernel and initrd images 4) Downgrading the System ROM BIOS and Smart Array BIOS (as shipped it had the latest versions) to versions up to a year old. 5) Playing with memmap to exclude mem from 610-640K from being used by the kernel. Booting from CD works, but is suboptimal (I have to type the kernel kickstart options, and I don't want to have to do that 16 times, plus I want easy repeatability in future). Google has been fairly silent on the issue. Does anyone have any suggestions for what else I could try/prod/poke? Thanks, Craig Miskell, Technical Support, AgResearch Invermay 03 489-9279 "The two rules for success: 1. Don't tell people everything you know." - Anon. Please accept my abject apologies for the awful mess of a legal disclaimer which follows. Not my choice ;-( ======================================================================= Attention: The information contained in this message and/or attachments from AgResearch Limited is intended only for the persons or entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipients is prohibited by AgResearch Limited. If you have received this message in error, please notify the sender immediately. =======================================================================

3 7

← Newer
1
...
13
14
15
16
17
18
19
...
24
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss June 2006