"Resources" give HTTP error 500

Omeka S
1

Hello,
This HTTP error 550 happened recently and we have this stack trace. I was wondering if anyone ran into this issue before?
Thanks,
Lu.

Omeka\Api\Exception\NotFoundException: Omeka\Entity\Item entity with criteria {“id”:“144296”} not found in /var/www/html/application/src/Api/Adapter/AbstractEntityAdapter.php:714
Stack trace:
#0 /var/www/html/application/src/Api/Adapter/AbstractEntityAdapter.php(432): Omeka\Api\Adapter\AbstractEntityAdapter->findEntity()
#1 /var/www/html/application/src/Api/Manager.php(230): Omeka\Api\Adapter\AbstractEntityAdapter->read()
#2 /var/www/html/application/src/Api/Manager.php(115): Omeka\Api\Manager->execute()
#3 /var/www/html/application/src/Mvc/Controller/Plugin/Api.php(136): Omeka\Api\Manager->read()
#4 /var/www/html/application/src/Controller/Site/ItemController.php(46): Omeka\Mvc\Controller\Plugin\Api->read()
#5 /var/www/html/vendor/laminas/laminas-mvc/src/Controller/AbstractActionController.php(71): Omeka\Controller\Site\ItemController->showAction()
#6 /var/www/html/vendor/laminas/laminas-eventmanager/src/EventManager.php(319): Laminas\Mvc\Controller\AbstractActionController->onDispatch()
#7 /var/www/html/vendor/laminas/laminas-eventmanager/src/EventManager.php(179): Laminas\EventManager\EventManager->triggerListeners()
#8 /var/www/html/vendor/laminas/laminas-mvc/src/Controller/AbstractController.php(97): Laminas\EventManager\EventManager->triggerEventUntil()
#9 /var/www/html/vendor/laminas/laminas-mvc/src/DispatchListener.php(132): Laminas\Mvc\Controller\AbstractController->dispatch()
#10 /var/www/html/vendor/laminas/laminas-eventmanager/src/EventManager.php(319): Laminas\Mvc\DispatchListener->onDispatch()
#11 /var/www/html/vendor/laminas/laminas-eventmanager/src/EventManager.php(179): Laminas\EventManager\EventManager->triggerListeners()
#12 /var/www/html/vendor/laminas/laminas-mvc/src/Application.php(325): Laminas\EventManager\EventManager->triggerEventUntil()
#13 /var/www/html/index.php(21): Laminas\Mvc\Application->run()
#14 {main}

2

You’re sure it was 550? I don’t know that we ever return a 550 code, but it could come from some other layer of your system, a proxy, something like that.

The stack trace you’re showing there is for trying to visit the public page for an item that doesn’t exist (or is private). Depending on how you’re looking through the logs and how you’re getting or reproducing the error, it’s not necessarily the case that this message has anything to do with your error.

3

Hello, sorry you’re right, the error message is 500.

4

What were you doing when you got the 500 error?

The message you showed doesn’t look to me like it would be related to a 500 error. A 500 might come from a PHP-level error also so you might check your server’s PHP logs.

5

John,
Here’s the PHP error log output for this issue

[02-Oct-2024 11:34:37 UTC] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1409024 bytes) in /var/www/html/application/view/common/item-set-selector.phtml on line 29
[02-Oct-2024 11:34:37 UTC] PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 1400832 bytes) in Unknown on line 0
6

Additionally, It looks like the edit page for any individual item was causing this issue as well;
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 3141632 bytes) in Unknown on line 0
Raising PHPs memory limit allowed the pages to load, but I’m curious as to why Omeka would be using so much memory; this started randomly on our end without any changes (to my knowledge as the Omeka Sysadmin for UR)

7

How many items, and maybe more importantly, item sets, do you have? There’s some interfaces that assume you’ll have a relatively limited number of item sets.