MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't know if this is a problem with some mandrake setting or and apache problem. I have searched around quite a bit and not been able to figure out what was wrong.
I had a server set up and it was working flawlesly, then all of the sudden it quit. It seems like at first I could still access it from the other computers by typing in the local IP, but then I couldn't get the local computers onto it, or even get the server to respond to pings.
There was one user connected to my site at the time, he was uploading or something, and I was installing GD and Imagick image libraries. That's when it went dead.
I have checked my router settings toi make sure it is forwarding properly, and I have checked everything else I could think of. I CAN ping from my server other computers on the lan, as well as external sites succesfully. I can also use the internet connection, although it seems a little slower and less responsive.
When trying to connect to the site, the external computer just hangs. It doesnt say unreachable, it just times out after a while.
Any suggestions? Has anyone had this happen before? It seems weird because it just did it randomly.
The only thing I can think of is that one of those graphic libraries is a php extension and changing php somehow mesed up apache?
But since I can still access the page from the server by typing in the local IP, I would think apache and everything would be working fine....
A little update on the problem -
I dont know if this might be related:
I tried unistalling apache altogether. When the dialog comes up and says "You must also unintall all this other crap" I hit okay and the software removal program immediatly crashes.
So I went in and tried uninstalling all those packages first. I pinpointed the one with the problem. Its "apache-modules--1.3.28-3mdk". When I even click on the checkmark spot to uninstall it it crashes the uninstaller program. I don't know what this means or if it's even significant, but it IS keeping me from uninstalling Apache
-edit-
-Another update:
Ive managed to get all the apache dependant program unistalled, but when I check uninstall the main apache program, it still pops up the dialog saying I need to remove "apache2-mod_perl-2.0.47_1.99_09-3mdk, mod_php-4.3.3-2mdk"
If I click okay it crashes. the perl one has already been uninstalled
YEt another update in case anyone ever gets to this....
The system went down at aprox 16:42 so I checked my "messages" file in my logs to see what I could come up with. The only thing I can find is this error message repeated throughout the entire file, and the only error message around 16:42
So does that mean my hard drive is bad? If so are there any utilities in linux that would be able to fix it, or find the bad sectors and know not to use them or something?
Distribution: Mandrake 9.2 =<3 and Red Hat 8.0 (server)
Posts: 242
Rep:
in red hat 8
[root@server bin]# ls |grep network
redhat-config-network
redhat-config-network-cmd
redhat-config-network-druid
redhat-control-network
thats in /usr/bin
............
ah ha!
[root@server init.d]# /etc/init.d/network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[root@server init.d]#
I had the problem you had, after 47 days my networked stopped on both of my machines, just do that command instead of rebooting.
CRC is a cyclical redundancy check, or just a checksum in plain English. In this case, a hardware checksum between host and device. Doesn't mean the drive is bad; maybe you played with hdparm and set a bad value... like using UDMA/100, which the drive may support, with a 40 wire IDE cable.
in mandrake 9.2 (if that's what you're using) type service network restart to restart the network (you have to run it as root). but i don't know if that will even help you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.