Imported from the Apple Support Forums via the Wayback Machine 🔗
I can't manage to find documentation anywhere which states what portion of Web Services uses port 9010. I'm setting up a Snow Leopard server (all current updates installed) for a client, and they need to use Readerware for their library database and management: http://www.readerware.com/.
The server component kept throwing errors about port 9010 when it would start as it uses 9010 as its "control port" in communications with client software. Readerware support pointed me in the direction of Web Services, though just turning them off doesn't fix the problem. Even though a Port Scan in Network Utility shows 9010 as clear after flipping the big switch in Server Preferences, Readerware still throws errors and refuses to work correctly. Only if I switch off Web Services, reboot the server, and immediately start Readerware, will it work. If I turn Web Services on, Readerware continues to operate correctly until the server component is quit and relaunched. Then, 9010 port-in-use errors again.
My Snow Leopard Server install is still fairly virgin, and I haven't done anything to change Web Services other than turn it on and off. No software firewall is running. The Webmail component of Web Services is turned off as the Mail service itself is turned off. The obvious solution to me would be to customize the control port of Readerware, but they don't seem to offer that option.
Imported from the Apple Support Forums via the Wayback Machine 🔗
Out of the box, Apache is configured to use port 9010 as the monitoring port used by Server Admin and the various mod_status tools to check on server activity.
You can certainly disable these in /etc/apache2/httpd.conf but I'd expect Server Admin to lose its ability to monitor the server.
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks Camelot. That's a huge lead.
Does anyone else know for sure if Server Admin would function incorrectly (or unexpectedly) if I changed the port in the httpd.conf file to something else? Server Admin seems to work okay if I have Web Services shut down, start up this Readware database software, and then start Web Services. At least, I've not found a place where it doesn't work yet. Changing that port in httpd.conf seems like the simplest solution by far, but that's assuming there are no other ramifications (or that they won't affect my client's setup if there are).
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
…to add more to this, the Apache server status page on 9010 (http://localhost:9010/server-status/) appears to be localhost only. I can view it from Safari on the server, but even with all firewalls down and the server on the DMZ, I can't see it from the Internet. I'm working on my server remotely right now, so I can't test it from on the same subnet, but I suspect it wouldn't work there either. httpd.conf reads:
Listen 127.0.0.1:9010
So would commenting this out actually break Sever Admin? I'm using Server Admin from my MacBook over the Internet now, and it appears to be working exactly the same as Server Admin on the server itself through ARD.
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
That's absolutely correct. You don't typically want to expose the data that /server-status and /server-info give to the outside world.
So would commenting this out actually break Sever Admin?
Yes, because Server Admin doesn't communicate with Apache over port 9010.
Server Admin.app talks to servermgrd, a daemon process that runs on Mac OS X Server. Server Admin.app tells servermgrd what information it wants and servermgrd collects that data and returns it to the GUI app.
Since servermgrd lives on the server itself it's quite capable of communicating with Apache on localhost port 9010.
The other possible solution to your problem is to configure your other app so that it listens on a specific IP address rather than * - that way localhost:9010 can be the regular apache/Server Admin interface, while 192.168.1.2:9010 could be your ReaderWare app (if it supports this kind of configuration).
0
Apple Support Community member·
Imported from the Apple Support Forums via the Wayback Machine 🔗
…indeed, before seeing your reply I tried changing the port number and commenting out that line in httpd.conf, and Server Admin and Server Preferences freaked out. Thanks Camelot. Very helpful information. Will try to go another route.