Still getting the transfer error creating the temp directories in /var/archivematica/sharedDirectory

483 views
Skip to first unread message

davihart

unread,
Nov 13, 2015, 2:38:09 PM11/13/15
to archivematica
In my case the permissions on the temp directories are 775 but I still get the error copying /var/archivematica/sharedDirectory/TemDirs... to start of transfer.

the storage service error log shows:
OSError: [Errno 13] Permission denied: '/mnt/currently_processing/tmp'
INFO      2015-10-28 10:52:23  locations.models.space:space:_move_rsync:375:  Rsyncing from /mnt/disc_work/transfers/baxxxxxn_1893-10-01/. to /var/archivematica/storage_service/mnt/cur
rently_processing/tmp/tmp1hCZuL/battalion_1893/.
INFO      2015-10-28 10:52:23  locations.models.space:space:_move_rsync:383:  rsync command: ['rsync', '-t', '-O', '--protect-args', '-vv', '--chmod=ugo+rw', '-r', '/mnt/disc_work/trans
fers/bxxxon_1893-10-01/.', '/var/archivematica/storage_service/mnt/currently_processing/tmp/tmp1hCZuL/bxxxon_1893/.']

the permissions on the destinations dirs are:
root@archivematica1:/var/archivematica/storage_service/mnt/currently_processing/tmp# ls -lt
total 32
drwxrwxr-x 2 archivematica archivematica 4096 Nov 13 12:36 tmpRRr3RU
drwxrwxr-x 2 archivematica archivematica 4096 Nov 13 09:59 tmpIYh_oX
drwxrwxr-x 2 archivematica archivematica 4096 Nov 13 09:55 tmppvKd7S

it appears that the storage service dashboard is being run by a different user than archivematica, perhaps archivematicadashboard so we tried adding archivematicadashboard to archivematica
group to pick up the write permissions but that didnt work.  the storage service dashboard is accessed on port 8000 which is being listened to by nginx so I checked the nginx.conf file and
it is using user www-data but adding that user to the group permission did not work either.

Can anyone help?
thanks
David Hart

davihart

unread,
Nov 23, 2015, 2:37:24 PM11/23/15
to archivematica
Apparently the sharedDirectory is not writable by others.  The rsyncs are run as archivematica, but it wasnt the rsyncs that were failing.  I added www-data to the archivematica group and made the directory writable by archivematica and the transfers worked.  Thanks to anyone that checked this post.

David Hart | Systems Administrator

Digital Initiatives | Texas A&M University Libraries

Sarah Romkey

unread,
Nov 25, 2015, 1:03:40 PM11/25/15
to archiv...@googlegroups.com
Hi David,

Thanks so much for posting your solution to the list!

Cheers,

Sarah

Sarah Romkey, MAS,MLIS
Archivematica Program Manager
Artefactual Systems
604-527-2056
@archivematica / @accesstomemory



--
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 post to this group, send email to archiv...@googlegroups.com.
Visit this group at http://groups.google.com/group/archivematica.
For more options, visit https://groups.google.com/d/optout.

Tatiana Canelhas

unread,
Nov 21, 2017, 2:18:26 PM11/21/17
to archivematica
I am facing the same issues. Trying to transfer a small image as test. Nothing happens after I select Start Transfer.

Some of my log errors:

/var/log/archivematica/dashboard/dashboard.debug.log

ERROR     2017-11-21 19:01:54  archivematica.dashboard:views:start_transfer:265:  Error copying /var/archivematica/sharedDirectory/tmp/tmpD_DmTc/teste to start of transfer
Traceback (most recent call last):
 
File "/usr/share/archivematica/dashboard/components/filesystem_ajax/views.py", line 263, in start_transfer
    transfer_metadata_set_row_uuid
=row_id)
 
File "/usr/share/archivematica/dashboard/components/filesystem_ajax/views.py", line 319, in copy_to_start_transfer
   
raise Exception(error)
Exception: Filepath /var/archivematica/sharedDirectory/tmp/tmpD_DmTc/teste does not exist.


/var/log/archivematica/MCPClient/MCPClient.log

ERROR     2017-11-21 18:59:36  archivematica.mcp.client:archivematicaClient:startThread:218:  Gearman server is unavailable: ('Found no valid connections in list: [<GearmanConnection localhost:4730 connected=False>]',). Retrying in 1 seconds.
ERROR    
2017-11-21 18:59:36  archivematica.mcp.client:archivematicaClient:startThread:218:  Gearman server is unavailable: ('Found no valid connections in list: [<GearmanConnection localhost:4730 connected=False>]',). Retrying in 1 seconds.


/var/log/archivematica/storage-service/storage_service.log

INFO      2017-11-17 11:39:52  locations.models.space:space:browse:229:  path: /dados
INFO      2017-11-17 11:39:55  locations.models.space:space:browse:229:  path: /
dados/home
INFO      
2017-11-17 11:39:56  locations.models.space:space:browse:229:  path: /dados/home/tcdf_teste
INFO      
2017-11-21 11:01:25  locations.models.space:space:browse:229:  path: /dados/home
INFO      
2017-11-21 11:01:53  locations.models.space:space:move_rsync:421:  Moving from /dados/home/tcdf_teste/. to /var/archivematica/storage_service/dados/var/archivematica/sharedDirectory/tmp/tmpD_DmTc/teste/.
INFO      
2017-11-21 11:01:53  locations.models.space:space:move_rsync:449:  rsync command: ['rsync', '-t', '-O', '--protect-args', '-vv', '--chmod=ugo+rw', '-r', '/dados/home/tcdf_teste/.', '/var/archivematica/storage_service/dados/var/archivematica/sharedDirectory/tmp/tmpD_DmTc/teste/.']
WARNING  
2017-11-21 11:01:53  locations.models.space:space:create_local_directory:479:  Could not create storage directory: [Errno 13] Permission denied: '/dados/var'


/var/log/nginx/error.log

2017/11/21 17:01:54 [error] 19933#0: *40 upstream prematurely closed connection while reading response header from upstream, client: 10.9.16.44, server: , request: "POST /api/v2/location/a136a4e4-a93f-41b5-9479-564a8109aa99/ HTTP/1.1", upstream: "http://127.0.0.1:8001/api/v2/location/a136a4e4-a93f-41b5-9479-564a8109aa99/", host: "10.9.16.44:8000"


any idea?

It´s a fresh install from latest version.

Thanks

davi...@library.tamu.edu

unread,
Jul 25, 2018, 3:49:45 PM7/25/18
to archivematica
The code is not creating the temporary folders.  I don't remember how we resolved this except that I manually ran the rsync commands and checked the error output.  also check the directory created by the previous command
Reply all
Reply to author
Forward
0 new messages