flat icon indicating copy to clipboard operation
flat copied to clipboard

Dubious ownership of annotations

Open savary opened this issue 11 months ago • 13 comments

Our FLAT server goes down from time to time and we are trying to establish the reasons for that. One such case happened yesterday evening. I looked into the logs of the docker (sudo docker logs -n 1000 flat). An annotator was working on FLAT, then she seems to have logged out and logged back in. Then this error occurred:

fatal: detected dubious ownership in repository at '/data/annotations' To add an exception for this directory, call: git config --global --add safe.directory /data/annotations

This is likely due to our versioning of the annotations via an external git repository. It seems that the error is not that problematic as discussed here.

But I checked the access permissions in our annotation directory and they do not look very homogeneous:

parseme@parseme:~/annotations$ cd .. parseme@parseme:~$ cd annotations/ parseme@parseme:~/annotations$ ls -lia total 1752 5505187 drwxrwsr-x 351 parseme parseme 20480 nov. 13 18:49 . 5505059 drwxr-x--- 9 parseme parseme 4096 août 7 11:43 .. 5637212 drwxr-xr-x 2 parseme parseme 4096 janv. 10 2024 Abbas 5636773 drwxr-xr-x 2 parseme parseme 4096 janv. 10 2024 abdelati.hawwari 5637259 drwxr-xr-x 3 parseme parseme 4096 janv. 10 2024 abigail.walsh 5637425 drwxr-xr-x 2 parseme parseme 4096 janv. 10 2024 adela.tocaru 5767548 drwxr-sr-x 2 root parseme 4096 juil. 10 2024 adelina.cerpja 5767563 drwxr-sr-x 2 root parseme 4096 juil. 10 2024 adina.duca 5505488 drwxr-xr-x 4 parseme parseme 4096 janv. 10 2024 agata.savary 5637082 drwxr-xr-x 16 parseme parseme 4096 oct. 8 10:26 agata.savary.annotator 5506634 drwxr-xr-x 2 parseme parseme 4096 janv. 10 2024 agata.savary.test 5767594 drwxr-sr-x 2 root parseme 4096 juil. 5 2024 agata.savary.unidive 5636803 drwxr-xr-x 2 parseme parseme 4096 janv. 10 2024 aggelfoto123 5767576 drwxr-sr-x 2 root parseme 4096 juil. 17 10:38 agute.klints 5636807 drwxr-xr-x 2 parseme parseme 4096 janv. 10 2024 ainara.estarrona 5637002 drwxr-xr-x 2 parseme parseme 4096 janv. 10 2024 aixiu.an.zh ... parseme@parseme:~/annotations$ ls -l ./yalda.yarandi/final total 22000 -rw-r--r-- 1 root root 2373753 août 12 16:01 dev.udpipe-2.10-xpos-to-deprel.folia.xml -rw-r--r-- 1 root root 2001046 août 12 16:01 test.udpipe-2.10-xpos-to-deprel.folia.xml -rw-r--r-- 1 root root 12274118 août 12 16:01 train.udpipe-2.10-xpos-to-deprel.folia.xml -rw-r--r-- 1 root root 1073626 août 12 16:01 tree_bank_without_VMWE.folia.xml -rw-r--r-- 1 root root 4792400 août 12 16:01 tree_bank_with_VMWE.folia.xml parseme@parseme:~/annotations$ ls -l ./jaka.cibej/ total 328 -rw-r--r-- 1 parseme parseme 333884 janv. 10 2024 parseme_sl_ssj500k_13412_13511_noIDs.parsemetsv.folia.xml

Some directories have root as owner, another have parseme. In the former case the permissions are drwxr-sr-x, in the latter they are drwxr-xr-x. Similarly, some files have root as owner, some others have parseme.

Given that users are always added via DJANGO interface, what causes the difference? And are the correct owners and permissions? Could this be a reason for the unstability of the server?

savary avatar Jan 14 '25 14:01 savary