10083300 Absent Member.
Absent Member.
5689 views

apache2 could not bind to address 0.0.0.0:631

Hi,

I was wondering if any of you guys have experience this.
I installed SLES 10 SP2 / OES 2 SP 2 and select DSfW.

After the installation, apache2 failed to start.
Encounter error" apache2 could not bind to address 0.0.0.0:631"
There seem to be conflict with iprint services.

If i were to rccups stop and start apache2 it is working again.
I hv tried to disable cups from starting up again but after reboot, cups services started again.

Any idea how to resolve this?

Thanks,
Fairuz
Labels (2)
Tags (5)
0 Likes
8 Replies
Knowledge Partner
Knowledge Partner

Re: apache2 could not bind to address 0.0.0.0:631

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

How did you try to stop the cups service? It should be able to be stopped
using something like chkconfig or even Yast for a more GUI-like interface.

chkconfig <servicename> off

Good luck.





10083300 wrote:
> Hi,
>
> I was wondering if any of you guys have experience this.
> I installed SLES 10 SP2 / OES 2 SP 2 and select DSfW.
>
> After the installation, apache2 failed to start.
> Encounter error" apache2 could not bind to address 0.0.0.0:631"
> There seem to be conflict with iprint services.
>
> If i were to rccups stop and start apache2 it is working again.
> I hv tried to disable cups from starting up again but after reboot,
> cups services started again.
>
> Any idea how to resolve this?
>
> Thanks,
> Fairuz
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLBrSFAAoJEF+XTK08PnB5qPgP/AoEQwyJ7B0RGMw1CiAhpg9U
i3UgI59IJ5Mi6CsBbGDfLvyNx0mW2GEBMMQbuwb+SHwVJ7+SMHeOsvRHSG+Loeo/
iHcK/ozHJubKCO9iFO6OF958IxouoPP/0fuGwWKHLqwUL/RQxsT45So8+gMQihkD
AhO/cfkthdGuozA73API0/WD95QdE0EoDmQCl5wQMt8FkQN9W929XLZiijuVfGcD
nWTsZm5msoUq+mS4WLjLuFJnBQRB5/fHbVw2CAQ9j5vp9YIL3tkvSwjtgWao2ijF
N5ubNmx50nJyyH6/P2Tq6Sqt/SDlLj1+zwIXGeu05EOi5rXFTNMg+y2oZuxV/0U3
dzV/g4wkd1t3GzzeyHRsbubilnAdbJSRqpKOKPDB7g1LsQB3wV7M7I9gNn0hzJ1J
TfLbrp7SG8iKHhZezjipDMNvwRx027NGfcuH9EpLnQjZdF4zjWQDbkucDTM6I3IU
DYLQCm7BZit4S+HlfcHVPmyzdWXuXrNoWSyfcp7lFQtvqvqvKtRsFVNqU72X8GR8
RJjT99A0oe1WKP2G1j7TEUd4vwaeWh0dHPOD6cCzuKL9NiJftI5Y3j1zr/Fhp/SC
GWSTFNUmwEBHCFMyyfFgk53R+93nIjKCXSrfbxrb7IVnUFdyhhrHKquSYTwxU+0R
gHs5q/l+ATFdW0O9/NLl
=rFsi
-----END PGP SIGNATURE-----
0 Likes
HvdHeuvel Absent Member.
Absent Member.

Re: apache2 could not bind to address 0.0.0.0:631

On Fri, 20 Nov 2009 15:23:49 +0000, ab@novell.com wrote:

Fairuz

First of all, you should _NOT_ use a combination of SLES10SP2 / OES2SP2 !!

* OES2 FCS requires SLES10SP1 *
* OES2 SP1 requires SLES10SP2 *
* OES2 SP2 requires SLES10SP3 *

No other combinations of the above are allowed or supported!!
If you do have a different combo than above, you need to re-install the
box from scratch.


In addition to what Aaron mentioned;

In case you did make a typo, and you have installed SLES10SP3 with OES2
SP2, do you accidentally perhaps have a (Dummy) NIC configured at
installation time that has 0.0.0.0 bound to it ?

With SLES10SP3 you can no longer leave the IP address from a Dummy NIC
empty if you do a GUI install, nor remove it there at a later stage.
So there is a chance you entered 0.0.0.0 somewhere at installation time
just so that you could proceed.

Please check your installation if you did that, and if so you need to use
a text editor to remove the 0.0.0.0 IP address from "/etc/sysconfig/
network/ifcfg-dummy0" file, or from any network card for that matter as
you should never ever have 0.0.0.0 bound to any NIC.

You really do need to check for, and remove this binding if existing, as
any other OES service you run on the box, including NDSD, may bind itself
to the same bogus 0.0.0.0 address, and than you may find yourself in all
sorts of other weird behavior at a later stage.

Also remember that when you manually modify a configuration file, you are
also required to manually restart the same service as well for any
changes to be effective.


Regards
Hans




0 Likes
10083300 Absent Member.
Absent Member.

Re: apache2 could not bind to address 0.0.0.0:631

Hi Hans,

You are right, i had a typo. It is definately, SLES SP 3 with OES 2 SP2.
Question what do you mean by dummy NIC?

During the initial network setup, i have set a static ip to it. It has only one nic card.
In any case, i will check my vms to see if its indeed bind to ip 0.0.0.0

But if I were to deselect iprint servies from the installation, there isn't any conflict with the port 631.
0 Likes
9734555 Absent Member.
Absent Member.

Re: apache2 could not bind to address 0.0.0.0:631

I have exactly the same problem; but in my case it has something to do with VMware workstation version 7 (to be specific: the vmware 7 tools). Somehow the tools start cups and therefore the apache2-daemon does not start. I don't have this problem with the older version of VMware and in my case it does not matter whether I install just DSfW or OES2SP2.
I don't know why this is happening. I am a CNI and last week I had 4 students installing OES2SP1 (not SP2), but three of them had VMware ws 6.5 running and one VMware ws 7 and he was the only one with exact the same problem as described above. Whe looking at the VMware tools running I see something about a Virtual Printing Service. Maybe this could be the cause, but I am not sure.
0 Likes
Knowledge Partner
Knowledge Partner

Re: apache2 could not bind to address 0.0.0.0:631

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Regardless of the exact SLES distribution you should be able to see if
something is already binding port 631:

netstat -anp | grep :631

Look for the 'LISTEN ' line specifically:

netstat -anp | grep :631 | grep 'LISTEN '

Whatever shows up should be apache/httpd, and if it is not then that is
your problem.

Good luck.






9734555 wrote:
> I have exactly the same problem; but in my case it has something to do
> with VMware workstation version 7 (to be specific: the vmware 7 tools).
> Somehow the tools start cups and therefore the apache2-daemon does not
> start. I don't have this problem with the older version of VMware and in
> my case it does not matter whether I install just DSfW or OES2SP2.
> I don't know why this is happening. I am a CNI and last week I had 4
> students installing OES2SP1 (not SP2), but three of them had VMware ws
> 6.5 running and one VMware ws 7 and he was the only one with exact the
> same problem as described above. Whe looking at the VMware tools running
> I see something about a Virtual Printing Service. Maybe this could be
> the cause, but I am not sure.
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLC/u5AAoJEF+XTK08PnB5BooP/j6QW+4SytkZvepNP65B7TMy
2E104XqZIatehpoF8suxJVuaBkqnGM/1qLgoOZ6iJKj9yklNDJ5WQaQYgU012kJ8
g6TQCRFRN9zcgP8bg8xL0YTRuQNrBFe62dLKNPvOjqjuvVuR6BuNFHsj1jJtpamH
BHfKvkieuc2o5GG+JBK7xg1T9yy361pXAwdyvwbTU0kf280/BCjsX8XC/cV+LexL
o5VkANO/IoFU/91SbpuZ43yhO5gRjkW7JwKNPasdjJLZtfNi5tYoFTBtAV3LM1jJ
BB+MqsD+zI5EvbklEMDBoZPCpo/zA3NY2E9smiUcbsTetr+V2w1bOj7exLqG6fu9
saUTzN7dYWUmVN0YcWdDhJGI9GDPHaOVRV4G71lV6bfYFc9F8Cz+IdQCXtIGZ2HV
oFwIXURzEJ6t8rDFr+PkBlTDfECKzhIVeYml3DHJJ6QkXnnMPAnDpfa9AVSaC+8l
v2d3RWxin78ClKryVVeUAV9LNQyZUIZjPalu91YHq8Sm4X3jb/7x19k6JdkXlWVr
6EyD3juUMo84sDFtM6zfQ5lQr56E2rMNKFf3Ipwmsf+l/05a/C3ksxgxN4HgqZSi
X2idLaxtwrkvrLHaXMeocLJOjxRnd/ZLQikRN5tIJ81/TEVXZ/Zu5vAVJQ2ndJEt
Ck8C1/z/4Hn18jlRoD32
=DlMP
-----END PGP SIGNATURE-----
0 Likes
9734555 Absent Member.
Absent Member.

Re: apache2 could not bind to address 0.0.0.0:631

Okay; now I know for sure that this error is related to the new VMware ws 7 "Virtual Printing Daemon". It is a ThinPrint-daemon which will be automatically enabled during booting of a OES2 server. I have disabled it from the /etc/init.d/vmware-tools script.
Now my problems are gone and the apache2-daemon just runs fine.
0 Likes
Knowledge Partner
Knowledge Partner

Re: apache2 could not bind to address 0.0.0.0:631

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sounds good. Thank-you for posting back your results.

Good luck.





9734555 wrote:
> Okay; now I know for sure that this error is related to the new VMware
> ws 7 "Virtual Printing Daemon". It is a ThinPrint-daemon which will be
> automatically enabled during booting of a OES2 server. I have disabled
> it from the /etc/init.d/vmware-tools script.
> Now my problems are gone and the apache2-daemon just runs fine.
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLDAJ/AAoJEF+XTK08PnB5AwwP/idE7s5BJoZnyrKyxBeMQKJy
UNhzpfZjO/G6DPCFepW8ewRsW2/5nG17X+8eIBCAhy9vSiFMwbblgOWePrI3Ll7c
wzw/pExliaXZawTd4M02DkwuNkfQ9XRsjZ/BgHWWuOmRDovUs0GCa/a5eisVMIJi
+FI58eadokkJimLB8nluULq8aKP+0krdMvpirgIoaMQyEEE7EnpW9wrSEhRUeKmu
lDdVMJNkhyT53NWQLARjUn04M69ndog5dcw4iRZ6LeztRuv0dTUFah6vZXpv8gj7
e5v3yQ6cuUTvQvqbsAP3pZkZyg0+or5Tk77YDsTEyx7C8RV6CWNl3JpEs+LzeyZU
KZXeswWZ6Rg/xNHFI2FuEc7C0934T7hHo0PFzaY+71dl2or+uuBQTf9ASIzbnowW
ntdWp2bX2jiSioJGBR8VFsnrZZ/kSffpEk1bjRaF6UuHFUR0w7Rjfe2ctoVQFuM6
q+ZJUrYw4WA12CZseaSmu80a+IxvxwWTSbXCO/gq0oSDQiQMI1pdTg0ONyB4wWPx
zTTOBWOGuJiFLwDOMXpTFCcRveX/IO7MQ9MR9utzZoSl0kmUPDxgZS+JUI+nqLLQ
4b5j134eSjyqRycjY9pkpjH9rGohX+z02MKAoc09dj0ADJNwNlI1UqAPXOb9B2pj
y3Upnhi+r3rDZ88oFl42
=lnT6
-----END PGP SIGNATURE-----
0 Likes
Micro Focus Contributor
Micro Focus Contributor

Re: apache2 could not bind to address 0.0.0.0:631

9734555;1894658 wrote:
Okay; now I know for sure that this error is related to the new VMware ws 7 "Virtual Printing Daemon". It is a ThinPrint-daemon which will be automatically enabled during booting of a OES2 server. I have disabled it from the /etc/init.d/vmware-tools script.
Now my problems are gone and the apache2-daemon just runs fine.


I had the excat the same error when running iPrint in VmWare and the above solution helped me resolve the issue.

Thank you so much. There has to be a TID written for this one.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.