-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Download file > 512MB from SMB external storage not possible (NC 23.0.2) #31308
Comments
I had the same issue using Ubuntu 20.04 and smbclient. After installing php-smbclient (using an additional ppa) this issue was solved. |
Thanks, tried that and solved my issue as well. |
Samo issue here, max 512mb download on NC 23.0.2 with external storage app 1.15.0 on Ubuntu 20.04 . Installed PPA php-smbclient 7.4 1.0.6 from https://dannyda.com/tag/ubuntu-20-04-1-lts-php-smbclient/ Still not working. |
Same issue here, nextcloud 22.2.5, external storage app (files_external) version 1.13.1, OS Ubuntu 20.04 Works with php7.4-smbclient version 1.0.6-6+ubuntu20.04.1+deb.sury.org+10 as per instructions from https://dannyda.com/tag/ubuntu-20-04-1-lts-php-smbclient/ Restart php-fpm with systemctl restart php7.4-fpm after installing php7.4-smbclient. |
Not sure if this is helpful for anyone. I am running the latest nextcloud 23.0.3 docker container. Ran into this as well. I simply installed libsmbclient-dev and then ran pecl:
Anyone feeling lazy and running docker, I made a docker container (I only update this every few minor releases): You can see the dockerfile here, pretty simple: |
@icsy7867 Thanks using libsmbclient-dev and then ran pecl solved my issue. |
I can confirm this bug with version 24.0.0 |
I'm using the docker Image, but pecl isn't working for me: After installing libsmclient-dev and smbclient within apt I get the following error:
Also Any ideas what might be wrong? |
I wasnt able to reproduce your issue. Also you shouldnt run the echo line if you werent able to run PECL as the .so file wont exist. I pulled the latest nextcloud continaer: And then I exec'd into the container: And I was able to successfully run:
|
My Host is a RaspberryPi with Pi OS arm64 (Bullseye) with Samba 4.13.13 installed. I am using a Portainer Stack to run the containers:
My ENV file:
I can reproduce my issue after deleting the image and running it from nextcloud:latest:
Could this be related to the RaspberryPi only? |
I'm not sure. But just a guess. |
Someone also mentioned pihole blocking pecl |
Thanks a million times for pointing me that direction! It was the pihole blocking.. |
This worked for me:
Thanks. |
I had the same issue with NC 24.0.4, External Storage Support 1.16.1, Ubuntu 20.04.4 LTS, PHP 8.1.8. |
Same Issue here... |
Please simply install php-smbclient then |
Please alter the Documentation then https://github.com/nextcloud/documentation/blob/master/admin_manual/configuration_files/external_storage/smb.rst |
PRs are welcome! |
Case closed.. lol |
I've created this issue for you to not forget it: nextcloud/documentation#9428 |
Installing php-smbclient can only be a workaround, since not all linux distribution provides a package for this. Installation via pecl or adding external repositories may affect the consistency of the installation and its maintainability. This is not acceptable in professional environments. Since smbclient is the CIFS client which is present on all linux distributions, the focus should be on finding the actual bug instead of using workarounds and closing bugreports. So please reopen the bug. Thanks! |
I also have this issue! And before being told to install php-smbclient:
|
Is this in a docker container? Try doing and apt-get update first. I also used a different set of commands personally. |
That worked! Could you share the docker file? It does not exist anymore |
this only becomes valid in ubuntu 22 required for nc - nextcloud/server#31308
Today I noticed php-smbclient is not working with Samba 4.17.5 from Debian. Recompiled again as well against the new lib-smbclient: So I've reverted to using smbclient and now have the 512MB bug again. Really, smbclient is standard and should be the path forward. So whatever bug is causing this really needs to be looked at. If the ticket is not re-opened in the next couple of days, I'll open a new ticket as I don't know if the admins are notified if a comment takes place on a closed ticket. |
https://github.com/icsy7867/nextcloud I also finally got around the playing with gitlab. I am automatically rebuilding these weekly with the latest major versions (24 and 25): Feel free to use them if you like. |
Had the same bug, got it solved by running the following commands within the docker container: apt update && apt -y install libsmbclient-dev libmagickwand-dev && pecl install smbclient && echo “extension=smbclient.so” > /usr/local/etc/php/conf.d/docker-php-ext-smbclient.ini && pecl install inotify Still, this bug should be fixed, ideally php-smbclient directly integrated in Nextcloud |
Bug description
When I try to download files larger than 512 MB from SMB/CIFS shares (attached via the "External storage support" Nextcloud), the download fails (downloading starts then stops at 512 MB and finally results in failure).
This is on a NC 23.0.2. / External Storage app version 1.15.0 (latest). When I copy the directory /var/www/html/apps/files_external/3rdparty/icewind from the backup of NC 23.0.0 than it works again.
Therefore there is an issue at least with the combination of the external storage app with the used icewind 3rdparty app.
Steps to reproduce
Expected behavior
Download without issue
Installation method
Manual installation
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: