PHP Fatal error: Uncaught InconsistentModelException

KevinTheJedi

You will need to see what’s causing that. You should have an Issue Summary field on the Ticket Details form with a Variable of “subject”. If you have that you should have no issues. The problem would only occur if someone removed the field, removed the variable, or something along those lines.

Cheers.

bsanjay

Thanks KevinTheJedi, I couldn't figure out what's causing this bug, but the workaround you mentioned of dropping the ost_ticket__cdata table and running cron worked perfectly when the error was for the subject column, i.e. the Unknown column 'B4.subject' error.

Now, again I've run into the same issue with no tickets displaying, but the error is Unknown column 'B7.field_44' or sometimes its B6.field_44, and the dropping table and running cron solution does not work. I would like to find the cause of it, and possibly fix it, the thing that I was experimenting with when this new error came was I was creating a custom queue to display tickets data in a certain way, it was working good, but soon this popped up, I have even deleted that custom queue and dropped cdata table and re-run the cron, but no luck, don't know how to get the tickets to show up now, any help would be good.

Sidenote, this is my configuration:

KevinTheJedi

bsanjay

Well for one you didn’t read the requirements and installed an unsupported PHP version. Downgrade to PHP 8.2, install all the suggested extensions listed in the dashboard page, restart the web server, and retest.

Cheers.

bsanjay

Thanks @KevinTheJedi
I downgraded to 8.2, installed all extensions listed, restarted web-server, dropped ost_ticket__cdata table, ran cron, but sadly still getting the same - can't see any tickets, can only see ticket counts.

KevinTheJedi

bsanjay

What’s it saying.

Cheers.

bdeguire

Hi,
I've recreated the same problem on version 1.18.1.
The problem happens when I modified the normal ticket form (ID = 2) and added 2 new fields at the same time.
At that point, the column "subject" in "ticket__cdata" is renamed to "field_20".
Hope this helps!

KevinTheJedi

bdeguire

You'll need to post a lot of information. A screenshot of Admin Panel > Dashboard > Information. A screenshot or paste of the error you are receiving. A screenshot of your Ticket Details Form. Any other information you feel would be helpful.

Cheers.

bdeguire

KevinTheJedi
Hi KevinTheJedi,
Yes, sorry about that. Here is the screenshot and the error.

40207 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught InconsistentModelException: Unable to prepare query: Unknown column 'B4.subject' in 'field list' SELECT A1.numberASnumber, A1.ticket_idASticket_id, A1.sourceASsource, A1.lastupdateASlastupdate, B4.subjectAScdatasubject, A1.isoverdueASisoverdue, B6.nameASusername, B4.priorityAScdatapriority, B7.firstnameASstafffirstname, B7.lastnameASstafflastname, B8.nameASteamname, A1.team_idASteam_id, A1.isanswered= '0' AS2GkBZxz, (SELECT COUNT(R0.id) AScountFROMost_threadQ7 JOINost_ticketQ8 ON (Q7.object_type= 'T' AND Q7.object_id= Q8.ticket_id) LEFT JOINost_thread_entryR0 ON (Q7.id= R0.thread_id) WHERE Q8.ticket_id= A1.ticket_idAND NOT R0.flags& 4 != 0) AS _thread_count, (SELECT COUNT(R1.id) AScountFROMost_threadQ7 JOINost_ticketQ8 ON (Q7.object_type= 'T' AND Q7.object_id= Q8.ticket_id) LEFT JOINost_thread_entryR0 ON" while reading upstream

The resulting behaviour is the same as @bsanjay dated Dec 13 2024: https://forum.osticket.com/d/103665-php-fatal-error-uncaught-inconsistentmodelexception/8

Let me know if you have any more questions.

KevinTheJedi

bdeguire

I still need:

A screenshot of your Ticket Details Form.

Cheers.

bdeguire

KevinTheJedi

Sure, here you go. As a reminder, the problem occurs right after I add 2 fields at the same time : no error occurs if they are added one at a time.

KevinTheJedi

bdeguire

That is very odd as you have the Issue Summary field with variable of subject. So, try dropping the table in the db manually then running cron a bunch of times until it’s fully recreated and repopulated with data. It will take multiple cron runs to fully repopulate. Just keep running until data stops being added to the _ticket__cdata table.

The only other thing I can think of is the fact you have a language pack installed. It could be something was incorrectly translated and is now causing issues. We have new language pack builds coming soon and I’ve already gone in and corrected all known issues with all languages. So if the issue is with the language pack it should be resolved with the next builds.

Cheers.

bdeguire

KevinTheJedi

Hi,

In this short video, you can see the bug happening: inserting 1 field is fine, but 2 causes the bug.

osticketbug2.mp4

758kB

Another note: I've dropped the table and ran the CRON, and it recreated the table correctly! So it seems to be related with the form posting in some way...

Hope this helps!

akbass

I have the same issue as OP.
Running osticket in a docker instance
tiredofit/osticket:3.6.2, so
osTicket v1.17.6
mariadb:10.11
nginx version: nginx/1.25.1
PHP 8.2.8
Error pasted below

Dropping the ost_ticketcdata table and running cron a few times seemed to work. But it's consistent behaviour when adding a new form field. Doesn't matter if I set the new field to required or optional. Subject variable is there in the form and the ost_ticketcdata table.

I was considering rolling my own docker image to incorporate a newer osticket release (1.18.2?) if that would solve the problem. Any pointers/insights appreciated.
Thanks

Fatal error: Uncaught InconsistentModelException: Unable to prepare query:
SELECT 
  A1.`number` AS `number`, A1.`ticket_id` AS `ticket_id`, A1.`source` AS `source`,
  A1.`lastupdate` AS `lastupdate`, B2.`subject` AS `cdata__subject`, A1.`isoverdue` AS `isoverdue`, 
  B4.`name` AS `user__name`, B2.`priority` AS `cdata__priority`, 
  B5.`firstname` AS `staff__firstname`, B5.`lastname` AS `staff__lastname`, 
  B6.`name` AS `team__name`, A1.`team_id` AS `team_id`, A1.`isanswered` = '0' AS `2GkBZxz`, 
  (SELECT
    COUNT(R0.`id`) AS `count` FROM `ost_thread` Q7
    JOIN `ost_ticket` Q8 ON (Q7.`object_type` = 'T' AND Q7.`object_id` = Q8.`ticket_id`) 
    LEFT JOIN `ost_thread_entry` R0 ON (Q7.`id` = R0.`thread_id`)
    WHERE Q8.`ticket_id` = A1.`ticket_id` AND NOT R0.`flags` & 4 != 0
  ) AS _thread_count,
  (SELECT
    COUNT(R1.`id`) AS `count` 
    FROM `ost_thread` Q7
    JOIN `ost_ticket` Q8 ON (Q7.`object_type` = 'T' AND Q7.`object_id` = Q8.`ticket_id`) 
    LEFT JOIN `ost_thread_entry` R0 ON (Q7.`id` = R0.`thread_id`) 
    LEFT JOIN `ost_attachment` R1 ON (R1.`type` = 'H' AND R0.`id` = R1.`object_id`) 
    WHERE Q8.`ticket_id` = A1.`ticket_id` AND R1.`inline` = 0
  ) AS _att_count,
  B7.`expire` > NOW() AND NOT B7.`staff_id` = 1 AS `_locked`,
  (SELECT
    COUNT(R0.`id`) AS `count`
    FROM `ost_thread` Q7 
    JOIN `ost_ticket` Q8 ON (Q7.`object_type` = 'T' AND Q7.`object_id` = Q8.`ticket_id`) 
    LEFT JOIN `ost_thread_collaborator` R0 ON (Q7.`id` = R0.`thread_id`)
    WHERE Q8.`ticket_id` = A1.`ticket_id`
  ) AS _collabs,
  COALESCE(B5.`firstname`, B5.`lastname`, B6.`name`, 'zzz') AS `assignee`
FROM `ost_ticket` A1
JOIN `ost_ticket_status` A2 ON (A1.`status_id` = A2.`id`) 
LEFT JOIN `ost_thread` A3 ON (A3.`object_type` = 'T' AND A1.`ticket_id` = A3.`object_id`) 
LEFT JOIN `ost_thread_referral` A4 ON (A3.`id` = A4.`thread_id`) 
LEFT JOIN `ost_staff` A5 ON (A4.`object_type` = 'S' AND A4.`object_id` = A5.`staff_id`) 
LEFT JOIN `ost_thread` A6 ON (A1.`ticket_id` = A6.`object_id` AND A6.`object_type` = 'C') 
LEFT JOIN `ost_thread_referral` A7 ON (A6.`id` = A7.`thread_id`) 
LEFT JOIN `ost_staff` A8 ON (A7.`object_type` = 'S' AND A7.`object_id` = A8.`staff_id`) 
LEFT JOIN `ost_department` B0 ON (A4.`object_type` = 'D' AND A4.`object_id` = B0.`id`) 
LEFT JOIN `ost_department` B1 ON (A7.`object_type` = 'D' AND A7.`object_id` = B1.`id`) 
LEFT JOIN `ost_ticket__cdata` B2 ON (A1.`ticket_id` = B2.`ticket_id`) 
LEFT JOIN `ost_ticket_priority` B3 ON (B2.`priority` = B3.`priority_id`) 
LEFT JOIN `ost_user` B4 ON (A1.`user_id` = B4.`id`) 
LEFT JOIN `ost_staff` B5 ON (A1.`staff_id` = B5.`staff_id`) 
LEFT JOIN `ost_team` B6 ON (A1.`team_id` = B6.`team_id`) 
LEFT JOIN `ost_lock` B7 ON (A1.`lock_id` = B7.`lock_id`) 
WHERE
  A2.`state` = 'open' 
  AND (
    (A2.`state` = 'open' AND (
      A1.`staff_id` = 1 OR A5.`staff_id` = 1 OR A6.`object_type` = 'C' AND A8.`staff_id` = 1
    )) 
    OR A1.`dept_id` IN (1, 2)
    OR B0.`id` IN (1, 2)
    OR A6.`object_type` = 'C' 
    AND B1.`id` IN (1, 2)
  )
  AND (A1.`ticket_pid` IS NULL OR A1.`flags` & 8 != 0)
GROUP BY A1.`ticket_id` 
ORDER BY B3.`priority_urgency` ASC, A1.`lastupdate` DESC 
LIMIT 25 
in /www/osticket/include/class.orm.php:3483 
Stack trace: #0 /www/osticket/include/class.orm.php(3529): MySqlExecutor->execute() 
#1 /www/osticket/include/class.orm.php(2104): MySqlExecutor->getArray() 
#2 /www/osticket/include/class.orm.php(2054): HashArrayIterator->{closure}() 
#3 /www/osticket/include/class.orm.php(2033): CallbackSimpleIterator->next() 
#4 /www/osticket/include/class.orm.php(2042): CallbackSimpleIterator->rewind() 
#5 /www/osticket/include/class.orm.php(1713): CallbackSimpleIterator->valid() 
#6 /www/osticket/include/class.orm.php(1723): CachedResultSet->fillTo(9223372036854775807) 
#7 /www/osticket/include/class.orm.php(1739): CachedResultSet->asArray() 
#8 /www/osticket/include/staff/templates/queue-tickets.tmpl.php(258): CachedResultSet->getIterator() 
#9 /www/osticket/scp/tickets.php(569): require_once('/www/osticket/i...') 
#10 /www/osticket/scp/index.php(17): require('/www/osticket/s...') 
#11 {main} thrown in /www/osticket/include/class.orm.php on line 3483

KevinTheJedi

akbass

What happens when you run that manually in MySQL?

Cheers.

akbass

I just ran this SQL command manually in the db and it inserted data into ost_ticket__cdata fine

And OSTicket is still up.

You can see the two new columns I added in the UI that caused the initial issue (location and room)

KevinTheJedi

akbass

I'm talking about the query in the error message you provided. What happens when you run that query manually?

Cheers.

akbass

KevinTheJedi

the db_query was
INSERT INTO ost_ticket__cdata set subject='test ticket', ticket_id= 6 on duplicate key update subject='test ticket'
and that seemed to run just fine (there was no update of tickets in the UI though, but at least it didn't crash)
Or am I missing something? Thanks

KevinTheJedi

akbass

Uhhh…huh? Look above. The error includes a SELECT query; not an INSERT query.

Cheers.

akbass

Oh right.
I ran that whole select query and I got a nice join table with all the data requested in it.
No crash in the UI.

KevinTheJedi

akbass

Hmm, we need the real error and cause for that query to fail. The PHP-level error you posted isn’t descriptive enough; it just says the database couldn’t execute it. We need the MySQL-level error for this that says why it couldn’t execute it. Try checking to see if your MySQL instance has error logging enabled. If so check your database error logs to find the real error. If not then enable error logging, persist the changes, wait until the error happens again, then check the logs.

Cheers.