Apple Event: May 7th at 7 am PT

> Learn more

> Add to your calendar 

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

User profile for user: menzbua
menzbua Author
User level: Level 1
9 points

No Webservices starting on OSX Server 5.0.15

Hi @all,


i have a problem with my OSX Server 5.0.15. Today i've insalled the latest security patches for OSX 10.10 and i have to reboot the server. After the reboot no webservices on the server comes up. Not the normal Webserver and also not the Calender and the Contactsserver. I don't know how i can troubleshoot this issue. In lsof -i -n -P i see that nothing listens on port 80 or 443 but i see other ports listening by httpd:


sudo lsof -i -n -P |grep httpd

httpd 520 root 4u IPv4 0x447c87e2169cc417 0t0 TCP 127.0.0.1:35443 (LISTEN)

httpd 520 root 5u IPv4 0x447c87e2169cbb47 0t0 TCP 127.0.0.1:35480 (LISTEN)

httpd 531 _www 4u IPv4 0x447c87e2169cc417 0t0 TCP 127.0.0.1:35443 (LISTEN)

httpd 531 _www 5u IPv4 0x447c87e2169cbb47 0t0 TCP 127.0.0.1:35480 (LISTEN)

httpd 4355 root 4u IPv4 0x447c87e21904f9a7 0t0 TCP 127.0.0.1:35243 (LISTEN)

httpd 4355 root 5u IPv4 0x447c87e2150f0277 0t0 TCP 127.0.0.1:35280 (LISTEN)

httpd 4363 _www 4u IPv4 0x447c87e21904f9a7 0t0 TCP 127.0.0.1:35243 (LISTEN)

httpd 4363 _www 5u IPv4 0x447c87e2150f0277 0t0 TCP 127.0.0.1:35280 (LISTEN)

httpd 4367 root 4u IPv4 0x447c87e218e71417 0t0 TCP 127.0.0.1:34580 (LISTEN)

httpd 4367 root 5u IPv4 0x447c87e218e68417 0t0 TCP 127.0.0.1:34543 (LISTEN)

httpd 4380 _www 4u IPv4 0x447c87e218e71417 0t0 TCP 127.0.0.1:34580 (LISTEN)

httpd 4380 _www 5u IPv4 0x447c87e218e68417 0t0 TCP 127.0.0.1:34543 (LISTEN)


I've also resetted the hole webserver with the command serveradmin command web:command=restoreFactorySettings and deleted the /Library/Server/Config/apache2 directory but this also did not helped.


Could anyone help me troubleshoot this issue?


Thanks a lot


Regards

Manuel

Mac mini, OS X Server

Posted on Feb 9, 2016 11:00 AM

Reply
28 replies
User profile for user: MrHoffman
MrHoffman
Community+ 2024
User level: Level 10
116,997 points

Feb 16, 2016 1:06 PM in response to menzbua

menzbua wrote:


But i can not disable the Serverwebsites regardless the 80 or the 443 site?


Are you getting an error when you attempt to disable the server web sites, or the sites are not getting disabled?


That there are issues shutting off the sites is not a huge surprise, given Apache appears to be failing. Shut off what you can in the configuration, save, and reboot.


Or are you indicating that you cannot test this, because you require HTTPS TCP 443 sites to be active?


One-line answers can be surprisingly difficult to interpret, unfortunately.


It'll likely be easier and more efficient and more expeditious to get some formal help here. From Apple support, or otherwise.

Reply
User profile for user: menzbua
menzbua Author
User level: Level 1
9 points

Feb 16, 2016 11:38 PM in response to MrHoffman

Sorry for the one liner but the problem is i can not disable the SSL Serverwebsite over the Server.app because the button to delete the Sites is greyed out. So if i want to disable it i can not do it.

I removed all Webserver configurations that i can. The only thing that is left is the Serverwebsite for Port 80 and the Serverwebsite for Port 443 and these two can not be deleted. I've also disabled the Calendarserver and the Contactserver. So on the Server is only the Mail and the Time-Machine Server running.

Reply
User profile for user: menzbua
menzbua Author
User level: Level 1
9 points

Feb 17, 2016 7:43 AM in response to menzbua

After file permission repair fallowing status.

I can start the Webserver via the Server.app (that works before too). When i take a look at sudo launchctl list |grep proxy i see that serviceproxy is not started:


sudo launchctl list |grep proxy

- 0 com.apple.odproxyd

- 0 com.apple.kcproxy

- 0 com.apple.serviceproxy


After unloading the service proxy sudo launchctl unload /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons/com.a pple.serviceproxy.plist and reload it again sudo launchctl load /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons/com.a pple.serviceproxy.plist the service proxies are there


sudo launchctl list |grep proxy

- 0 com.apple.odproxyd

- 0 com.apple.kcproxy

2280 0 com.apple.serviceproxy


ps auxw |grep servicep

_www 2287 0,0 0,0 2445920 2032 ?? S 4:37pm 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

_www 2286 0,0 0,0 2445920 2020 ?? S 4:37pm 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

_www 2285 0,0 0,0 2445920 2020 ?? S 4:37pm 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

_www 2284 0,0 0,0 2445920 2132 ?? S 4:37pm 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

_www 2283 0,0 0,0 2445920 2140 ?? S 4:37pm 0:00.01 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log

root 2280 0,0 0,1 2445920 5576 ?? Ss 4:37pm 0:00.13 /usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf -E /private/var/log/apache2/service_proxy_error.log


And now the Webserver is up and running. So this is not the perfect solution but i know now how to fix the problem. But if we can find now, why i have manually load the service proxies that would be great. Because when i stop the server in the Server.app and start it again i have to unload and load the service proxies to get the webserver reachable via 80 or 443.

Reply
User profile for user: pterobyte
pterobyte
User level: Level 6
11,098 points

Feb 18, 2016 2:48 AM in response to menzbua

When you reload it, try and use the -w option and see if it sticks now.


sudo launchctl load -w /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons/com.apple.serviceproxy.plist


Also, have a look at the output of:


launchctl print system/com.apple.serviceproxy


This should give you information about it.


Note: load -w is a legacy command but it still mostly works. If it doesn't, try:


launchctl enable system/com.apple.serviceproxy


You may also want to have a look at:


man launchctl


as many things have changed with launchd/launchctl. There are also more debugging functions available.


I know that the legacy commands and behaviour often still apply. But of course not always.


HTH,

Alex

Reply

No Webservices starting on OSX Server 5.0.15

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.
Learn more Sign up