[GLLUG] apache problems - further

[Szymon Machajewski]

Oh, I'm sorry I missed this.

In this case simply edit httpd.conf of the apache server and specify the IP you want apache to use.

Do this under the LISTEN directive.

Thank you.
 
Szymon Machajewski

Solutions Engineer / DBA
Red Hat Certified Engineer
Oracle Certified Associate
Microsoft Certified Solution Developer
www.grcc.edu/smachaje 


>>> "Benjamin Cathey" <benjamincathey at catheycompany.com> 6/21/2007 9:19 AM >>>
>->> It looks to me that you are listening already on port 80.  netstat shows
>->> 'mailserver' with PID  3946 as the program running.
>->> 
>->> In a browser simply put the IP address of your server and see what pages
>->> will come up.
>->> 
>->> You can either disable the mailserver http interface and release port 80 for
>->> your Apache system.
>->> You can add another IP to the interface and have both programs listening on
>->> port 80.
>->> You can change the port in Apache and run it on a different port then 80.
>->> 

Right - That's what I said I did.  I have two IPs set up on the same NIC.  mailserver is listening on 192.168.1.200 and apache is setup to listen to 192.168.1.205 but it won't start and gives me that error message about "no listening sockets available" -- (98)Address already in use: make_sock: could not bind to address 192.168.1.205:80
no listening sockets available, shutting down --


Benjamin Cathey
System Administrator
Cathey Company
4917 Tranter St.
Lansing, MI 48910 USA
Phone:     517.393.4720
Fax:       517.393.4225
Toll Free: 800.333.1972
"Service is Our Profession"


----- Original Message -----
From: Szymon Machajewski
[mailto:SMachaje at grcc.edu] 
To: Benjamin Cathey
[mailto:benjamincathey at catheycompany.com] 
Sent: Thu, 21 Jun 2007 09:05:26
-0400
Subject: Re: [GLLUG] apache problems - further


>->> It looks to me that you are listening already on port 80.  netstat shows
>->> 'mailserver' with PID  3946 as the program running.
>->> 
>->> In a browser simply put the IP address of your server and see what pages
>->> will come up.
>->> 
>->> You can either disable the mailserver http interface and release port 80 for
>->> your Apache system.
>->> You can add another IP to the interface and have both programs listening on
>->> port 80.
>->> You can change the port in Apache and run it on a different port then 80.
>->> 
>->> 
>->> 
>->> Thank you.
>->>  
>->> Szymon Machajewski
>->> 
>->> Solutions Engineer / DBA
>->> Red Hat Certified Engineer
>->> Oracle Certified Associate
>->> Microsoft Certified Solution Developer
>->> www.grcc.edu/smachaje 
>->> 
>->> 
>->> >>> "Benjamin Cathey" <benjamincathey at catheycompany.com> 6/21/2007 8:52 AM
>->> >>>
>->> Okay - well, I thought it would work using the 'system-configure' utility in
>->> Fedora but apparently not.  
>->> 
>->> That only modified the /etc/httpd/conf.d/system-config-httpd.conf file.  I
>->> went in and modified the /etc/httpd/conf/httpd.conf file and specified
>->> Listen 192.168.1.205:80 thinking that would fix it but now I get THIS error:
>->> 
>->> [root at mercury conf.d]# httpd
>->> (98)Address already in use: make_sock: could not bind to address
>->> 192.168.1.205:80
>->> no listening sockets available, shutting down
>->> Unable to open logs
>->> [root at mercury conf.d]#
>->> 
>->> Maybe I have something set up incorrectly.  I know the IP works (I can ping
>->> it) but apparently no sockets are open on that IP.  Anyone know why?
>->> 
>->> nmap shows nothing open on that IP 
>->> 
>->> [root at mercury conf.d]# nmap 192.168.1.205
>->> 
>->> Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-06-21 08:50 EDT
>->> Note: Host seems down. If it is really up, but blocking our ping probes, try
>->> -P0
>->> Nmap finished: 1 IP address (0 hosts up) scanned in 0.226 seconds
>->> [root at mercury conf.d]# nmap 192.168.1.200
>->> 
>->> Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2007-06-21 08:51 EDT
>->> Interesting ports on 192.168.1.200:
>->> Not shown: 1665 closed ports
>->> PORT    STATE SERVICE
>->> 22/tcp  open  ssh
>->> 25/tcp  open  smtp
>->> 80/tcp  open  http
>->> 110/tcp open  pop3
>->> 111/tcp open  rpcbind
>->> 119/tcp open  nntp
>->> 143/tcp open  imap
>->> 389/tcp open  ldap
>->> 443/tcp open  https
>->> 465/tcp open  smtps
>->> 563/tcp open  snews
>->> 636/tcp open  ldapssl
>->> 993/tcp open  imaps
>->> 995/tcp open  pop3s
>->> 998/tcp open  busboy
>->> 
>->> Nmap finished: 1 IP address (1 host up) scanned in 0.219 seconds
>->> [root at mercury conf.d]#
>->> 
>->> If you can help - please and thank you
>->> 
>->> Benjamin Cathey
>->> System Administrator
>->> Cathey Company
>->> 4917 Tranter St.
>->> Lansing, MI 48910 USA
>->> Phone:     517.393.4720
>->> Fax:       517.393.4225
>->> Toll Free: 800.333.1972
>->> "Service is Our Profession"
>->> 
>->> **********************
>->> ** LEGAL DISCLAIMER **
>->> **********************
>->> 
>->> This E-mail message and any attachments may contain legally privileged,
>->> confidential or proprietary information. If you are not the intended
>->> recipient(s), or the employee or agent responsible for delivery of this
>->> message to the intended recipient(s), you are hereby notified that any
>->> dissemination, distribution or copying of this E-mail message is strictly
>->> prohibited. If you have received this message in error, please immediately
>->> notify the sender and delete this E-mail message from your computer. 
>->> 
>->> 
>->> _______________________________________________
>->> linux-user mailing list
>->> linux-user at egr.msu.edu 
>->> http://mailman.egr.msu.edu/mailman/listinfo/linux-user 
>->> 
>->> 

**********************
** LEGAL DISCLAIMER **
**********************

This E-mail message and any attachments may contain legally privileged, confidential or proprietary information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this E-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this E-mail message from your computer.