Ошибка удаления файла nextcloud
Observing a backup running recently, I noticed a substantial number of files being backed up from the Nextcloud trash directory. On inspecting this, it became apparent not a single file had been permanently deleted from my installation since setting it up over a year ago!
Comments
Comments are now linked to Discourse. Disqus has been removed due to introducing mandatory advertisements. If you'd like to comment, please hit the blue comment button to be taken to the relevant Bayton Discuss topic where you can log in using Twitter, Facebook, Google or Github.
Disqus comments will re-appear (read-only) here soon.
Hi,
I know this is an old post but I am trying to delete files from NC V. 14.0.6. Using your examples: D – delete after a number of days, but earlier if space is required D1, D2 on our Test box. Placed in config.php. Did not delete the files. I thought I would ask you since I have followed a lot of your guides with great outcomes.
Is there another step? Do I need to create a Cron job? In a way I guess I will be pretty lucky if you even notice this post! Worth a try.
TA… g.
So I believe the functionality around this is a little questionable. Leave it with me to check and I’ll get back to you!
Thanks. I appreciate your help.
Oh Also have Background Jobs set to AJAX
An update. After reading some info on:
https://docs.nextcloud.com/server/14/admin_manual/configuration_server/background_jobs_configuration.html
I switched AJAX to Cron. I received an error in log:
Exception: The requested uri(http:/www.google.com/nextcloud) cannot be processed by the script ‘/nextcloud/index.php’)
/var/www/html/nextcloud/lib/private/AppFramework/Http/Request.php - line 768:
OC\AppFramework\Http\Request->getRawPathInfo()
/var/www/html/nextcloud/lib/base.php - line 772:
OC\AppFramework\Http\Request->getPathInfo()
/var/www/html/nextcloud/lib/base.php - line 1068:
OC::init()
/var/www/html/nextcloud/index.php - line 40:
require_once("/var/www/ht … p")
Even though I have this error which I am researching. Older files “were deleted”.
I only have one I put in yesterday and if all goes it should be gone tomorrow.
So I am thinking I need to change a configuration in index.php?
Looking at now. Maybe find fix?
So your automatic removal post worked! Now just clean up on this issue.
Back with update.
Note to others. When installing NC, which maybe I would have done if I read more is change from AJAX to Cron for Background Jobs. Since I am new to Linux and Nextcloud I throw this there out as learning curve. Makes me feel better.
This did not work with my current settings when I did the force automatic removal. And upon changing received some errors.
After a long couple of days I worked it out and this auto removal worked.
Be sure to specify your path to cron.php… example. /var/www/html/nextcloud/cron.php
Files in Deleted Files were removed as specified.
This created a new error in logging.
OC\User\NoUserException: 36B664A4-338F-499B-B9D7-2D10A9BE1CEF is not a valid user anymore.
To check:
sudo -u www-data php occ ldap:check-user 36B664A4-338F-499B-B9D7-2D10A9BE1CEF
The user does not exists on LDAP anymore.
Clean up the user’s remnants by: ./occ user:delete “36B664A4-338F-499B-B9D7-2D10A9BE1CEF”
To Remove:
sudo -u www-data php ./occ user:delete “36B664A4-338F-499B-B9D7-2D10A9BE1CEF”
The specified user was deleted
There is a lot of resources out there but being new maybe I should have researched more for initial NextCloud best practices.
Next stop. Throw more files in deleted and make double sure it works. Then on to production server!
This may not have anything to do with the change to config.php but it happened and if it happens to someone else this may help.
Big Thanks to all the people who post out there. Appreciate it.
Updated from an older Nextcloud/ownCloud or fresh install:
Updated from NC 11 to NC12 on release date.
Where did you install Nextcloud from:
Updater Module in NC
Signing status:
Signing status No errors have been found.
List of activated apps:
App list Enabled: - activity: 2.5.2 - bruteforcesettings: 1.0.2 - comments: 1.2.0 - dav: 1.3.0 - federatedfilesharing: 1.2.0 - federation: 1.2.0 - files: 1.7.2 - files_markdown: 1.0.1 - files_pdfviewer: 1.1.1 - files_sharing: 1.4.0 - files_texteditor: 2.4.1 - files_trashbin: 1.2.0 - files_versions: 1.5.0 - files_videoplayer: 1.1.0 - firstrunwizard: 2.1 - gallery: 17.0.0 - logreader: 2.0.0 - lookup_server_connector: 1.0.0 - nextcloud_announcements: 1.1 - notifications: 2.0.0 - oauth2: 1.0.5 - password_policy: 1.2.2 - provisioning_api: 1.2.0 - serverinfo: 1.2.0 - sharebymail: 1.2.0 - survey_client: 1.0.0 - systemtags: 1.2.0 - theming: 1.3.0 - twofactor_backupcodes: 1.1.1 - updatenotification: 1.2.0 - user_ldap: 1.2.1 - workflowengine: 1.2.0 Disabled: - admin_audit - encryption - files_external - user_external
Nextcloud configuration:
Are you using external storage, if yes which one: local storage on filesystem (outside nextcloud folder)
Are you using encryption: no
Are you using an external user-backend, if yes which one: LDAP
LDAP configuration (delete this part if not used)
LDAP config +-------------------------------+------------------------------------------------------------+ | Configuration | s01 | +-------------------------------+------------------------------------------------------------+ | hasMemberOfFilterSupport | | | hasPagedResultSupport | | | homeFolderNamingRule | | | lastJpegPhotoLookup | 0 | | ldapAgentName | cn=nextcloud,ou=services,dc=ageg,dc=ca | | ldapAgentPassword | *** | | ldapAttributesForGroupSearch | | | ldapAttributesForUserSearch | | | ldapBackupHost | | | ldapBackupPort | | | ldapBase | dc=ageg,dc=ca | | ldapBaseGroups | dc=ageg,dc=ca | | ldapBaseUsers | dc=ageg,dc=ca | | ldapCacheTTL | 600 | | ldapConfigurationActive | 1 | | ldapDefaultPPolicyDN | | | ldapDynamicGroupMemberURL | | | ldapEmailAttribute | mail | | ldapExperiencedAdmin | 0 | | ldapExpertUUIDGroupAttr | | | ldapExpertUUIDUserAttr | | | ldapExpertUsernameAttr | | | ldapGidNumber | gidNumber | | ldapGroupDisplayName | cn | | ldapGroupFilter | | | ldapGroupFilterGroups | | | ldapGroupFilterMode | 0 | | ldapGroupFilterObjectclass | | | ldapGroupMemberAssocAttr | uniqueMember | | ldapHost | ldapi:/// | | ldapIgnoreNamingRules | | | ldapLoginFilter | (&(|(objectclass=inetOrgPerson))(|(uid=%uid)(|(cn=%uid)))) | | ldapLoginFilterAttributes | cn | | ldapLoginFilterEmail | 0 | | ldapLoginFilterMode | 0 | | ldapLoginFilterUsername | 1 | | ldapNestedGroups | 0 | | ldapOverrideMainServer | | | ldapPagingSize | 500 | | ldapPort | 389 | | ldapQuotaAttribute | | | ldapQuotaDefault | | | ldapTLS | 0 | | ldapUserDisplayName | displayname | | ldapUserDisplayName2 | | | ldapUserFilter | (|(objectclass=inetOrgPerson)) | | ldapUserFilterGroups | | | ldapUserFilterMode | 0 | | ldapUserFilterObjectclass | inetOrgPerson | | ldapUuidGroupAttribute | auto | | ldapUuidUserAttribute | auto | | turnOffCertCheck | 0 | | turnOnPasswordChange | 0 | | useMemberOfToDetectMembership | 1 | +-------------------------------+------------------------------------------------------------+
Jason Bayton
This comment has been minimized.
DominiqueFuchs commented Apr 23, 2020
Thanks @skjnldsv for providing the log snippets ands answering the questions above! That helps a lot trying to reproduce this. Based on the impact of this issue (extreme) and the comparatively low number of reports (4 people in this thread) there seems to be a pretty specific but exotic condition going on.
luspi commented Mar 7, 2020
Just wanted to say that this happened to me today, I caught the desktop client in the middle of deleting all files on the server INCLUDING files that I do not have locally but only on the server. The activity log shows no errors but lists a selection of files that were supposedly deleted . Thankfully I'm backing my server up regularly.
Desktop client: 2.6.4
Nextcloud: 18.0.1
Server OS: Ubuntu 18.04
Server configuration
Nextcloud version: 16.0.4.1
The text was updated successfully, but these errors were encountered:
github-actions bot commented Sep 15, 2021
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
Client configuration
Client version: 2.5.3
Operating system: Fedora 30
OS language: English
Qt version used by client package (Linux only, see also Settings dialog): 5.12.4
Client package (From Nextcloud or distro) (Linux only): nextcloud-client-2.5.3-1.fc30
Bun-Bun commented Apr 23, 2020
@skjnldsv Could you elaborate on the thing regarding the trashbin please? Not sure if I got your description right there. Do you mean the unintentionally/suddenly deleted files are synced back again after you put the local copies in the trash bin on your client side?
Same scenario on my case. The bad client sent delete requests to the server, which moved everything to the NC trashbin, and then the bad client immediately started reuploading all the files back to the server. Which in my case caused it to fill up and stop working. Locally to the bad client the files were unchanged.
Bun-Bun commented Apr 16, 2020
My solution was to install Nextcloud-2.3.3.1 client and configure it to not check for updates.
That is the last version of the client before they started screwing everything up with it.
Bun-Bun commented Apr 23, 2020
As my post earlier said
Server OS: Centos 7
Desktop client: Windows 2.6.2 (Win 10 Pro 1803)
Nextcloud: 14
The cause
By default, Nextcloud is set to hold on to deleted items for 30 days. After this, files are only deleted when storage starts running low. This means for those with terrabytes of unused storage, deleted items may actually never disappear!
rbu commented Oct 16, 2019
This has not happened in the 3 weeks since I downgraded from 2.5.3-1.fc30 to 2.5.2-1.fc30. I guess I'll just stay on that version for the foreseeable future 🤷♂️
github-actions bot commented Aug 31, 2021
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!
skjnldsv commented Apr 23, 2020 •
Just after moving all my files to the trashbin, the client started syncing again all my files to the server. Hope that helps!
@misch7 @DominiqueFuchs, If I can be any more help, I have tons of other logs 🙏
Bun-Bun commented Mar 15, 2020 •
This also happened to me today. During the night while I was asleep all the files on my server were deleted. Server was also full because the files were also being re uploaded (thus in the main storage and trashbin) by the client that deleted the files from the server. Local files on that client appear to be ok. Local files on all other connected clients were deleted.
I am in the process of cleaning this up and restoring from a server backup, but would really like to figure out how to prevent this in the future as it has taken most of my day.
Confirmed that it was the one client by looking in the servers access-logs
xxx.xxx.xxx.xxx - Bun-Bun [14/Mar/2020:04:19:16 -0600] "DELETE /remote.php/dav/files/Bun-Bun/wallpapers HTTP/1.1" 204 - "-" "Mozilla/5.0 (Windows) mirall/2.6.2stable-Win64 (build 20191224) (Nextcloud)"
I only have one client of that version installed on my home IP. One of those lines for each of the items in the root of my nextcloud folder.
Server OS: Centos 7
Desktop client: Windows 2.6.2 (Win 10 Pro 1803)
Nextcloud: 14
maxxer commented Jan 3, 2022
I just had something very much like this happen this morning. Running NC 23.0.0 on CentOS 7 and using the most recent (I believe, I always allow it to update whenever it asks though I have since uninstalled it because of this issue) Windows client.
What version of desktop client are you using?
This comment has been minimized.
Fieldmouse88 commented Oct 19, 2021
I solved my problem by not nextcloud anymore. Besides "most probably" would not be reassuring enough to actually risk provoking this bug in anything else than a development environment.
maxxer commented Jul 6, 2021
5. Устранение замечаний после обновления.
Зайдем в Настройки облачного хранилища Nextcloud, чтобы узнать результаты самодиагностики текущего вариант развернутой нами версии:
Найдем пункт Общие сведения и перейдем в него:
После некоторого времени самотестирования системы мы можем получить вот такой результат:
Все способы устранения замечаний уже имеются на моём сайте.
После устранения всех замечаний, заново открываем раздел Общие сведения и всё должно быть в порядке:
3. Команды технического обслуживания.
Переводим в режим обслуживания выполнив команду:
Как это видят пользователи:
После перевода системы в режим обслуживания, приступим к обновлению системы облачного хранилища Nextcloud с помощью утилиты updater.phar .
Перейдем в каталог с утилитой updater.phar :
И запустим её выполнение:
Утилита проверит факт наличия последующей версии и предложит выполнить действия по переходу на следующую версию облачного хранилища Nextcloud:
Отвечаем буквой ‘ y ‘, чтобы начать процесс обновления.
Начнётся и продолжится технический процесс скачивания файлов облачного хранилища Nextcloud:
Когда процесс получения файлов закончится, система облачного хранилища Nextcloud предложит проверить вам обновление и совместимость ваших установленных в ней приложений со скачанной версией Nextcloud. Отвечаем буквой ‘ Y ‘.
Побегут процессы работы с приложениями системы облачного хранилища:
В конце обработки приложений утилита updater.phar поинтересуется следует ли сохранить Режим обслуживания? Если ответить утвердительно, то потом его можно отключить вручную. Ответим буквой ‘ y ‘, то есть сохраним включённым Режим обслуживания.
Для того, чтобы обновить систему облачного хранилища Nextcloud до крайней актуальной версии проделайте несколько раз обновления по алгоритму данной инструкции.
Пример: 18.0.5 —> 18.0.11 —> 19.0.5 —> 20.0.2 —> 20.0.9 —> 21.0 (крайняя на момент данной инструкции).
Client configuration
Browser:
Chromium 59.0.3071.86 (Developer Build) (64-bit)
Firefox 52.0.2 (64-bit)
Operating system:
Debian 4.9.30-2 (2017-06-12) x86_64 GNU/Linux
Nextcloud Desktop should not remove files from the server that are not gone from the machine.
2. Устранение ошибки.
Пришлось удалять неисправное приложение из Nextcloud с помощью командной строки из под консоли, так как web-интерфейс стал функционально недоступен из-за этой ошибки.
Путь до установленного в CentOS 7 облачного хранилища Nextcloud будем считать: /files/storage/www/ .
2.1. Активация режима обслуживания.
Переведем облачное хранилище Nextcloud в режим обслуживания:
В конец файла до закрывающей скобки и точки с запятой, по смыслу синтаксиса конфигурационного файла, вставьте эту команду:
Обратите внимание на запятую в конце строки — она важна!
Сохраните и закройте файл. В браузере вы можете увидеть, что система находится в режиме обслуживания.
2.2. Список команд.
Что нам доступно в рамках данного вопроса?
- app:check-code
- app:disable
- app:enable
- app:getpath
- app:install
- app:list
- app:remove
- app:update
- config:app:delete
- group:delete
- user:delete
Что делает каждая команда можно легко догадаться по ее синтаксису. Что еще можно делать с ними ты тоже только что догадались.
2.3. Удаление приложения.
Теперь в консоли выполните следующее…
Посмотрим список установленных, активных и отключенных приложений:
В данном списке находим примерное название неисправного, ранее установленного нами приложения в web-интерфейсе облачного хранилища Nextcloud, и удаляем его полностью из системы. Временное отключение не помогает. Web-интерфейс всё равно работает неисправно даже при деактивированном приложении. В случае удаления приложения, его снова можно будет поставить из магазина приложений. Оно там будет находиться в привычном виде с приглашением установить его снова.
Удаляем неисправный для нас Ebook reader следующим образом:
Готово! Неисправная программа удалена! Забегая вперед, напишу, что я всё сделал правильно и угадал название неисправного приложения. Можно заканчивать данную инструкцию, но всё не так однозначно!
Путем и методом сделать всё прекраснее, облачное хранилище Nextcloud было снова приведено в негодность другими установленными приложениями из магазина приложений. Капитан Очевидность подсказал, что приложения в магазине обновляются не сразу после обновления Nextcloud и даже ругаются с предупреждением, что версии несовместимы и можно сломать Nextcloud, но нам это не страшно и мы героически ломаем вновь и вновь облачное хранилище!
Теперь по делу: названия в приложения из листа приложений могут не совпадать в их реальным названием в магазине приложений, поэтому прийдется думать что из консольного списка ассоциируется с названием из магазина… Иногда приходится удалять приложения на угад из списка. Благо всё удаленное можно заново установить из того же магазина… И заново сломать облачное хранилище… если поставить те же грабли и наступить на них.
2.4. Деактивация режима обслуживания.
Закончив удаление неисправных приложений выключите режим обслуживания облачного хранилища Nextcloud, заменив true на false в файле конфигурации.
Сохраним файл конфигурации. Зайдем снова в систему.
Поздравляю! Облачное хранилище Nextcloud вновь работает в обычном режиме.
Очередное актуальное обновление любимого облачного хранилища Nextcloud — это всегда радость:
И, конечно же, его хочется установить… но не хочется скачивать обновление, потом распаковывать и заменять старые версии файлов облачного хранилища Nextcloud, потом приводить систему в рабочее состояние после обновления. Бывает, что «всё и так работает», зачем обновляться? Зачем рисковать получить неработающий Nextclud?
Не переживайте, обновляться стало гораздо проще!
Для обновления системы облачного хранилища Nextcloud в консольном режиме требуется использовать утилиту updater.phar, которая находится в корневом каталоге updater облачного хранилища Nextcloud.
Внимание! Понижение версии не поддерживается и может повредить ваши данные! Если вы хотите вернуться к более старой версии Nextcloud, выполните новую, свежую установку, а затем восстановите данные из резервной копии.
erenouf commented Dec 23, 2021
I just had something very much like this happen this morning. Running NC 23.0.0 on CentOS 7 and using the most recent (I believe, I always allow it to update whenever it asks though I have since uninstalled it because of this issue) Windows client.
I actually hadn't been doing anything actively with it. Another user was moving folders from one shared folder to another, and later noted that it was empty a while after the move. Looking in the apache log file I see a large number of DELETE commands issued from me to the new location.
I wasn't even aware of that user doing the work, and hadn't been doing anything to explicitly interact with NC except through a browser, but apparently my client thought that the empty directory was somehow the "right" one and I suppose tried to bring the NC server into sync with its emptiness.
2. Утилита командной строки и порядок обновления.
Утилита updater.phar — это PHP скрипт. Для активации её работы вы должны запускать её от имени пользователя от имени которого работает ваша система web-сервера и использовать работу с теми каталогами, к которым, у этого пользователя, есть права доступа.
Например: nginx или apache .
Обновление версии облачного хранилища Nextcloud необходимо обновлять поэтапно:
- Прежде чем вы сможете выполнить обновление до новейшего актуального выпуска, выполните обновление до крайнего предпоследнего выпуска.
- Затем запустите обновление еще раз, чтобы перейти к крайнему предпоследнему выпуску следующего основного выпуска.
- Вы не можете пропустить крайние предпоследние выпуски. Повторно запустите обновление, пока не достигнете актуального доступного (или применимого) выпуска.
- Пример: 18.0.5 —>18.0.11 —>19.0.5 —>20.0.2 —>20.0.9 —>21.0.
rbu commented Sep 23, 2019
This just happened to me a THIRD time within one week. It removed ALL the files from the server and crashed syncing the changes down.
I've disabled the client for now, as it's simply running amok on my files. I have a log file for this incident and the previous comment's incident of partial deletion that I'm happy to answer questions with.
skjnldsv commented Apr 23, 2020 •
Client logs 2.6.4git
Actual behaviour
Two days ago, Nextcloud desktop removed all my files from the server, including folders shared with others. It also removed myself from shares (to me) of others.
The files on the local system stayed intact. However, recovering from this took me significant amounts of time, sweat and conflict solving. Plus, all of the folder timestamps on the server are now gone.
skjnldsv commented Apr 23, 2020
Sure, obervations are as follow:
- See lots of network activity
- Investigate, see the desktop client sending lots of data
- See said client syncing the whole folder from scratch
- Check web and see al previous files are into trashbin and are deleted at the same timestamp as the DELETE requests logs were logged from client to server
DominiqueFuchs commented Sep 25, 2019 •
Hi @rbu , really sorry for your experience with the client. However, to find the root cause for this it´s absolutely crucial to be able to reproduce this over here (if I just set up the client on my standard fedora box, connect it to my fresh NC16 docker instance with a user having a random tree of online folders nothing unexpected happens).
I understand you do not want to expose file names by posting a complete log. Few things though:
mgallien commented Sep 15, 2021
Please affected people can you make sure you upgrade to the latest release (3.3.3 at the moment).
It is my understanding that most probably you will no longer run into this bug with this version.
The solution
Config parameters exist to allow Nextcloud server owners the capability of adapting this behaviour, these are as follows:
- auto – standard behaviour
- D, auto – change the minimum days a file is kept with standard behaviour
- auto, D – delete after a number of days, but earlier if space is required
- D1, D2 – do not delete before, but definitely delete after a certain number of days
- disabled – disable automatic deletion
So to automatically delete files after 30 days, and give Nextcloud the ability to delete sooner if space does eventually run low, you can add this to your config.php :
'trashbin_retention_obligation' => 'auto, 30',
To ensure all files are retained for 30 days, but definitely deleted after 35 days, the following can be added to your config.php :
'trashbin_retention_obligation' => '30, 35',
Obviously the number of days can be modified to suit.
$post->ID, 'post_type' => $post->post_type ) ) ); if ($subpages == 0 )
Support the site. Share the
Feeling extra supportive?
/ (UK) / (Wishlist) / (Patreon)
All funds go towards server costs and test equipment
После устранения недостатков, следует проверить своего облачного хранилища безопасность официальным online-сканером Nextcloud.
Результат должен быть положительным и примерно вот таким, с поправкой на вашу актуальную версию Nextcloud:
Готово! Облачное хранилище Nextcloud готово к эксплуатации.
rbu commented Sep 26, 2019 •
Hey @DominiqueFuchs, thanks for the response. Regarding the log, if you have specific questions regarding the log or a way to share it privately with an individual, I could do that.
- That's a good idea, however I probably won't have the time to do this in the next 10 days (on vacation next week)
- The server is privately hosted (on Docker/Fedora). I'll include a list of enabled plugins [1]. There's a (small) "Samba" remote share enabled in my files (which is the only thing that did not get deleted during any of those incidents).
- The client is on btrfs, same is the server. There's about 40k files in over 1k directories in my personal folder.
- Not activated in the client or server.
Edit: I'd like to add one thing that I found odd. I remember seeing error messages about "too many open files" (in red, part of the sync status bar) before/during one of these incidents happening. I wasn't sure if it's too many network connections, open files or maybe it failed to set up inotify listeners? Note that my client system allows a large number of inotify listeners: fs.inotify.max_user_watches=524288
I found a lot of lines like this in the log files (which could explain why the "Scans" samba share did not get deleted):
I saw the first incident maybe 3 days after upgrading the fedora package from 2.5.2-1.fc30 to 2.5.3-1.fc30. I have since my last comment downgraded to 2.5.2-1.fc30 and haven't seen this problem again.
[1] List of enabled plugins
- Accessibility
- Activity
- Auditing / Logging
- Bookmarks
- Brute-force settings
- Calendar
- Collaborative tags
- Comments
- Contacts
- Deleted files
- External storage support
- Federation
- File sharing
- First run wizard
- Gallery
- Log Reader
- Monitoring
- Nextcloud announcements
- Notes
- Notifications
- Password policy
- PDF viewer
- Plain text editor
- Privacy
- Recommendations
- Right click
- Share by mail
- Support
- Tasks
- Theming
- Update notification
- Usage survey
- Versions
- Video player
- Viewer
- Group folders
- Optical character recognition
- Default encryption module
- Full text search
- Full text search - Elasticsearch Platform
- Full text search - Files
- Full text search - Files - Tesseract OCR
- LDAP user and group backend
- Social sharing via email
- Talk
rbu commented Jan 13, 2020 •
I thought I'd give this another chance and BOOM. all files are gone. again, on 2.6.2. That's after about 2 weeks of usage. I restored and had another few days of it not deleting all files.
diditopher commented Jan 3, 2022 •
I've seen this happen before, but always in combination with long file paths. My guess is that this might be an issue with long file paths in Windows:
In the Windows API (with some exceptions discussed in the following paragraphs), the maximum length for a path is MAX_PATH, which is defined as 260 characters.
When you rename a folder with files or subfolders inside, it is possible to create files with a path longer then the allowed 260 characters. My guess is: When that happens, nextcloud client syncs these files to the server. Then on the next sync the other client fails to create these files due to the path length limitation. One sync later this client sees these files aren't there locally, assumes they were deleted and deletes them from the server.
This comment has been minimized.
bengtj commented Apr 26, 2020
Maybe this is related. I had a 14GB folder with misc files that I yesterday:
- Disconnected from nextcloud.
- Moved from C:\ to D:\ with explorer.
- Connected it again to nextcloud.
Today I discovered that the folder was empty on all clients. I did not find anything on the server in trash. I got desperate and now I'm restoring a backup that I fortunately did the 24th.
And just now I found that there was a restore button on the delete activity in the server that maybe could have fixed it even though I did not find the folders in the trash.
Anyhow, maybe this can be used for reproducing the issue. The client was "Version 2.6.2stable-Win64 (build 20191224)" and Nextcloud 17.0.2 running in a docker container on Fedora 30.
DominiqueFuchs commented Apr 23, 2020
@skjnldsv Could you elaborate on the thing regarding the trashbin please? Not sure if I got your description right there. Do you mean the unintentionally/suddenly deleted files are synced back again after you put the local copies in the trash bin on your client side?
erenouf commented Jan 3, 2022
Ah, that's a really interesting thought. I don't think that's likely it quite here though. I just checked and the directory containing some of the files that were deleted has 60 characters in the path to it. Of course, there were some characters for the local part of the path where I had it mounted and the name of the files within, but I don't think in general those would be around 200 characters more, certainly not for every file that was removed.
I grabbed one of the commands from the apache log here, and I'm replacing some potentially sensitive names with an equal number of X characters:
Would it be likely to increase the chance of confusion if the path were shared multiple times, as seems to happen when a parent and one of its child folders are both shared with another user? For example, we have a folder for "ongoing efforts" and a different directory for each customer inside that. Many of those customer directories also got shared, as well as that "ongoing efforts" so everyone who isn't the original owner of the folder sees both "ongoing efforts" and, say, "customerA" in their top level of the Files app.
If something happens in there, might the app see the move in one path, but not the other and try to clean it up or something like that? Like it gets the notification that a file at "ongoing efforts/customerA/subFolder1/file1.txt" was moved to "ongoing efforts/customerA/subFolder2/file1.txt" but then we also see the mysterious file at "customerA/subFolder2/file1.txt" and have no explanation for it so remove it?
Решил я добавить всяких полезных приложений в своем Nextcloud 18. Зашел во встроенный магазин приложений и начал подключать всё, что может быть полезно на мой взгляд. Щедрой рукой установил себе Ebook reader и еще несколько других приложений…
Рашил посмотреть, как будут открываться книги Ebook reader формата, а тут сюрприз на некоторых вкладках!
Дословно ошибка Nextcloud:
4. Подготовка к эксплуатации после обновления.
После обновления системы облачного хранилища Nextcloud, требуется обновить некоторые индексы таблиц баз данных под новую версию движка Nextcloud и пересчитать количество файлов пользователей, чтобы все их файлы потом отображались корректно в их личных кабинетах.
4.1. Добавление недостающих индексов баз данных.
Разработчики Nextcloud часто добавляют новые индексы к уже существующим таблицам базы данных, например, для повышения производительности.
4.2. Обновление конфигурации Nginx.
Обновите настройку конфигурации Nginx облачного хранилища Nextcloud до актуальной версии.
Копируем в файл конфигурации данный текст и по смыслу меняем его на свои параметры:
Проверьте синтаксис файла конфигурации:
И перезапустите Nginx, чтобы конфигурация засчиталась:
4.3. Выход из режима обслуживания.
Для отключения режима обслуживания выполним команду:
Когда вы выводите сервер из режима обслуживания, вошедшие в систему пользователи должны обновить свои страницы в web-браузерах.
4.4. Переиндексация файлов пользователей.
Запустим консольную команду для работы консольной утилиты console.php в корневом каталоге системы облачного хранилища Nextcloud:
Ответ:
Все файлы всех пользователей успешно переиндексировались и теперь пользователи корректно увидят свои файлы во всех своих каталогах.
The issue
If your Nextcloud instance utilises a data directory situated on a disk/partition/volume far greater in size than the sum of the data you’re storing, you may notice files in the trash are not being deleted.
skjnldsv commented Oct 19, 2021
Been a while since that happened yep 🤔
Matthiasfranck commented Apr 16, 2020 •
The samen happened to me today. Has someone found a solution to solve this? Ik would like to use Nextcloud again, but with such as risk of loosing data this is not possible.
Matthiasfranck commented Apr 23, 2020
In my case the files were gone on both server and client. Even in the nextcloud trash or the client trash (windows) were no files.
So I think that in my case the client started removing files from the computer and this propagated to the server who also started removing the files.
skjnldsv commented Apr 23, 2020
skjnldsv commented Apr 23, 2020 •
Happened to me again today.
Got a DELETE request for all files/folders in root.
erenouf commented Jan 3, 2022
What version of desktop client are you using?
I had kept it up dated any time it asked to, so I presume it was the latest. I have since removed it though since I can't have it deleting files other people create like that. Sorry I can't provide any additional detail, but it happened to me and one other person in the company who had the windows app installed.
This comment has been minimized.
Steps to reproduce
I hope I cannot reproduce this.
skjnldsv commented Apr 23, 2020
-
completely normal install, docker, 18.0.3. Never had an issue before
Читайте также: