We are receiving a bunch of API Unexpected Data errors in the logs daily. We use local email piping.

Attached below is a photo of the error. There is no IP address in the error so I am assuming that means it is something with our server and not someone from the outside.

I'm not sure if this is related but we are having a very hard time getting the closed tickets queue to load at all. We have about 1100 tickets in our system. Total space used is 314.47 MiB and space for attachments is 291.34 MiB. Attachments are being stored in the database.

We are running 1.11-rc1 because we had to have the CC functionality. The server is GoDaddy.

Any suggestions?

I would not recommend using a [buggy] Release Candidate in a production environment. I would recommend that you restore from back and revert back to your old version. Also there may have been some changes in the api between 1.10.x and 1.11rc1.

Unfortunately, we started on 1.11-rc1 when we put this server in back in June so there is no backup to revert to.

I know the developers don't generally disclose how close they are on new releases but any idea when 1.11 stable will be out?

Thanks,
Daniel

I'm hoping by the end of December. But they don't tell me things like release dates (because then i usually share them).

3 months later

We are still getting these API errors. We are using email piping but I have also had it throw this error when doing regular email fetching.

API Unexpected Data
system_emails: Unexpected data received in API request

as well as:
API Unexpected Data
thread_entry_recipients: Unexpected data received in API request

These errors show up each time an email is received.

Version info below:

    Hi pablopol24 I have been using 5.6 and we have been getting these same errors. I tried using 7.2.6 since it is supposed to be supported in 1.11 but it appears 7.2.6 does not work with 1.11. We have had to revert back to 5.6 or all of our tickets show up empty.

    Has anyone else seen any of these API errors in the log and know what might be causing it? All of our tickets come in via email. We use email piping on the local server if that matters.

    Thanks,
    Daniel

      5 months later

      I've just installed a fresh copy of v1.12 and am experiencing this same issue.

      Email is piped in via Postfix transport. Each incoming email causes two "API Unexpected Data" events to appear in the log:
      1. system_emails: Unexpected data received in API request
      2. thread_entry_recipients: Unexpected data received in API request

      Is there a method to debug the API request? I'm curious if this error is due to a bug in osTicket, or if the error is in how I've setup the Postfix transport. The flags to pipe are DRhu. Is this correct?

      PHP is v5.6.40-0+deb8u4
      all PHP extensions listed at (Admin -> Dashboard -> Information) are checked/installed

      5 days later

      @nnunn please do not be a necromancer.
      Please start your own thread.

      Write a Reply...