|
|
|
@ -1 +1,34 @@ |
|
|
|
Welcome to the Wiki. |
|
|
|
# Full Memory issue |
|
|
|
|
|
|
|
If your Nextcloud web app show you the following message, it can be an full memory issue. |
|
|
|
``` |
|
|
|
Internal Server Error |
|
|
|
The server encountered an internal error and was unable to complete your request. |
|
|
|
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. |
|
|
|
More details can be found in the server log. |
|
|
|
``` |
|
|
|
|
|
|
|
To confirm it, look at the Nextcloud logs: |
|
|
|
`compose logs nextcloud` |
|
|
|
|
|
|
|
You should be able to see logs with errors like: |
|
|
|
`Sabre/DAV/Exception/InsufficientStorage: Inssufficient space in [directory path], xxxxxx required, YYYYYYY availaible` |
|
|
|
|
|
|
|
In that case, you must find where the memory issue is : |
|
|
|
* it is global on the nextcloud database? |
|
|
|
* is it due to a specific user? |
|
|
|
|
|
|
|
Thanks to the command `du -sch *` find the biggest repositories, and identify the issue. |
|
|
|
|
|
|
|
|
|
|
|
### Trashbin issue: |
|
|
|
Nextcloud has a specific way to manage the deletion of files and repositories, explained here: https://docs.nextcloud.com/server/stable/user_manual/files/deleted_file_management.html?highlight=trash |
|
|
|
|
|
|
|
If the memory issue is due to the trashbin folder full of old deleted file, you can start by deleteing them to free the memory and make the application available again for the users. |
|
|
|
|
|
|
|
You can also modify the trashbin configuration, in the `config.php` file, with the parameter `trashbin_retention_obligation'. |
|
|
|
|
|
|
|
Example: |
|
|
|
`'trashbin_retention_obligation' => 1,3` |
|
|
|
Here the deleted files are kept at least 1 day, and up to 3 days, if the quota of deleted files is not exceeded (if exceeded, they will be deleted sooner). |
|
|
|
|
