Bug 16973 - Cannot upload cover images under plack
Summary: Cannot upload cover images under plack
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: 3.22
Hardware: All All
: P5 - low major
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-25 15:27 UTC by Tomás Cohen Arazi (tcohen)
Modified: 2019-06-27 09:24 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomás Cohen Arazi (tcohen) 2016-07-25 15:27:07 UTC 
To reproduce:

- Have a clean 3.22 packages install
- Create an instance, with plack enabled:
  $ koha-create --create-db test
- Go through the webinstaller
  $ koha-plack --enable test
  $ koha-plack --start  test
- Have a record
- Try attaching a cover image to it.
=> FAIL: "Denied" error message shows
Comment 1 Marcel de Rooy 2016-07-26 12:58:46 UTC 
Tested with 3.22.x commit 978f8aedf3dddb26cbbc44455c239ab10d3f7dd2 and just a few custom patches on top of that (not related to Upload). Yes it is a clean package dev install :)
But cannot yet reproduce your problem. I could upload several files one after another.

Could you check the temporary upload folder in /tmp: owner, permissions?
For this test instance called upgrade, I have:
drwxr-xr-x 2 upgrade-koha upgrade-koha  4096 Jul 26 14:55 koha_upgrade_upload

What happens if you remove the folder and upload another file or two?
Comment 2 Marcel de Rooy 2016-07-26 13:00:24 UTC 
Forgot to say: Yes, it is with plack and memcache.
Comment 3 Marcel de Rooy 2016-07-26 13:03:19 UTC 
And with: ProxyPass "/cgi-bin/koha/tools/upload-cover-image.pl" "!"

I am wondering: It seems like koha-plack does not restart apache. Is that the source of the problem?
Is your problem solved with a restart of apache ??
Comment 4 Tomás Cohen Arazi (tcohen) 2016-07-26 17:07:15 UTC 
It might be a local problem. It vanished now and couldn't reproduce on kohadevbox yet. Will re-open if I manage to.