Tasks not being updated in DB as completed

[Aaron Elkiss]

Hi,

I've got a transfer that's stuck in the 'Assign file UUIDs to objects' job; the dashboard thinks it's still executing commands, but as far as I can tell what's happened is that all the tasks have run but some of them have failed to update the database - in particular looking at the MCPServer.debug.log for the tasks it hasn't marked as complete in the database, it logs:

MCPServer.debug.log:DEBUG     2017-02-13 17:23:01  archivematica.mcp.server:taskStandard:check_request_status:95:  Task 0ef3cf37-5004-4495-a2fd-a9591579d7a6 finished! Result COMPLETE - {'stdOut': '', 'exitCode': 0, 'stdError': ''}

but for a task that is marked as completed, it logs:

MCPServer.debug.log:DEBUG     2017-02-13 17:29:48  archivematica.mcp.server:taskStandard:check_request_status:95:  Task 504edc69-27c8-4a00-af7f-576a5f3fc3dd finished! Result COMPLETE - {'stdOut': '', 'exitCode': 0, 'stdError': ''}
MCPServer.debug.log:DEBUG     2017-02-13 17:29:48  archivematica.mcp.server:taskStandard:performTask:90:  Finished performing task 504edc69-27c8-4a00-af7f-576a5f3fc3dd

Has anyone seen this? Any suggestions for recovering from this state? Any ideas why it might happen?

Thanks!

Aaron Elkiss
Library IT Architecture & Engineering
University of Michigan

[Qing Zou]

Hi Aaron,

Have you figured out the issue? I ran into a similar issue. I tested a couple of transfers they all got "Index AIP failed". And In the MCPServer.debug.log, I found the following:

DEBUG     2017-02-24 17:24:50  archivematica.mcp.server:taskStandard:check_request_status:95: Task 5d18b366-82fe-4de1-8f3b-5b32321c6805 finished! Result COMPLETE - {'stdOut': "SIP UUID: ...
ivematica/sharedDirectory/www/AIPsStore/e7b5/b235/600d/442b/b2b9/047e/b96b/0d71/testoo2-e7b5b235-600d-442b-b2b9-047eb96b0d71.7z',  u'related_packages': [], u'size': 11246, u'resource_uri':    u'/api/v2/file/e7b5b235-600d-442b-b2b9-047eb96b0d71/'}] \nIndexing AIP info\nRemoved FITS output from METS. \nIndexing AIP files\n", 'exitCode': 1,   'stdError':  'No handlers could be found for logger "elasticsearch.trace"\nElasticsearch not found, normally installed at /etc/elasticsearch/elasticsearch.yml\nError indexing AIP files\n'}

Could anyone help? Thanks.

By the way, my instance is running archivematica 1.5.1 on centos 7. The Elasticsearch (1.7.5) is in a different container.

Best,

Jason Zou

[Tatiana Canelhas]

Hi Aaron and Qing Zou,

Have you figured out this issue?

I am trying to figure out why in my LOCATIONS tab (Storage Service), the usade of my TransferBacklog does not mach the actual size. 

So, i ran into this problem on my task table:

•  UUID: 88..2
  
•  fileName: co..77
  
•  exec: postStoreAIPHook_v1.0
  
•  arguments: "b3..77"
  
•  stdOut: Checking if transfer 4e..9b is fully stored...
  
•  Transfer 4e..9b fully stored, sending delete request to storage service, deleting from transfer backlog - SIP b3..77 not associated with an ArchivesSpace component

•  stdError: No handlers could be found for logger "elasticsearch.trace"
  

•  jobUUID: 59..0d
  

Any ideias???

I know it is deleting the backlog, but somehow the size does not upgrade.