Closed pkikawa closed 2 years ago
I'm not seeing this in my local. You say this only happens on the add-binary step and not before?
What are the perms on the collection dir?
ls -l /var/www/media/ddr/ddr-densho-1000
or whatever dir it is.
total 1680
-rw-r--r-- 1 ddr ddr 1677940 Feb 13 11:56 changelog
-rw-r--r-- 1 ddr ddr 2404 May 6 2019 collection.json
-rw-r--r-- 1 ddr ddr 9917 Feb 13 11:56 control
-rw-r--r-- 1 ddr ddr 2747 May 6 2019 ead.xml
drwxr-xr-x 490 ddr ddr 20480 Feb 13 11:56 files
And the dir itself? ls -l /var/www/media/ddr/ | grep ddr-densho-1000
densho@DDREditor:/var/www/media/ddr$ ls -la
total 48
drwxr-xr-x 12 ddr ddr 4096 Oct 9 2020 .
drwxr-xr-x 6 root root 4096 Jan 16 2019 ..
drwxr-xr-x 4 ddr ddr 4096 Feb 13 12:12 ddr-densho-1000
test
I'm seeing a bunch of these lines in /var/log/ddr/ddrlocal-celery.log
:
PermissionError: [Errno 13] Permission denied: '/var/log/ddr/ddrlocal-celery.log'
Can you check the perms in the logs dir?
ls -l /var/log/
ls -l /var/log/ddr/
pkikawa:
densho@DDREditor:/var/log/ddr$ ls -l /var/log/ddr/
total 4680
drwxrwxr-x 11 ddr ddr 4096 Jul 22 2021 addfile
-rwxrwxr-x 1 ddr ddr 170177 Mar 15 12:19 celerybeat.log
-rwxrwxr-x 1 ddr ddr 106049 Mar 11 13:50 celeryd.log
-rwxrwxr-x 1 ddr ddr 300151 Jun 1 2020 celeryd.log.1
-rw-r--r-- 1 root root 41436 Mar 15 12:19 ddrlocal-celery.log
-rw-r--r-- 1 ddr ddr 125 Mar 15 12:29 ddrlocal.log
-rw-r--r-- 1 ddr ddr 127 Mar 15 12:29 ddrlocal.log.2022-03-11
-rwxrwxr-x 1 ddr ddr 203543 Feb 13 12:12 gitstatus.log
-rwxrwxr-x 1 ddr ddr 335750 Jun 15 2020 gitstatus.log.1
-rwxrwxr-x 1 ddr ddr 39817 Jun 6 2020 gitstatus.log.10.gz
-rwxrwxr-x 1 ddr ddr 39672 Jun 14 2020 gitstatus.log.2.gz
-rwxrwxr-x 1 ddr ddr 39840 Jun 14 2020 gitstatus.log.3.gz
-rwxrwxr-x 1 ddr ddr 39762 Jun 12 2020 gitstatus.log.4.gz
-rwxrwxr-x 1 ddr ddr 39891 Jun 11 2020 gitstatus.log.5.gz
-rwxrwxr-x 1 ddr ddr 39945 Jun 10 2020 gitstatus.log.6.gz
-rwxrwxr-x 1 ddr ddr 39816 Jun 10 2020 gitstatus.log.7.gz
-rwxrwxr-x 1 ddr ddr 39855 Jun 8 2020 gitstatus.log.8.gz
-rwxrwxr-x 1 ddr ddr 39800 Jun 7 2020 gitstatus.log.9.gz
-rw-r--r-- 1 ddr ddr 2054 Mar 11 13:45 local.log
-rw-r--r-- 1 ddr ddr 331664 Oct 8 2020 local.log.1
-rwxrwxr-x 1 ddr ddr 77208 Jul 1 2018 local.log.10.gz
-rw-r--r-- 1 ddr ddr 1161 Oct 12 16:32 local.log.2021-09-18
-rw-r--r-- 1 ddr ddr 3515 Oct 12 16:31 local.log.2021-10-12
-rw-r--r-- 1 ddr ddr 125 Oct 29 15:59 local.log.2021-10-15
-rw-r--r-- 1 ddr ddr 4616 Nov 2 15:49 local.log.2021-10-29
-rw-r--r-- 1 ddr ddr 158 Nov 2 15:50 local.log.2021-11-02
-rw-r--r-- 1 ddr ddr 125 Dec 7 10:33 local.log.2021-11-08
-rw-r--r-- 1 ddr ddr 4305 Dec 10 15:40 local.log.2021-12-07
-rw-r--r-- 1 ddr ddr 125 Dec 14 10:52 local.log.2021-12-10
-rw-r--r-- 1 ddr ddr 1667 Dec 31 16:54 local.log.2021-12-14
-rw-r--r-- 1 ddr ddr 316 Jan 28 08:55 local.log.2021-12-31
-rw-r--r-- 1 ddr ddr 125 Feb 1 13:56 local.log.2022-01-28
-rw-r--r-- 1 ddr ddr 125 Feb 13 11:54 local.log.2022-02-01
-rw-r--r-- 1 ddr ddr 125 Mar 4 15:10 local.log.2022-02-13
-rw-r--r-- 1 ddr ddr 316 Mar 11 13:00 local.log.2022-03-04
-rwxrwxr-x 1 ddr ddr 14355 Jul 23 2020 local.log.2.gz
-rwxrwxr-x 1 ddr ddr 1754142 Jul 12 2019 local.log.3.gz
-rwxrwxr-x 1 ddr ddr 80446 May 7 2019 local.log.4.gz
-rwxrwxr-x 1 ddr ddr 66791 Apr 23 2019 local.log.5.gz
-rwxrwxr-x 1 ddr ddr 78829 Apr 22 2019 local.log.6.gz
-rwxrwxr-x 1 ddr ddr 78771 Apr 21 2019 local.log.7.gz
-rwxrwxr-x 1 ddr ddr 199691 Apr 20 2019 local.log.8.gz
-rwxrwxr-x 1 ddr ddr 75719 Jul 2 2018 local.log.9.gz
-rw-r--r-- 2 ddr ddr 43 Feb 2 10:09 README
-rw-r--r-- 1 ddr ddr 75874 Mar 11 13:50 worker.log
-rw-r--r-- 1 ddr ddr 262385 Nov 9 16:07 worker.log.1
-rwxrwxr-x 1 ddr ddr 15722 Jul 28 2021 worker.log.2.gz
There's your problem: /var/log/ddr/ddrlocal-celery.log
is owned by root.root
. You can fix it by running sudo chown ddr.ddr /var/log/ddr/ddrlocal-celery.log
Note: pkikawa changed the permissions on Tuesday but GitHUb wasn't taking comments at the time so I couldn't post this.
creating a new object, editing an object, adding a binary results in a stuck
pending
notification and a hanging lock file in the collection dir. the operation completes successfully otherwise. manually removing the lock file works.this is on dana's local VM (5.3.1) running deb 11 after the version upgrade.
Clarification: This happens whenever a collection/entity/file is added or edited.