Re: [SLE] http server setup problem in suse 10.0
Hello all:
I would like to set up apache http server only for serving localhost requests. I installed the apache and other required packages through yast/network services/HTTP server. When it turned to the server configuration (HTTP server wizard) I could not pass the first step as there was not anything in the "Listen to Interfaces" window. It was completely empty. Now I am stucked. I think the localhost interface should be there at least. What should I do?
First check if the daemon is running. Yast > System > System Services > Runlevel Look for Apache2 and see if it is enabled. If it isn't set to 'yes'. You could also be geeky and drop into terminal mode and as root (su) type /etc/init.d/apache2 start (You can also do stop/restart if you want.) The old version used to be /etc/init.d/httpd (At least that's how it is on our SLES boxen. -- kai ponte www.perfectreign.com || www.livebeans.com linux - genuine windows replacement part
I could not pass the first step as there was not anything in
Hello: the
"Listen to Interfaces" window. It was completely empty. Now I am stucked. I think the localhost interface should be there at least. What should I do?
First check if the daemon is running. The demon is not runnig. That's why I want to configure. I think YAST/Network Services/HTTP server should do it.
Nevertheless I checked YAST/System/System services and I _turned_apache2_on. However still can't configure in HTTP sevices window. Is this a suse bug? Thanks, IG ___________________________________________________________________________ [origo] klikkbank lakossági számlacsomag havi 199 Ft-ért, bankkártya éves díj nélkül! www.klikkbank.hu
Hi! Am Mittwoch, 1. März 2006 18:15 schrieb Istvan Gabor:
The demon is not runnig. That's why I want to configure. I think YAST/Network Services/HTTP server should do it.
Yep, if you start the http-server module in Yast, you get to radio-buttons "activate apache" is the one you have to enable. Sven
On Wednesday 01 March 2006 12:15, Istvan Gabor wrote:
First check if the daemon is running.
The demon is not runnig. That's why I want to configure. I think YAST/Network Services/HTTP server should do it.
Nevertheless I checked YAST/System/System services and I _turned_apache2_on. However still can't configure in HTTP sevices window.
Is this a suse bug?
Hi Istvan, I doubt it's a bug... it worked straight away after I installed 10.0. There *was* a small configuration bug related to enabling access to pages published in user's public_html directories, but I believe that problem has been fixed. When you go into YaST > Software Management and enable the "Selections" filter (top left) you can click on the item "Simple Webserver with Apache2" and verify what is installed in the right side pane, where the individual packages are listed. If everything required has been installed, you need to start looking at conflicting packages or settings of some kind. Are you getting any errors in your logs when you try to start Apache2? regards, Carl
When you go into YaST > Software Management and enable
Hello: the "Selections" filter
(top left) you can click on the item "Simple Webserver with Apache2" and verify what is installed in the right side pane, where the individual packages are listed.
First time when I started HTTP server module in YAST it has downloaded and installed the apache2 and related packages. Nevertheless I checked apache installation in the Software Management module as you suggested and selected "simple web server with apache 2". This resulted in marking some packages to be installed (with an *open* triangle, I've never seen this mark before). I accepted the offers ans installed the packages. I have no any dependency problems according to yast. But nothing changed regaring apache setup. There are two things I don't understand: 1. Why don't I get those radio buttons and setup options in HTTP server wizard modult that you and others mention? 2. Why is the "interfaces" window empty? It should contain at least localhost (127.0.0.1) and my network card. Earlier on debian I could use http server even without a network card to serve localhost. (Frankly, I think suse people has "fixed" here something too. Like the printer setup and graphics card setup modules that worked much better in earlier suse versions.)
your logs when you try to start Apache2?
I even don't think anymore that this is an apache problem. I think this is a suse/YAST specific configuration issue. Thanks for helping, IG ___________________________________________________________________________ [origo] klikkbank lakossági számlacsomag havi 199 Ft-ért, bankkártya éves díj nélkül! www.klikkbank.hu
It seems I am not the only one who has/had this problem: http://www.linuxquestions.org/questions/showthread.php? s=&threadid=340392 I checked the suse manual and it even shows the wizard window with the "listen on interfaces" window. It just doesn't tell how to "get" an interface there. IG ___________________________________________________________________________ [origo] klikkbank lakossági számlacsomag havi 199 Ft-ért, bankkártya éves díj nélkül! www.klikkbank.hu
On Wednesday 01 March 2006 13:31, Istvan Gabor wrote:
I even don't think anymore that this is an apache problem. I think this is a suse/YAST specific configuration issue.
OK, some random 'forensics/troubleshooting' notes: a. Is there anything else running, like Skype, using the port and interface you're trying to configure? This has been known to interfere with Apache2, both starting *and* installation... check with netstat: netstat -tulpen | grep ":80" b. Verify/adjust your host settings in: 1. YaST Control Center => Network Services => Host Names 2. YaST Control Center => Network Services => DNS and Host Name It can't hurt to keep "poking at" this problem until something informative crops up, right? regards, Carl
OK, some random 'forensics/troubleshooting' notes:
a. Is there anything else running, like Skype, using the port and interface you're trying to configure? This has been known to interfere with Apache2, both starting *and* installation... check with netstat: netstat -tulpen | grep ":80"
Well, it seems my apache instalation is OK, and apache runs well. If I go to "localhost" with my browser I get the apache default page. It seems that only YAST can not configure it. By the way, this is I get when I run the above command: # netstat -tulpen | grep ":80" tcp 0 0 :::80 :::* LISTEN 0 14746 6314/httpd2-prefork
b. Verify/adjust your host settings in: 1. YaST Control Center => Network Services => Host Names
I have here several lines: 127.0.0.1 localhost 127.0.0.2 linux.site linux ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts
2. YaST Control Center => Network Services => DNS and Host Name
hostname: linux domain name: site Thanks again, IG ___________________________________________________________________________ [origo] klikkbank lakossági számlacsomag havi 199 Ft-ért, bankkártya éves díj nélkül! www.klikkbank.hu
On Thursday 02 March 2006 17:27, Istvan Gabor wrote:
Well, it seems my apache instalation is OK, and apache runs well. If I go to "localhost" with my browser I get the apache default page. It seems that only YAST can not configure it. By the way, this is I get when I run the above command:
# netstat -tulpen | grep ":80" tcp 0 0 :::80 :::* LISTEN 0 14746 6314/httpd2-prefork
OK, the problem must be the wizard, not Apache2. Now, I found a similar problem reported *for 10.1* not 10.0: https://bugzilla.novell.com/show_bug.cgi?id=135884&x=24&y=5 But this was reported at the end of last November and marked "resolved" one hour later. Your other settings looked normal, so I've <snipped> them. ;-) Why not take a look here?: /usr/share/doc/packages/yast2-http-server Maybe there are some useful tidbits about that wizard to be found. Good luck and keep us updated! Carl
participants (4)
-
Carl Hartung -
Istvan Gabor -
Kai Ponte -
Sven Burmeister