[GLLUG] apache problems - further
Benjamin Cathey
benjamincathey at catheycompany.com
Thu Jun 21 10:05:45 EDT 2007
>->> Many programs (sshd for example) will automatically listen on all
>->> interfaces. What program is using your port 80 right now?
>->>
>->> Try /sbin/fuser -n tcp 80
>->>
>->> that should give you the pid of the program on port 80. I suspect it's
>->> still your mailserver. You will need to figure out how to configure it to
>->> listen on just the one ip. Or, maybe it's ok and Apache wants to get 80
>->> on the other IP as well. That is pretty easy to configure in httpd.conf
>->> to listed on just 1 ip.
yes the mailserver is listening on port 80 and it IS listening on just the one IP. Again, here is the info:
[root at mercury conf.d]# netstat -plant
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:2208 0.0.0.0:* LISTEN 2297/hpiod
tcp 0 0 192.168.1.200:993 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:995 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:389 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 0.0.0.0:998 0.0.0.0:* LISTEN 2088/rpc.statd
tcp 0 0 192.168.1.200:110 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:143 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2054/portmap
tcp 0 0 192.168.1.200:80 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:465 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 0.0.0.0:44337 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:563 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:119 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:25 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:443 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 192.168.1.200:636 0.0.0.0:* LISTEN 3946/mailserver
tcp 0 0 127.0.0.1:2207 0.0.0.0:* LISTEN 2302/python
tcp 0 0 192.168.1.200:443 75.7.194.69:13409 ESTABLISHED 3946/mailserver
tcp 0 0 192.168.1.200:443 75.7.194.69:13413 ESTABLISHED 3946/mailserver
tcp 0 0 192.168.1.200:25 124.104.136.175:63135 ESTABLISHED 3946/mailserver
tcp 1 36 192.168.1.200:25 64.14.86.205:22049 CLOSING -
tcp 1 0 192.168.1.200:40411 209.132.176.120:80 CLOSE_WAIT 2473/python
tcp 0 0 :::22 :::* LISTEN 2328/sshd
tcp 0 0 ::1:631 :::* LISTEN 2314/cupsd
tcp 0 0 ::ffff:192.168.1.200:22 ::ffff:192.168.0.250:2208 ESTABLISHED 2760/1
It is simply listening on 192.168.1.200:80 - so I SHOULD be able to start listening on port 80 on the other IP:
eth0 Link encap:Ethernet HWaddr 00:13:72:0B:D7:5A
inet addr:192.168.1.200 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fe0b:d75a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:40989 errors:0 dropped:0 overruns:0 frame:0
TX packets:37561 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:30724453 (29.3 MiB) TX bytes:10833131 (10.3 MiB)
Interrupt:17
eth0:0 Link encap:Ethernet HWaddr 00:13:72:0B:D7:5A
inet addr:192.168.1.205 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:17
But when I try to start it I get this:
[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]#
HELP? Anyone? I KNOW this is possible. I've seen it done before . . .
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: Mark Szidik/mlc
[mailto:SzidikM at mlcnet.org]
To: Benjamin Cathey
[mailto:benjamincathey at catheycompany.com]
Sent: Thu, 21 Jun 2007 09:59:51
-0400
Subject: RE: [GLLUG] apache problems - further
>->> Many programs (sshd for example) will automatically listen on all
>->> interfaces. What program is using your port 80 right now?
>->>
>->> Try /sbin/fuser -n tcp 80
>->>
>->> that should give you the pid of the program on port 80. I suspect it's
>->> still your mailserver. You will need to figure out how to configure it to
>->> listen on just the one ip. Or, maybe it's ok and Apache wants to get 80
>->> on the other IP as well. That is pretty easy to configure in httpd.conf
>->> to listed on just 1 ip.
>->>
>->>
>->>
>->> ---
>->> Mark Szidik, CIO
>->> Michigan Library Consortium
>->> 1407 Rensen Street, Suite 1, Lansing, MI 48910-3657
>->> Ph:800.530.9019 x117 Fax:517.492.3881
>->> Ph:517.492.3817
>->> MLC - Partnerships. Solutions. Excellence.
>->>
>->>
>->>
>->>
>->> "Benjamin Cathey" <benjamincathey at catheycompany.com>
>->> Sent by: linux-user-bounces at egr.msu.edu
>->> 06/21/2007 09:52 AM
>->>
>->> To
>->> "Jim Fick" <jfick at mphi.org>
>->> cc
>->> linux-user at egr.msu.edu
>->> Subject
>->> RE: [GLLUG] apache problems - further
>->>
>->>
>->>
>->>
>->>
>->>
>->> >->> What about using two different nics?
>->>
>->> I don't think I have to, right? I mean that is the whole point is that
>->> apache can use the other IP address. This seems like it must be a common
>->> thing. I know our firewall box has multiple IPs set up on the one
>->> incoming nic (for NAT.)
>->>
>->> Wow - I thought this would be easy - HA!
>->>
>->> Anyone else?
>->>
>->>
>->> 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: Jim Fick [mailto:jfick at mphi.org]
>->> To:
>->> Benjamin Cathey [mailto:benjamincathey at catheycompany.com]
>->> Sent: Thu, 21 Jun
>->> 2007 09:49:46 -0400
>->> Subject: RE: [GLLUG] apache problems - further
>->>
>->>
>->> >->> What about using two different nics?
>->> >->>
>->> >->> > -----Original Message-----
>->> >->> > From: linux-user-bounces at egr.msu.edu [mailto:linux-user-
>->> >->> > bounces at egr.msu.edu] On Behalf Of Benjamin Cathey
>->> >->> > Sent: Thursday, June 21, 2007 9:45 AM
>->> >->> > To: Michael George
>->> >->> > Cc: linux-user at egr.msu.edu
>->> >->> > Subject: Re: [GLLUG] apache problems - further
>->> >->> >
>->> >->> > >->> Pardon my ignorance, but is there a reason you want to use a
>->> >->> > different IP
>->> >->> > >->> address for the SMTP server and the HTTP server? Maybe you
>->> are
>->> >->> > making
>->> >->> > >->> things unnecessarily complex...
>->> >->> >
>->> >->> > Okay - Here's the thing - the 'mailserver' process is a mailserver
>->> >->> package
>->> >->> > which includes a webmail interface.
>->> >->> >
>->> >->> > The way their software works, the only way for me to do this is to
>->> set
>->> >->> it
>->> >->> > up with a separate ip. I have the mailserver up and running and
>->> >->> listening
>->> >->> > on 192.168.1.200. It's apache I am having trouble with.
>->> >->> >
>->> >->> > The other site will be COMPLETELY separate and have it's own web
>->> >->> interface
>->> >->> > (http and https), etc
>->> >->> >
>->> >->> >
>->> >->> > 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.
>->>
>->>
>->> _______________________________________________
>->> 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.
More information about the linux-user
mailing list