Screenshot copy error about website HOT 9 CLOSED

Hello,

Hmm, do you only get this when pasting in the image? If you save the image, open the image manager (image icon) then upload through there does it work?

from website.

So after testing, I can't save the image in the image manager either and the error message is related to the size :

But as you can see, it's barely heavy : 26 Ko

Do you have a suggestion ?

Cheers,

Julien

from website.

Hi Dan,

have you had the occasion to look into this issue ?

Thank you again.

Julien

from website.

Hi @onlinejul,
Have you checked the permissions of the storage folder and everything within?

from website.

Hi Dan,

on the server, according to the doc, il checked the following directories :

and

Just so you have a better understanding of the issue :

• Sometimes, the copy/paste works, it has worked on some screenshots,
• When I changed the settings in php.ini to 10M, it seems to have worked for a day.

Do you see anything wrong with the acls ?

Thank you.

Julien

from website.

Hi Dan,

I made some additionnal tests, when the problem occurs, it seems that restarting the apache2 service resolves the issue.

I don't exactly know what happens to apache and when, but at some point, the service looks like it is in a bad state :

Do you have any idea on how to long term solve this ? I will research this error meanwhile.

Sorry for the delay.

Julien

from website.

Hi @onlinejul,

FYI, I don't track issues in this website repo often so, if you want quicker potential support from myself or others I'd recommend opening an issue on https://github.com/BookStackApp/BookStack/issues instead, referencing this one.

Seems like an odd issue. What kind of machine are you running BookStack on? Just wondering if this could be due to restrained available memory on the system.

from website.

Hi Dan,

sorry for the long delay. So the issue has nothing to do with Bookstack, it happened because we had a routine tested on some servers that would remove the files of the /tmp folder each night. Stopping this cron on this server seemed to have stopped the error from happening.

Sorry for the bother.

Cheers,

Julien

from website.

@onlinejul No worries, glad you figured it out!

from website.