Processing configuration editing issue

32 views
Skip to first unread message

sergio...@gmail.com

unread,
Jul 2, 2025, 5:29:18 AMJul 2
to archivematica
Dear all, I have migrated Archivematica from version 1.10.2 to 1.17.1 and installed the last release of the storage service. I did the backup of mysql, elastic search databases and configured archivematica and the storage server with the previous configuration of the old installation. The problem is the Administration menu"Processing configuration" doesn't edit the default/automated configuration, while it works for downlaoding and apparently for the reset button. In the shared path,  I have checked the existing of the processing XML files, but it is not clear their content (I have read the documentation, but for me it is not clear).

For editing I have this timeout error. 

ERROR     2025-07-02 07:35:54  archivematica.dashboard:views_processing:_report_error:53:  Unable to load processing configuration page. Deadline exceeded: 30.0
Traceback (most recent call last):
  File "/usr/share/archivematica/dashboard/components/administration/views_processing.py", line 62, in edit
    form = ProcessingConfigurationForm(request.POST or None, user=request.user)
  File "/usr/share/archivematica/dashboard/components/administration/forms.py", line 306, in __init__
    self.load_processing_config_fields(user)
  File "/usr/share/archivematica/dashboard/components/administration/forms.py", line 312, in load_processing_config_fields
    self.processing_fields = client.get_processing_config_fields()
  File "/usr/share/archivematica/dashboard/contrib/mcp/client.py", line 207, in get_processing_config_fields
    return self._rpc_sync_call("getProcessingConfigFields", data)
  File "/usr/share/archivematica/dashboard/contrib/mcp/client.py", line 123, in _rpc_sync_call
    raise TimeoutError(timeout)
contrib.mcp.client.TimeoutError: Deadline exceeded: 30.0


I am wondering what are the Archivematica check for the editing. Can you help me, please?
Regards
Sergio

Douglas Cerna

unread,
Jul 2, 2025, 1:23:07 PMJul 2
to archiv...@googlegroups.com
Hello,

The TimeoutError means the archivematica-dashboard service could not communicate with the archivematica-mcp-server service.

The MCPServer logs might have additional information and you can check with:

sudo cat /var/log/archivematica/MCPServer/MCPServer.debug.log
sudo journalctl -u archivematica-mcp-server

If for some reason the MCPServer was down when you tried to edit the configurations you could try restarting both services with:

sudo service archivematica-mcp-server restart
sudo service archivematica-dashboard restart

and try editing the configurations again.

As a last option you could try recreating the processing configuration files by:

1. Renaming the /var/archivematica/sharedDirectory/sharedMicroServiceTasksConfigs/processingMCPConfigs directory that contains them, for example:

sudo mv /var/archivematica/sharedDirectory/sharedMicroServiceTasksConfigs/processingMCPConfigs /var/archivematica/sharedDirectory/sharedMicroServiceTasksConfigs/processingMCPConfigs-broken

2. Restarting the MCPServer service which by default creates that directory and those XML files if they're not there:

sudo service archivematica-mcp-server restart

Hope this helps.



--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/archivematica/61157607-2e11-4775-a929-3f8dfc554bcbn%40googlegroups.com.


--
Douglas Cerna (he/him),
Software Developer, Artefactual Systems Inc.
http://www.artefactual.com
Message has been deleted

sergio...@gmail.com

unread,
Jul 3, 2025, 3:45:58 PMJul 3
to archivematica
Hello, your reply has been very very useful. The problem is the mcp server was not able to connect to the mysql database because the password in /etc/sysconfig/archivematica-mcp-server was wrong. I don't know why I was not able to understand this service status. :-(.
Thank you again and have you great days. All the best

Sergio

Reply all
Reply to author
Forward
0 new messages