Announcement

Collapse
No announcement yet.

Errors in Logs - Duplicate entry & Invalid byte sequence

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Errors in Logs - Duplicate entry & Invalid byte sequence

    I've been seeing some strange errors today. I recently upgraded my advanced pack to the newest version and implemented the Google calendar integration. I don't think either of those is the problem, but these errors did show up afterward.

    I've had the duplicate entry error for 2 days now. It displays at what seems like random times. Lots of empty Job errors and now just recently that stream error. Any idea what these mean or what I can look for to fix them?

    []
    [2017-07-21 15:42:05] Espo.ERROR: EmailAccount 58ad8c3d76bb230dd (Import Message w/ MailMimeParser): [23000] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5972208ba8fc57b76-588a06f64cd9e0bb7' for key 'UNIQ_12A5F6CCA832C1C9A76ED395' []
    []
    [2017-07-21 15:42:15] Espo.ERROR: CronManager: empty Job entity [5972205426ad7cff5]. []
    []
    [2017-07-21 15:42:15] Espo.ERROR: CronManager: empty Job entity [5972205461bdd5bfa]. []
    []
    [2017-07-21 17:20:33] Espo.WARNING: E_WARNING: stream_get_contents(): stream filter (convert.quoted-printable-decode): invalid byte sequence {"code":2,"message":"stream_get_contents(): stream filter (convert.quoted-printable-decode): invalid byte sequence","file":"/home/crm2/public_html/vendor/zbateson/mail-mime-parser/src/Message.php","line":901,"context":{"stream":"[resource] (stream)"}}
    []
    [2017-07-21 17:21:32] Espo.WARNING: E_WARNING: stream_get_contents(): stream filter (convert.quoted-printable-decode): invalid byte sequence {"code":2,"message":"stream_get_contents(): stream filter (convert.quoted-printable-decode): invalid byte sequence","file":"/home/crm2/public_html/vendor/zbateson/mail-mime-parser/src/Message.php","line":901,"context":{"stream":"[resource] (stream)"}}
    Last edited by joy11; 07-24-2017, 03:29 PM.

  • #2
    Hello
    all errors related with email fetching...

    Comment


    • #3
      I am getting a similar message, what do you mean "related with email fetching"?

      [2017-11-28 20:04:14] Espo.ERROR: API [PATCH]:/:controller/:id, Params:Array ( [controller] => Account [id] => 59f120be9b26f843a ) , InputData: {"orderstatus":"Rejected"} - SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a1dc13e32af6' for key 'PRIMARY' [] []
      [2017-11-28 20:04:14] Espo.ERROR: Display Error: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a1dc13e32af6' for key 'PRIMARY', Code: 23000 URL: /espocrm/api/v1/Account/59f120be9b26f843a [] []
      [2017-11-28 20:20:30] Espo.ERROR: API [PATCH]:/:controller/:id, Params:Array ( [controller] => Account [id] => 59f120be9b26f843a ) , InputData: {"orderstatus":"Rejected"} - SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a1dc50e4252a' for key 'PRIMARY' [] []
      [2017-11-28 20:20:30] Espo.ERROR: Display Error: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a1dc50e4252a' for key 'PRIMARY', Code: 23000 URL: /espocrm/api/v1/Account/59f120be9b26f843a [] []

      Advice?

      I have a workflow rule to send an email when a certain field is set to a certain value.
      The value was changed and later put back to the value that will send the email a new email.
      Last edited by khopper; 11-28-2017, 08:33 PM.

      Comment


      • tanya
        tanya commented
        Editing a comment
        You have accounts with the same id 5a1dc50e4252a. Check in database

    • #4
      Can you check the emails associated with that account? See if there is more then one email sent out or you could check your jobs table and see if your workflow is stuck on pending or failed. I think when I had my issue I turned my workflow inactive for a little bit while I was looking for the issue in the database and then when I turned it back on it kind of fixed itself.

      Comment


      • #5
        WOW - that is strange how just disabling the workflow and re-enabled it will resolve the issue.
        Tested and confirmed - I didn't even wait more than 5 Minutes before re-enabling the workflow.

        Tanya - is this a possible bug/glitch?

        Comment


        • #6
          I know that if you have a lot of jobs running that fail, the CRM has a tendency to start doing some strange things. Are your database tables set as ESPO's default of MyISAM? You may see processes time-out because they are waiting for prior jobs to complete before they can begin. Somewhere in the last update or two, there was an overwrite (I'm still unable to find it) that will create any new entity tables as MyISAM regardless of what the database default is. I've been manually changing them to InnoDB in the database to improve performance. This is just another thought which could affect errors with processes timing out.

          Comment


          • #7
            Tanya - I have checked my DB in the account.id table and '5a1dc50e4252a' does not exist.

            Comment


            • #8
              Starting to think this may be a bug!

              From error logs from a new instance - it's been happening a lot! I discovered that the ID is from the Notifications Table... I searched it for Dups but only 1 instance exist for 5a2ac2628e5dc.
              The error corresponds to the creation time of the record in the DB???? Wouldn't it have to exist prior to be considered a duplicate?

              [2017-12-08 16:48:34] Espo.ERROR: API [PATCH]:/:controller/:id, Params:Array ( [controller] => Account [id] => 5a050e4fa1a14df89 ) , InputData: {"orderstatus":"Rejected"} - SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a2ac2628e5dc' for key 'PRIMARY' [] []
              [2017-12-08 16:48:34] Espo.ERROR: Display Error: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a2ac2628e5dc' for key 'PRIMARY', Code: 23000 URL: /espocrm/api/v1/Account/5a050e4fa1a14df89 [] []

              Comment


              • #9
                Did you do any customization, related to notification or any workflow?

                Comment


                • #10
                  No, I have not.
                  I disabled one of the fields from being Audited and the error went away.
                  I later added it back to being an Audited field and it has not happened since.

                  Comment


                  • #11
                    What is type of this field?

                    Comment


                    • #12
                      The field name is "Order Status" and it is an ENUM field.

                      Comment

                      Working...
                      X