0 Replies Latest reply on Dec 11, 2014 6:17 PM by travispressestheredbutton

    After upgrading to Mac OS 10.9.5 it no longer publically serves the Admin Console

    travispressestheredbutton

      Title

      After upgrading to Mac OS 10.9.5 it no longer publically serves the Admin Console

      Your post

      After upgrading to 10.9.5 I could no longer access my admin console on 16000/16001. I can still load my FM Databases but cannot access anything in the browser. If I Share Screen onto my server I can hit the Admin Console on localhost.

      My theory is that the update is now serving the OS Apache and not the FileMaker Apache. It seems like it is - the error file specified by '/usr/sbin/apachectl -V' is updating when I hit and fail the landing page on port 80.

      The log file at  /Library/FileMaker\ Server/HTTPServer/logs/error_log is not updating for errors occurring on any page. 

      I normally restart apache with  sudo httpd -f /Library/FileMaker\ Server/HTTPServer/conf/httpd.conf -k graceful. But now I get the following errors:

      (48)Address already in use: make_sock: could not bind to address [::]:80

      (48)Address already in use: make_sock: could not bind to address 0.0.0.0:80

      no listening sockets available, shutting down

      Unable to open logs

      So I try to stop the current instance of apache so I can manually start the filemaker instance. First I confirm port 80 is running something:

      database_admin$ sudo lsof -i :80

      COMMAND   PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
      httpd   83997 root    5u  IPv6 0xdb5bb2afe9938681      0t0  TCP *:http (LISTEN)
      httpd   83998 _www    5u  IPv6 0xdb5bb2afe9938681      0t0  TCP *:http (LISTEN)
      httpd   84001 _www    5u  IPv6 0xdb5bb2afe9938681      0t0  TCP *:http (LISTEN)

      These are the services running on port 80 preventing FM Apache from running.

      database_admin$ sudo /usr/sbin/httpd -k graceful-stop
      database_admin$ sudo lsof -i :80
      COMMAND   PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
      httpd   86000 root    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)
      httpd   86001 _www    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)
      httpd   86001 _www   15u  IPv6 0xdb5bb2afe8ae09c1      0t0  TCP db.myserver.com:http->claptona.database.com:33678 (ESTABLISHED)
      httpd   86004 _www    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)
      httpd   86004 _www   15u  IPv6 0xdb5bb2afdeb5bd01      0t0  TCP db.myserver.com:http->claptona.database.com:33679 (ESTABLISHED)
      httpd   86005 _www    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)
      httpd   86006 _www    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)

      We then wait a few minutes and get

      database_admin$ sudo lsof -i :80
      COMMAND   PID USER   FD   TYPE             DEVICE SIZE/OFF NODE NAME
      httpd   86000 root    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)
      httpd   86004 _www    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)
      httpd   86006 _www    5u  IPv6 0xdb5bb2afe4959241      0t0  TCP *:http (LISTEN)

      So something is forcing these processes to run. I cannot turn them off. The command originates as '/usr/sbin/httpd -D FOREGROUND'. 

       

      Is anyone else having this issue? I'd be happy to get my OS Apache instance back but I don't want to spend any more time configuring my OS Apache when we're supposed to be running FIleMakers.