2 Replies Latest reply on Jun 20, 2017 3:01 AM by desktoporga_fba

    FileMaker Server crashes because of huge Stderr.log

    desktoporga_fba

      FileMaker Server 14 and 15 produce form time to time huge file "Stderr.log", so that FM-Server cannot work anymore.

      Sometimes a new installation becomes necessary.  This happens to several of our customers.

       

      We are thinking of Installing FMS 16 - but are not shure if this will solve the problem. It is mentioned since  a long time gain and again.

       

      We sliced one of these huge Stderr.log-files: ere are 100 MB of it which is zipped only 373 KB

       

      This is how the loop starts:

      ...

      FlateDecode: decoding error: unknown compression method.

      Error (31): Bad delta-height value in JBIG2 symbol dictionary

      FlateDecode: decoding error: unknown compression method.

      omniORB: Warning: the local loop back interface (127.0.0.1)

      is the only address available for this server.

      omniORB: Warning: the local loop back interface (127.0.0.1)

      is the only address available for this server.

      Error (41): Invalid symbol number in JBIG2 text region

      Error (44): Invalid symbol number in JBIG2 text region

      Error (47): Invalid symbol number in JBIG2 text region

      Error (56): Invalid symbol number in JBIG2 text region

      Error (59): Invalid symbol number in JBIG2 text region

      Error (62): Invalid symbol number in JBIG2 text region

      Error (65): Invalid symbol number in JBIG2 text region

      Error (67): Invalid symbol number in JBIG2 text region

      Error (70): Invalid symbol number in JBIG2 text region

      Error (72): Invalid symbol number in JBIG2 text region

      .... a few loops later:

      Error (50911): Invalid symbol number in JBIG2 text region

      Error (50911): Invalid symbol number in JBIG2 text region

      Error (50911): Invalid symbol number in JBIG2 text region

      ... and so on.

       

      The funny thing is: the number of  Error (50911):  is no more increased.

       

      Later in this file are only RETURNs - so I dont transmit this.

       

      Has anybody a hint how to stop this?

       

      Has FileMaker itself a hint for solving this SERIOUS problem?

       

      Thanks for answers that help.

        • 1. Re: FileMaker Server crashes because of huge Stderr.log
          TSGal

          desktoporga_fba:

           

          Thank you for your post and file.

           

          This appears FileMaker is trying to uncompress a file/image/PDF.  What can you tell me about the file?  I also see there are references to fonts not being found (F_2, F_3, F_4, F_5).

           

          What are the clients doing at the time of these entries?

           

          TSGal

          FileMaker, Inc.

          • 2. Re: FileMaker Server crashes because of huge Stderr.log
            desktoporga_fba

            I talked with my customer's admin - but this is not to find out, because nobody notices when this process starts.

            We have up to 20 clients in several locations ... no way to find out which client-action triggers this. Sorry.

             

            But there is one hint: This customer had often server-shutdowns with FM-Server 13, when many PDF's have been postet in a short time. Since FM-Server we don't have this problem anymore - but now we have the Stderr.log-problem, about once a week or once in two weeks.

             

            WW/DTO