apache2 could not bind to address 0.0.0.0:631 after vSphere upgrade

After the upgrade from vSphere 4.0x to vSphere 4.1 or ESXi 4 to ESXi4.1 apache on a OES 2 server wouldn’t start with the error

apache2 could not bind to address 0.0.0.0:631

As you all probably know TCP port 631 is for IPP print, or for us Novell guy’s iPrint. iPrint is started with apache (the website that is). But if iPrint cannot start, apache wouldn’t start also. So what’s blocking TCP port 631? The must be another service that’s using TCP port 631 for ipp printing. After some investigation I discovered that CUPS was started on the OES 2 server. And CUPS also uses ipp and so TCP port 631. So shutting down CUPS enabled me to start apache (rcapache start). Of course you have to make sure that CUPS isn’t started by default anymore on boot time (insserv -r /etc/init.d/cups).

But what started CUPS because it wasn’t started at boot time before. The only change that was made on the OES 2 was the upgrade of the VMware tools. So that was it.

I must say, not really nice of VMware to enable the start of daemons that weren’t started by default before? I don’t know what the reason is why they want to start CUPS for the VMware tools? So if you know the reason, let me know!

About Michael
Michael Wilmsen is a VMware training/consultant (no specific order) with more than 15 years in the IT industry. Main focus is VMware vSphere, Horizon View and Site Recovery Manager with a deepdive to performance. Michael is VCDX 210, VCAP 4/5 certified, has been rewarded with the vExpert title from 2011, is a PernixPro, Nutanix Tech Champion and a Nutanix Platform Professional.

6 Comments to “apache2 could not bind to address 0.0.0.0:631 after vSphere upgrade”

  1. By Miguel, October 13, 2010 @ 20:07

    The same issue happens with OES2 sp2 latest patches.

  2. By Miguel, October 13, 2010 @ 20:07

    The same issue happens with OES2 sp2 latest patches.

  3. By Simon Flood, November 18, 2010 @ 11:40

    I’ve just commented on your recently published Cool Solutions article – basically the issue is with later versions of VMware Tools as that now includes something called ThinPrint. This provides virtual printing from within VMs and on Linux-based VMs uses CUPS …

    See TID #7007214 for more information and a fix.

  4. By Simon Flood, November 18, 2010 @ 11:40

    I’ve just commented on your recently published Cool Solutions article – basically the issue is with later versions of VMware Tools as that now includes something called ThinPrint. This provides virtual printing from within VMs and on Linux-based VMs uses CUPS …

    See TID #7007214 for more information and a fix.

  • Apache with iPrint won’t start even if CUPS is disabled « — December 28, 2010 @ 13:19

  • Apache with iPrint won’t start even if CUPS is disabled « — December 28, 2010 @ 13:19

  • RSS feed for comments on this post. TrackBack URI

    Leave a Reply

    You must be logged in to post a comment.