Couple of days ago upgraded 3.22.3 to 3.24.0 (GPL version) following instructions in http://matrix.squiz.net/resources/upgrading/upgrade-3.22-to-3.24. All seemed to go cleanly, no error messages. However, cannot now upload new content into locations where the Search Manager operates:
[php] Fatal error: Uncaught exception 'Exception' with message 'Unable to add indexable content due to database error: SQLSTATE[25P02]:
In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block'
in /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc:935
Stack trace: #0 /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc(418): Search_Manager->addIndexableContent('25370', Array)
#1 /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc(226): Search_Manager->reindexAttributes(Object(Image), Array)
#2 /chester1/Local/Ix86/Linux/msm/mysource_matrix/core/include/event_manager.inc(304): Search_Manager->onAttributeChange(Object(Image), Array)
#3 /chester1/Local/Ix86/Linux/msm/mysource_matrix/core/include/asset.inc(3143): Event_Manager->broadcastEvent(Object(Image), 'attributeChange', Array)
#4 /chester1/Local/Ix86/Linux/msm/mysource_matrix/core/ass in /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc on line 935[/php]
We use Search Manager only on a few nodes, and mostly what we're indexing are the text and metadata associated with Image assets. With Search Manager off, the new Images can be added successfully. We did disable Search Manager before doing the upgrade. Looks like all the ALTER TABLE statements ran without error. We're using Postgres and don't implement rollback.
Any thoughts?
Thanks
Brian
[quote]
Couple of days ago upgraded 3.22.3 to 3.24.0 (GPL version) following instructions in http://matrix.squiz.net/resources/upgrading/upgrade-3.22-to-3.24. All seemed to go cleanly, no error messages. However, cannot now upload new content into locations where the Search Manager operates:
[php] Fatal error: Uncaught exception ‘Exception’ with message ‘Unable to add indexable content due to database error: SQLSTATE[25P02]:
In failed sql transaction: 7 ERROR: current transaction is aborted, commands ignored until end of transaction block’
in /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc:935
Stack trace: #0 /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc(418): Search_Manager->addIndexableContent(‘25370’, Array)
#1 /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc(226): Search_Manager->reindexAttributes(Object(Image), Array)
#2 /chester1/Local/Ix86/Linux/msm/mysource_matrix/core/include/event_manager.inc(304): Search_Manager->onAttributeChange(Object(Image), Array)
#3 /chester1/Local/Ix86/Linux/msm/mysource_matrix/core/include/asset.inc(3143): Event_Manager->broadcastEvent(Object(Image), ‘attributeChange’, Array)
#4 /chester1/Local/Ix86/Linux/msm/mysource_matrix/core/ass in /chester1/Local/Ix86/Linux/msm/mysource_matrix/packages/search/search_manager/search_manager.inc on line 935[/php]
[/quote]
We haven’t seen this particular issue, however there is a current bug which is being resolved for the 3.24.1 release which caused the PHP memory limit to be exceeded when creating an asset in very large systems when Search Manager was enabled (Bug 3898). This would be the closest match, however there doesn’t seem to be a memory issue here.
Please lodge this as a new bug report with details of the action performed at the time and we will see if this can be replicated here.