I've made a CentOS 5 x86_64 setup last year, around november/december.This system is supposed to operate as a home router/gateway, firewall, nas, small intranet/extranet server and media center.I've previously built a system using older parts (Pentium III 866MHz), and had on it CentOS 5 x86.It successfully served the same purpose (except nas and media center) for quite some time, about 1-2years, until i felt i needed better hardware (more memory, speed and disk space mainly) and 64-bit support.
Part of this intended setup isn't finished (router/gateway, firewall, media center), partially because i'm still lacking a good 1000mbps switch and a supported wireless n 3-antenna card in AP/server mode.In the previous setup, i had router/gateway, firewall and small intranet/extranet server working, with a crappy 100mbps switch (the switch is broken now).the new setup has run pretty well, it had been upgraded 2 times, etc...But since it has been installed, even before any updates, upgrades or repo additions, there has been always warnings/errors during kernel boot.I'm listing my specs, configs, versions and logs bellow. all the partitions, RAID and LVM were created during CentOS initial setup.
I'm trying to install uzbl and was following the step by step guide on this page http://xanderboy.esdebian.org/36949/uzb ... orts-flash When i run make i get a lot of errors and warnings. Can anybody point out what I'm doing wrong?
-bash: export: `/usr/java/default': not a valid identifier messages when we login as root to one of our server. This started occurring after a consultant installed software on the server. I have looked around in .bashrc, etc. for the error path so I can remove it, but can't seem to locate it. Does anyone have any tips on how to locate script line where this is being included, and/or trace the login procedure to find the culprit?
Not sure on what is going on here. The server is RAID1 through hardware RAID. It was running an unusual high load so I rebooted it. Now it won't boot up. I am getting these errors after the CentOS boot screen:sda: Current [descriptor]: sense key: Medium ErrorAdd.Sense: Address mark not found for data field
end_request: I/O error, dev sda, sector 3040555357 device-mapper: raid1: A read failure occurred on a mirror device. device-mapper: raid1: All sides of mirror have failed.
Though my upgrade from 11.3 to 11.4 went pretty well (X and apparmor/samba config to renew), I have a bunch of warnings at boot time. Sample: "* wil be removed in a future UDEV version..." On another box, I get some "/etc/*/ipv6" should have a .conf file. Should I worry / fix up something before next upgrade?
this started to happen recently after a reboot due to updates. The screen displays many, meaning more than 12 of: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/ which is then followed by: Boot has failed, sleeping forever.
I deleted /etc/modprobe.conf, so that is not the problem. The normal boot process will display the modprobe warning twice and all is well. If the warning is displayed more than twice, the boot will fail and I have to try again.
I try to set up a 5 nodes cluster and a shared Coraid Storage with conga but it fails with "Shared Storage Support" checked.The message is:'A problem occurred when installing packages: Packages of set "Clustered Storage" are not present in available repository' and it is shown under every node on the next sceen after I submit.The pc where conga runs is on the same subnet (192.168.xxx.xxx) and it has the same /etc/hosts of the other nodes.In that pc runs a proxy too and the nodes go out through it (that pc has 2 NICs)Every node (2.6.18-128.1.14.el5-xen-x86_64) is patched whith the last yum update (this morning) the same is for the pc (2.6.18-128.1.14.el5).Every node has 4 NICs , 2 NICc towards the storage the others in bonding towards the WAN.Every node is exactly alike, they have been installed with the ks.cfg generated from the first node and they all have the support for Clustering, Virtualization, and Clustered Storage.
I have a 10-year-old desktop computer with Windows XP on one drive and Ubuntu 10.4 on the second drive. The first is an old IDE disk, the second a more modern SATA drive. Tried to boot Ubuntu, and got a lot of arcane i/o errors that I am sorry I can't repeat verbatim but there was something about unable to read sector this or sector that, among other things. I thought maybe the drive was hosed. Tried booting into recovery mode to see if I could figure anything out but it was too geeky for me. Then I tried rebooting Ubuntu to see if I could look at the errors again but now the system insists on going into recovery mode.
Then I tried booting windows, which as I mentioned is on a different physical drive. The MS logo comes up and then it reboots spontaneously and we're back where we started. Any ideas? Should I suspect the second drive is seriously damaged, or could there be some problem with the motherboard?
I just installed CentOS 5 today. Had terminal open and got these errors:Quote:Message from syslogd@ at Wed Jul 8 12:38:33 2009 ...localhost kernel: Uhhuh. NMI received for unknown reason a0 on CPU 0.Message from syslogd@ at Wed Jul 8 12:38:33 2009 ...localhost kernel: You probably have a hardware problem with your RAM chipsMessage from syslogd@ at Wed Jul 8 12:38:33 2009
The problems I was having earlier: [URL]seemed to be solved.
I was not getting any error messages after restart. I should have powered down fully, but did not think that it would make a difference. :(
The same issue is again occurring, but after shutdown ONLY and only on the first boot. After the first boot, a system restart will not cause any error messages. (I have rebooted at least ten or twenty times to make sure)
But after a system shutdown, the first boot hangs up and I get the
"Red Hat nash version 5.1.19.6 starting hdb: timeout waiting for DMA hdb: drive not ready for command"
errors five or six times before each boot. Also the system boots very slowly the first time.
I used the getinfo.sh all command and posted the info to the suggested site here: [URL]
Is it possible this could be a hardware issue? This is an old salvaged HDD. Ive changed everything I c an think of in the BIOS with no results.
I have used the hdparm -d /dev/hdb command and verified that dma is not being used on initial boot or after a shutoff but IS being used after a reboot...
here are the HDD settings /dev/hdb: multcount = 16 (on) IO_support = 0 (default 16-bit) unmaskirq = 0 (off)
I installed the VSFTPD from YUM and installed the webmin module.i can connect to the server with Telnet but can�t list files.When i try to connect with a FTP client i get the following errors: An error occured openig that folder on the ftp server. Make sure you have access to that folder.
200 Switching to ASCII mode. 227 Entering passive mode (172,20,1,5,69,210)
I'm running CentOS 5.3 x64 within a 32 bit version of Windows XP via VirtualBox. What I'm trying to do is install Eclipse such that I can code in both C++ and Java. I'm going to need to eventually add the OpenMP library, but that's later on. Right now, I'm just trying to get Eclipse to that point, I have the gcc and jre installed...it's just that Eclipse is not wanting to cooperate.
I did uninstall the open-jdk and install the Java SE 6u14. java version "1.6.0_14" Java(TM) SE Runtime Environment (build 1.6.0_14-b08) Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
And the gcc... gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44) Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I was able to install the Eclipse SDK using yum...
However when I go to update it using Eclipse's update utility to install from the Eclipse Project Updates (in this case, Eclipse 3.2.2 update) I get:
Unable to complete action for feature "Eclipse Platform" due to errors. Unable to complete action for feature "Eclipse RCP" due to errors. Unable to create file "/usr/share/eclipse/plugins/com.ibm.icu_3.4.5.20061213.jar1249125532555.tmp". [/usr/share/eclipse/plugins/com.ibm.icu_3.4.5.20061213.jar1249125532555.tmp (Permission denied)]
I have just installed a fresh copy of CentOS 5.3 and from the get-go, the NIC started dropping packets like crazy. I even closed the port on the switch,. moved the cable to a different port,. All yield the same "dropping packets" behavior. Zero on the errors, just dropping packets. Should I stick a diff nic instead?
When using YUM UPDATE from the prompt more than 230 items are scheduled for update however when the download process has completed I receive errors regarding Perl dependences such as:
file /usr/lib/perl5/5.8.8/List/Util.pm from install of perl-5.8.8-27.el5.x86_64 conflicts with file from package perl-5.8.8-18.el5_3.1.i386
I am unsure how to overcome this. It occurs on two different servers.
I am a complete novice when it comes to Linux, but want to learn, and installed CentOS5 on an old P4 Dell I had lying around. Dell Dimension 8100 BIOS is version A02 Install seemed to go fine, but when I power up I get the following message
Red Hat nash version 5.1.19.6 starting hdb: timeout waiting for DMA hdb: drive not ready for command
this happens a few times each, then CentOS finally loads.
If Im understanding this right, DMA is direct memory access. Is it possible the hard drive, motherboard etc does not support this?
After replacing all of the memory, the error remained, so we tried updating to the latest kernel. (Currently having to use centos-plus because we are using XFS)
After the kernel update the error disappeared fro 5 days (previously UNHEARD of - would often repeat several times a day), it appeared again and hasn't appeared since.
It does not seem like any real damage is done here - and I would like to suppress this error somehow. Optimally I would like it to only be forwarded to the log files - and NOT be displayed on the console.
Could someone point me to an easy way to set that up?
I just tried to install CentOS 5.4 on my notebook (HP G42-214BR), I use Windows 7 at the moment.
On the first time I got W7 installed at C: and couldn't istall centos on it. Before trying again I went to Windows and free something like 40GB from C:, but the disc where C: is went from basic to a dynamic disc.
After that I tried to install, and got some errors like:
And the final row was like:
And the installation don't go any further than this. What is going wrong?
i've got a server (blade on chassis) using Centos5.6. One partition is a LUN on SAN and the hardware used is a QLogic QMI3472 (qla2xxx driver) the kernel used is 2.6.18-238.12.1.el5
and i've got a lot of error message when i used the LUN partition with this log kernel (complete log attached to this message)
I've been trying to understand issues that occur during a uClinux distribution build (so I can include such issues in a module I'm writing for students). My process has been to work through errors that occur due to missing packages, then remove the distribution and build it again to uncover what happens.One thing I notice is different sets of warnings within each iteration of making a new build. From the document here (URl...it states, "A typical warning involves a variable being used before its value has been set."
So my question: is there a way to verify that the issue throwing the warning has been resolved by the end of the make build?And, is running make build again an option or could this cause problems within the build directories or image?
You should be running a firewall. I would also periodically check for rootkits with rkhunter and chkrootkit. Antivirus is usually optional, but it depends on your network ... if you have Window$ machines, do use clamav or something.Hope I'm not distorting the thread but just ran rkhunter and got a lot of red warnings, especially worrying seems:
This is the command line I used to run cdrecord. Afterwards, I ran 'cdrecord -media-info' on the same disc and, as a result, I got the messages contained in the file I am adjoining. There, two consecutive warnings can be seen, which I quote:
Quote:
The disk, after recording, however, is both readable by GNU/linux and another O.S. What is the meaning of those warnings and what are its possible implications? I would like to know.
I recently just installed centos, but it appears that when I installed it v 0.9.8e was installed consequently, all the lib's etc. are /lib/libssl.so.0.9.8e instead of an ordinary /lib/libssl.so.0.9.8 etc. and this is causing some problems for me, as programs are looking for /lib/libssl.so.0.9.8, and even if i symlink/copy/move /lib/libssl.so.0.9.8e to /lib/libssl.so.0.9.8 there are still some errors occurring. I had been reading that supposedly yum is meant to have a "yum downgrade" option, however it doesn't appear to be recognised when I run it on my centos server.
I am new to CENTOS (5.2) and more importantly new to linux. Any time I try to gcc compile something, it always throws random errors. I yum installed development-tools which is what I have seen other threads suggest but that did not solve the issue. I still get the same errors. I cannot find a common error among the many things I have attempted to compile.
Here is my most recent file for an example made when trying to compile up-imapproxy : gcc -g -O2 -I. -I./include -c -o src/icc.o src/icc.c gcc -g -O2 -I. -I./include -c -o src/main.o src/main.c src/main.c: In function "int main(int, char**)": src/main.c:618: error: invalid conversion from *void* to *void* (*)(void*) src/main.c:618: error: initializing argument 3 of int pthread_create(pthread_t*, const pthread_attr_t*, void* (*)(void*), void*) src/main.c:646: error: invalid conversion from int* to socklen_t* src/main.c:646: error: initializing argument 3 of int accept(int, sockaddr*,socklen_t*) src/main.c:675: error: invalid conversion from void* to void* (*)(void*) src/main.c:675: error: initializing argument 3 of int pthread_create(pthread_t*, const pthread_attr_t*, void* (*)(void*), void*) make: *** [src/main.o] Error 1
