3 Replies Latest reply on Jan 22, 2015 10:53 PM by Markus Schneider

    wpc_access_log, is extremely large

    jwshelton22

      Title

      wpc_access_log, is extremely large

      Your post

           The Filemaker 11 Server Advanced file, wpc_access_log, is extremely large, +3GB.

           I was going to rename it and let a new be created but it stated it was open in fmswpc.exe.

           I could not locate that file.

           How should I trim down the wpc_access_log file?

           Windows server.

           thanks,

           Jim

        • 1. Re: wpc_access_log, is extremely large

               Jim Shelton:

                

               Thank you for the post. 

                

               The file is opened by the fmswpc.exe FileMaker Server 11 Advanced process. If FileMaker Server 11 Advanced is first stopped, then the log can be moved.

                

               Additionally, the FileMaker Server 11 Advanced Admin Console has a setting to limit the log size: 

                

               Configuration > Web Publishing > General Settings > "Log Size:"

                

               For more information, review "Logging and statistics settings" on page 69 of the FileMaker Server 11 Advanced Help Guide.

                

               TSFalcon

               FileMaker, Inc.

          • 2. Re: wpc_access_log, is extremely large
            TWE

            Last year I set the size you indicated to 40 MB. The wpc_access_log.txt file is now over 800 MB. What do I need to do to limit the size of this file? I'm running FM server advanced 12. Windows says, as you mentioned, that the file was opened by fmwxpc.exe.

            • 3. Re: wpc_access_log, is extremely large
              Markus Schneider

              AFIK, the log size is just for the FM Server log. Other logs (wpe, etc) will fill every Disk if something goes mad. Logging can be disabeled, IMHO the only solution (at least with FMS11)

              We have had this back in 2011 - we had to disable the log's. Runs fine now, although debugging is no longer possible (iwp)