>=3.2.x does not work (on Ubuntu) if local sync folder is on SMB

cholzer79 commented 3 years ago

For a bit over 1 year I have been using the Nextcloud client on Ubuntu 20, which is a Virtual machine on my ESXi 6.7.0 Update 3.

Originally I installed the Nextcloud desktop app via PPA, which worked great!

About a month ago I upgraded it to the latest version, which caused the client to take forever to start, and once it started it was very unresponsive. It became impossible to go to the "Settings" screen as Ubuntu then told me that the app is unresponsive and asked if i want to wait or shut it down. After that update it did not sync anymore either.

So I completely uninstalled the Nextcloud desktop app (manually removed all files and folders that mentioned nextcloud) and tried the "appimage" version from the Homepage.

Sadly 3.2.1 and 3.2.2 showed the exact same behaviour.

So I then I downloaded the old 3.1.1 version and look at that, it works just fine! :D

Question: where does the appimage version store the nextcloud desktop app configuration and logs? Because I can't find that anywhere on the system!?

Steps to reproduce

Use Ubuntu 20 (in my case its a VM accessed through the ESXi webinterface)
upgrade your excisting, working 3.1.x Nextcloud Desktop App to 3.2.x

Expected behaviour

It should work.

Actual behaviour

Extremely sluggish, "Settings" window does not open, Ubuntu keeps telling me that the app does not respond, it does not sync

Server configuration

System provided by hetzner, NX20 version

Operating system: Linux 5.4.0-72-generic x86_64

Database: 10.3.29

PHP version: 7.4.16

Nextcloud version: 20.0.9

go2sh commented 3 years ago

Hey, I transfered your issue into the desktop repo as it is about the desktop client primarily.

cholzer79 commented 3 years ago

Hey, I transfered your issue into the desktop repo as it is about the desktop client primarily.

Oops, I am sorry. First time creating a report. 😅

FlexW commented 3 years ago

The configuration should be in ~/.config/Nextcloud like with the PPA.

Could you please provide your logs? Otherwise it will be impossible to see what the problem is.

cholzer79 commented 3 years ago

The configuration should be in ~/.config/Nextcloud like with the PPA.

Oh boy, maybe I should enable the "hidden files" option in nautilus so I see the folder. 😅

Here is the log from 3.2.2 (why is it called "owncloud"?) 20210602_0852_owncloud.log

I closed 3.1.1, then launched 3.2.2 - I don't know why it complains about the db to be "locked" as no other instance was running. The 3.2.2 AppImage client is just as unusable as my previous (via PPA) installation got when I updated it.

notResponding

3.1.1 AppImage client works like a charm! Just switched back to it after this test.

FlexW commented 3 years ago

Thanks for the logs. It's called owncloud because Nextcloud is a fork of ownCloud and no one changed this string until now:) You have a few database lock errors in your logs. I'm unsure why they are there, but what you could try is to stop all clients, and then delete the files starting with ._sync in all your sync folders. Then start the 3.2.2 client again. That maybe helps.

cholzer79 commented 3 years ago

You have a few database lock errors in your logs. I'm unsure why they are there, but what you could try is to stop all clients, and then delete the files starting with ._sync in all your sync folders. Then start the 3.2.2 client again. That maybe helps.

Yeah but why only with the 3.2.x client? if the db files would realy be locked then i should not be able to just close the 3.2.x client, fire up 3.1.1 and it works like a charm.... right? 🤔😅

btw. this is the only PC in the LAN that has the nextcloud client installed. so there is no other nextcloud client in the lan accessing these files at the same time. they are located on a NAS though (unraid smb share) in case something changed between 3.1.1 and 3.2 in that regard.

Also if the db files were locked and that causes the issue then the client does not handle this gracefully. The user has no idea what is going on and why the client is slugish & freezing.

github-actions[bot] commented 3 years ago

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!

mgallien commented 3 years ago

You have a few database lock errors in your logs. I'm unsure why they are there, but what you could try is to stop all clients, and then delete the files starting with ._sync in all your sync folders. Then start the 3.2.2 client again. That maybe helps.

Yeah but why only with the 3.2.x client? if the db files would realy be locked then i should not be able to just close the 3.2.x client, fire up 3.1.1 and it works like a charm.... right? thinkingsweat_smile

btw. this is the only PC in the LAN that has the nextcloud client installed. so there is no other nextcloud client in the lan accessing these files at the same time. they are located on a NAS though (unraid smb share) in case something changed between 3.1.1 and 3.2 in that regard.

Also if the db files were locked and that causes the issue then the client does not handle this gracefully. The user has no idea what is going on and why the client is slugish & freezing.

Do I understand correctly that the desktop client sync folder is located on a mounted SMB share ? In that case, I am pretty sure you will run into problems with SQLite lock handling. If I remember correctly I had that between Windows desktop and server in the past. At one point in tome (do not remember when) the sync database has been moved to the sync folder. That change was beneficial for a lot of use case but not your one. This may explain why you see differences. I also fail to see how I would address this. Sorry

cholzer79 commented 3 years ago

Do I understand correctly that the desktop client sync folder is located on a mounted SMB share ?

Correct - and the Ubuntu machine is the only machine that has the nextcloud client installed in my LAN. So it's not like 2 clients are competing to access the same file(s). :)

In that case, I am pretty sure you will run into problems with SQLite lock handling. If I remember correctly I had that between Windows desktop and server in the past.

Before I switched to Ubuntu I had a Windows 10 machine running the nextcloud client, with the sync folder also on the NAS. That worked without an issue :)

At one point in tome (do not remember when) the sync database has been moved to the sync folder. That change was beneficial for a lot of use case but not your one. This may explain why you see differences.

was that between 3.1.1 and 3.2.x by any chance? If that was done after 3.1.1 then this would explain why 3.1.1 works without a problem while 3.2.x does not work at all.

main reason why I moved from OneDrive to nextcloud is that I can have have all sync folders for all accounts on the NAS.

github-actions[bot] commented 3 years ago

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!

mgallien commented 3 years ago

Do I understand correctly that the desktop client sync folder is located on a mounted SMB share ?

Correct - and the Ubuntu machine is the only machine that has the nextcloud client installed in my LAN. So it's not like 2 clients are competing to access the same file(s). :)

In that case, I am pretty sure you will run into problems with SQLite lock handling. If I remember correctly I had that between Windows desktop and server in the past.

Before I switched to Ubuntu I had a Windows 10 machine running the nextcloud client, with the sync folder also on the NAS. That worked without an issue :)

At one point in tome (do not remember when) the sync database has been moved to the sync folder. That change was beneficial for a lot of use case but not your one. This may explain why you see differences.

was that between 3.1.1 and 3.2.x by any chance? If that was done after 3.1.1 then this would explain why 3.1.1 works without a problem while 3.2.x does not work at all.

main reason why I moved from OneDrive to nextcloud is that I can have have all sync folders for all accounts on the NAS.

That kind of setup is not something we test against. It is pretty much hard to get reliable access to SQLite over a mounted SMB share. I guess this needs a fix. Unfortunately we are pretty busy at the moment so I cannot make promises on when we can solve it.

cholzer79 commented 3 years ago

It is pretty much hard to get reliable access to SQLite over a mounted SMB share. Since I moved the client back to 3.1.1 I had no problems anymore. Also had no problem with earlier versions.

I guess this needs a fix. Unfortunately we are pretty busy at the moment so I cannot make promises on when we can solve it. Understood - I will stay on 3.1.1 then. :)

benjamindahl commented 3 years ago

I've got the exact same problem. Ubuntu 20.04 LTS Storage as SMB mount Nextcloud Server 22.1.1.2 Nextcloud Desktop Client > 3.1 (tried them all)

Server system provided by Owncube.com Linux 4.15.0-22-generic x86_64 QEMU Virtual CPU version 2.5+ (4 cores) PHP 7.4.23 MySQL 8.0.26 4 GB Memory

latest working desktop client version 3.0.3 all later versions react like described above. nextcloud.cfg.txt fstab.txt

cholzer79 commented 3 years ago

I've got the exact same problem. Ubuntu 20.04 LTS Storage as SMB mount Nextcloud Server 22.1.1.2 Nextcloud Desktop Client > 3.1 (tried them all)

latest working version 3.0.3 all later versions react like described above. nextcloud.cfg.txt fstab.txt

Thanks for confirming, good to know that I am not alone with this issue! :D

benjamindahl commented 3 years ago

Thanks for confirming, good to know that I am not alone with this issue! :D

Yes, and I can confirm the similar way I've taken to come to that temporary solution. Started with the PPA-version and then had to switch to the legacy appimage (3.0.3)

benjamindahl commented 2 years ago

Hey just wanted to mention that the problems still exists. Latest Ubuntu 20 LTS updates installed Nextcloud client 3.4.3 Last working version appimage 3.0.3

cholzer79 commented 2 years ago

Hey just wanted to mention that the problems still exists. Latest Ubuntu 20 LTS updates installed Nextcloud client 3.4.3 Last working version appimage 3.0.3

I ditched netxcloud because of this bug. I am back to onedrive now using https://github.com/abraunegg/onedrive which works perfectly and does not suffer from this problem.

This move also eliminated many of my problems that I had with the nextcloud mobile app - onedrive on android is just much more stable and auto-sync's instantly.

nextcloud / desktop