2 Replies Latest reply on Sep 29, 2010 12:41 PM by mps1773

    FMS server errors

    mps1773

      Title

      FMS server errors

      Your post

      Yesterday FMS logs reported the following errors:

      9/28/10   7:06 Web Server Error [0100:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc1)   Connecting to tomcat failed. Tomcat is probably not started or is listening   on the wrong port
      9/28/10 7:06 Web Server Error [0100:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc2)   Connecting to tomcat failed. Tomcat is probably not started or is listening   on the wrong port
      9/28/10 7:06 Web Server Information wpc 192.168.4.13 0.003524
      9/28/10 7:06 Web Server Error [12653:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc1)   Connecting to tomcat failed. Tomcat is probably not started or is listening   on the wrong port
      9/28/10 7:06 Web Server Error [12653:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc2)   Connecting to tomcat failed. Tomcat is probably not started or is listening   on the wrong port
      9/28/10 7:06 Web Server Information wpc 192.168.4.13 0.003787
      9/28/10 7:06 Web Server Error [0100:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc1)   Connecting to tomcat failed. Tomcat is probably not started or is listening   on the wrong port
      9/28/10 7:06 Web Server Error [0100:0000] [error] ajp_service::jk_ajp_common.c (1953): (wpc2)   Connecting to tomcat failed. Tomcat is probably not started or is listening   on the wrong port
      9/28/10 7:06 Web Server Information wpc 192.168.4.13 0.059217

      I was out of the office yesterday so I am as yet unaware of any issues from yesterday.  Today I was made aware of peculiar behavior from the hosted databases.  Upon closing down the database server and restarting the server's computer the database server would not start back up, stating that it failed to communicate with database server.  I had to restart the FMS machine multiple times.  It finally came online 26 minutes later but only after I disabled the Web Sharing feature in the OSX preferences.  The following are the relevant FMS log entries from the various startup attempts:

      9/29/10   9:45 Server Events Information Maximum number of files to host: 64
      9/29/10 9:45 Server Events Information The cache will flush every 3 minutes.
      9/29/10 9:45 Server Events Information File list filtering: Disabled
      9/29/10 9:45 Server Events Information Client authentication method: FileMaker and External Server.
      9/29/10 9:45 Server Events Information Disconnect idle clients enabled.
      9/29/10 9:45 Server Events Information Maximum idle client time: 12:00:00
      9/29/10 9:45 Server Events Information Sample statistics every 3 seconds.
      9/29/10 9:45 Server Events Information Automatic updates enabled.
      9/29/10 9:45 Server Events Information Server scheduling enabled.
      9/29/10 9:45 Server Events Information Schedule "Daily" scheduled for 09/29/2010 11:00 PM.
      9/29/10 9:45 Server Events Information Schedule "Weekly" scheduled for 10/01/2010 11:00 PM.
      9/29/10 9:45 Server Events Information Schedule "Every 2 Hours" scheduled for 09/29/2010 11:00 AM.
      9/29/10 9:45 Server Events Information Schedule "Nightly WMS Maintenance" scheduled for 09/30/2010   02:07 AM.
      9/29/10 9:45 Server Events Information Schedule "Status Pairing Routine" scheduled for 09/29/2010   09:55 AM.
      9/29/10 9:45 Server Events Information Default backup location: filemac:/Macintosh HD/Library/FileMaker   Server/Data/Backups/
      9/29/10 9:45 Server Events Information Administrator authentication method: Password required
      9/29/10 9:45 Server Events Information Secure (SSL) Network Encryption: Disabled
      9/29/10 9:45 Server Events Information Starting FileMaker Database Engine...
      9/29/10 9:45 Server Events Information Open files without consistency check: Disabled
      9/29/10 9:45 Server Events Information Server host name type: Custom
      9/29/10 9:45 Server Events Information Server host name: FileMaker Server 11
      9/29/10 9:45 Server Events Information Maximum number of client connections configured in FileMaker Server: 40
      9/29/10 9:45 Server Events Information Maximum number of Web Publishing Engine sessions configured in FileMaker   Server :  100
      9/29/10 9:45 Server Events Information Database cache size: 64 MB.
      9/29/10 9:45 Server Events Information XDBC connections are allowed.
      9/29/10 9:45 Server Events Information FileMaker Database Engine started.
      9/29/10 9:45 Server Events Information Starting FileMaker Server 11.0v2 (06-02-2010)...
      9/29/10 9:45 Server Events Information Client access logging enabled.
      9/29/10 9:45 Server Events Information Maximum size of log file: 64 MB
      9/29/10 9:45 Server Events Information Email notification to administrators: Errors only
      9/29/10 9:45 Server Events Information Statistics logging enabled.
      9/29/10 9:45 Server Events Information Default database location: filemac:/Macintosh HD/Library/FileMaker   Server/Data/Databases/
      9/29/10 9:45 Server Events Information Additional database folder: Disabled
      9/29/10 9:45 Server Events Information Runtime Solutions custom database extensions: Enabled
      9/29/10 9:45 Server Events Information Maximum number of client connections permitted by FileMaker Server   License:  Unrestricted
      9/29/10 9:45 Server Events Information Maximum number of Web Publishing Engine sessions permitted by FileMaker   Server License :  100
      9/29/10 9:45 Server Events Information XDBC connections are allowed by this FileMaker Server license.
      9/29/10 9:45 Server Events Information XDBC connections are not allowed.
      9/29/10 9:45 Server Events Information IWP connections are allowed by this FileMaker Server license.
      9/29/10 9:31 Publishing Engine Information FM Web Publishing - - wpc1 Launch failed - incompatible server type.
      9/29/10 9:31 Publishing Engine Information FM Web Publishing - - wpc1 task wc::DracoGlobals failed!
      9/29/10 9:31 Publishing Engine Information FM Web Publishing - - wpc1 Launch failed - incompatible server type.
      9/29/10 9:31 Publishing Engine Information FM Web Publishing - - wpc1 task wc::DracoGlobals failed!
      9/29/10 9:19 Server Events Information FileMaker Database Engine stopped.

      All of the remaining log entries are normal activity with no abnormalities.

      We are using FMSA 11.0.2.217 with clients using FMP 11v1, FMP 11v2, FMP 10v3 (Windows PCs) and I use FMPA 11v2 & FMP 11v2.  The FMS machine is OSX 10.6.4 running on a mac mini with hardware specs surpassing recommended system specs.

      I can readily supply full logs & system profile files to FileMaker reps upon request.

        • 1. Re: FMS server errors

          mps1773:

          Thank you for posting.

          It appears that one of the FileMaker Server processes is not starting. This is likely an issue with the installation.

          Besides reinstalling, here are some other options:

          1. Remove all hosted databases to make sure none are causing the problem. This probably isn't the case since the process fails to start before the databases are opened.
          2. Disable all non-essential startup services and applications. Is this machine dedicated to FileMaker Server?
          3. Check for recent configuration changes or system updates.

          Since the Web Sharing seems to be involved, it may help to reset the Apache settings to the default with the below terminal command and then redeploying FileMaker Server:

          sudo cp /etc/apache2/original/httpd.conf /etc/apache2/httpd.conf

          TSuki
          FileMaker, Inc.

          • 2. Re: FMS server errors
            mps1773

            Hello TSuki,

            The configuration of the FMS has been stable for quite some time with no changes being made to the settings or installation.  The only possibility that occurs to me would be updates issued by Apple.  I seem to recall there was an update or two in the previous week (one a security update, I believe) but the machine was restarted twice and has been running normally and continuously until today.  We have not had the WPE turned on since shortly after FMGo was initially released.

            The FMS machine is dedicated to the FMS and an FMP robot and has no other purpose. 

            Still, I had already decided to do a fresh reinstall on Friday and I will try as you suggest with the Apache settings.  What you have suggested makes much sense to me with what I have discovered so far.

            Thank you,

            Matthew Smith