top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

CentOS 6.4 on old PC not connecting

0 votes
531 views

On an old server (Dell PowerEdge SC1420, now without RAID) I have CentOS 6.4 installed, up, and running -- but it keeps failing to connect for some reason ....

NetworkManager applet 0.8.1 runs blue rings around in the panel for a while, then reports itself disconnected. It also offers a pseudo-choice, if I right-click, between Wired Connection and eth0; in fact, the cable to the router is the only connection the machine has or has ever had.

I've tried such things as I could find to get a connection, in vain. I've tried replacing the cable.

If there's a good fix, I'd like to get my wife running CentOS, because it's one obvious choice for her to have against such time as I'm gone. (I don't at all claim to be the Oldest Subscriber, but I am at an age such that I would be irrational not to plan for such contingencies.)

What new way can I try to get this beast online?

posted May 18, 2013 by anonymous

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

If it shows eth0 in the networkmanager window, then it appears that it can see the ethernet card.

What is the output from ifconfig?
What does /var/log/messages say when you are trying to connect?

answer May 18, 2013 by anonymous
OK, I got lots of output from ifconfig, and tons from /var/log/messages; so what should I look for??
commented May 19, 2013 by anonymous
(a) Post the output from ifconfig
(b) type this: tail -f /var/log/messages
(c) Now tell networkmanager to connect.
(d) Post everything that shows up from that point until the connection attempt fails.
commented May 19, 2013 by anonymous
Remember the problem machine can't even send *me* things over my LAN; what's more, I don't seem to see an app for writing them to a CD and sneaker-mailing them to myself.
Hi-yi-yippee-ki-yay! I did ps ax|grep networkmanager ; got a process number; killed it; and wonder of wonders, it put itself online.
I launched firefox, opened a tab to weather, and got today's data ; so it really is online!
commented May 19, 2013 by anonymous
Similar Questions
+1 vote
Centos 6.4 hostname is not correct

I currently have a problem with hostname and fqdn.
I use:

# cat /etc/redhat-release ; uname -r
CentOS release 6.4 (Final)
2.6.32-358.11.1.el6.centos.plus.x86_64

# hostname
srv1.devel.test.com

# grep HOSTNAME /etc/sysconfig/network
HOSTNAME=srv1.devel.test.com

# cat /etc/hostname
srv1

# cat /etc/domainname
devel.test.com

but

# hostname --fqdn
devel.test.com

As I think it should give: srv1.devel.test.com. Have you got similar problem? Any hint how to solve it?

+2 votes
Emacs 24 on CentOS 6.4

I've installed CentOS 6.4, for which Emacs 23 is available; but I'd like to have Emacs 24. I've looked at rpmforge and epel, but neither seem to have Emacs 24 already packaged; and I've searched for every combination of emacs + 24 + centos without success.

While I could, of course, just do the ./configure && make && make install dance, I don't like having software installed that's not in the packaging system. I'd appreciate any pointer to a prepackaged Emacs 24, or failing that, a good tutorial on how to package software correctly for CentOS.

+1 vote
Setting up paths etc. for Qt 4 development on a CentOS 6 system

I was just wondering, is there a "correct" or "preferred" way of setting up the path and other environment variables for Qt 4 development/build using qmake and all - on a CentOS 6 system?

I mean, this does not work out-of-the box, at least if you have build files that assume "qmake" may be executed just like that - as there is no Qt 4 qmake on the path, although "qmake-qt4" is available. Also, if
qt3-devel is installed, and the default path setup is used, "qmake" will point to the Qt 3 version, as the package includes a profile.d file that modify the path in such a way. Which also sets up other Qt related
variables, I believe. There is no such file in qt4-devel, however.

I know ways to set up everything so that this works as expected, of course, but it would be interesting to know how the packagers intended it to be done. Are you expected to edit login files by hand? That's sort
of surprising in this day and age... Or is the thinking that the suffixed ("-qt4") version of commands will always be used? Or that everyone will be using plain make with pkg-config? Or is there some other mechanism that should to be used to select the right Qt version?

0 votes
Appache index error on CentOS-6,4

I am getting this error when trying to access a virtual website index by ip address and port on a host that has SELinux disabled (another issue over which I have less control than I wish):

curl http://192.168.6.9:41780 | more

Gives this error in /var/log/httpd/error_log

[Mon Jun 10 09:04:44 2013] [error] [client 192.168.6.9] Directory
index forbidden by Options directive: /tftpboot/

and displays the default Centos/Apache server page instead of the list of files in the directory.

This virtual host is defined thus:

Listen 192.168.6.9:41780

DocumentRoot "/tftpboot"

allow from all
Options +Indexes

If I specify a known file within /tftpboot then that file's contents are displayed properly. It is only the index that appears to fail.

So, what configuration error have I made? Why am I not getting a list of the contents of /tftpboot ?

0 votes
ssi not working on virtual host, using CentOS 6.0 with Apache 2.2.15

I am using CentOS 6.0 with Apache 2.2.15, and set up Apache with virtual host. The SSI works fine on the first VH, but ssi on the other virtual hosts does not work. I got the following message in the error log: 

mod_include: Options +Includes (or IncludesNoExec) wasnt set, INCLUDES filter removed

Does anyone know how to resolve this problem?

...