BIND close listen

Kudose

'ello all.

I am trying to get ssl_proxy up and running on my dedicated box, but when I attempt to start it, it fails stating that the address is in use.

netstat reports the IP I am trying to assign as LISTEN on port 53.

I have cPanel and have reserved the IP, restarted Bind, remove the address from Apache.

I still can't seem to get it to go away.

Can I force this to stop or do I have to reboot (I really don't want to right now)?

TIA!

edit

The IP I am trying to use for ssl_proxy is a free IP.

dalecosp

I'm probably not understanding, but are you trying to run a proxy server on the BIND port (53)?

Do you need BIND?

It's understandable that you can't do both. Either kill BIND and run the proxy, or run the proxy on another port. I'd recommend the latter.

Kudose

Thanks for your post. I am trying to get ssl_proxy to listen on port 443 on one of my IPs, but the IP is being used by BIND even though I tell cPanel to reserve the IP.

I run this command

ssl_proxy -s xxx.xxx.xxx.xx:443 -c localhost:80 -m 32 -C /etc/symbion/cert.pem     -K /etc/symbion/key.pem -U 2048 -D 8192

and get this output

bind(): Address already in use

so I run netstat and get this

tcp        0      0 xxx.xxx.xxx.xx:domain        *:*                         LISTEN

Yesterday it said xxx.xxx.xxx.xxx:53 before I rebooted the machine.

Any thoughts?

dalecosp

OK, it's clearer now. The message

bind(): Address already in use

isn't from BIND, the Berkley Internet Name Daemon, but from bind(2) in libc.

So, it has nothing to do with a nameserver. You're trying to have the proxy listen on port 443, but you already have an SSL-aware Apache or other webserver listening on that port (which is the standard SSL/HTTPS port).

That's what you need to fix.

Kudose

Well, I have Apache listening for SSL on two of my 6 IPs, but not on the IP I am having troubles with.

How do you propose I proceed?

dalecosp

Hehe, I dunno. Call the helpdesk?

Do you have shell access, or just Cpanel?

"Linux is for the 1337
Windows is for the lazy and/or ignorant
Mac is for those that think they know how to use a computer, but really don't"
- Silverman69

Heh, I'd be interested in what he thought *BSD was for....

dalecosp

PS> First thing I'd do is netstat -anf inet | grep 443. That's the BSD variant, I think Linux should be the same.

Kudose

Apearently Fedora doesn't support -f, but does -F and also doesn't allow inet after the switches.

root@cp [~]# netstat -anF | grep 443
tcp        0      0 0.0.0.0:443                 0.0.0.0:*                   LISTEN
tcp        0      0 xxx.xxx.xxx.34:443           xx.126.xx.xx:4938         FIN_WAIT2
tcp        0      0 xxx.xxx.xxx.38:443           xx.116.xx.xx:3086          TIME_WAIT
tcp        0      0 xxx.xxx.xxx.38:443           xx.116.xx.xx:3087          TIME_WAIT
...
root@cp [~]#

The IP I am trying to use ends in .37 ... do you think maybe the 0.0.0.0:443 could be the problem?

dalecosp

I concur. Not sure what to tell you to do, though. Is it Apache? Look for the "Listen" and "BindAddress" directives in httpd.conf. What do they say?

Kudose

dalecosp wrote:
Look for the "Listen" and "BindAddress" directives in httpd.conf.

I think that is my issue ...

<IfDefine SSL>
Listen 80
Listen 443
</IfDefine>

I will edit this and get back with you later.

Thanks!