-
Notifications
You must be signed in to change notification settings - Fork 808
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]: FreeBSD Host Not Found once downloads of files have started #6024
Comments
I did turn off the Music app on the server which is giving the Deprecated notice in the server log, but this problem remains. I didn't expect it to matter, but it was worth a shot. |
It's appear that I'm not the only one having this issue: |
I face the same issue on FreeBSD 13.2 and nc client 3.9.3. The issue occured also with previous versions of FreeBSD and the nextcloud desktop client, it never worked for me. My workaround is to use nextcloudcmd, which does not show this problem. Windows, Linux and Mac clients on the same network have no issues. |
I have same problem since at least four years across several versions of FreeBSD and NC. Errors identical to the ones supplied earlier in this thread. "QNetworkReply::HostNotFoundError" is rather obvious but question remains where to look, maybe someone with Qt knowledge can advise? |
@jdgwf thanks for including logs |
All other software can reach the server at any time no other errors from any other application. |
Am 2023-09-07 11:35, schrieb Matthieu Gallien:
@jdgwf [1] thanks for including logs
from them, I fail to get an understanding of the issue
not sure how specific the freebsd networking stack is but it really
looks like a network issue
did you check that other software could reach the nextcloud server when
the error occur ?
I have the same issue since I installed my FreeBSD desktop at the
beginnung of 2022.
All other software reaches the server without issues!
Even nextcloudcmd (one time foreground sync included with the desktop
client) does work for me flawlessly.
what if you immediately restart the client when there is a network
error ?
For me it allways starts failing with the next sync.
I really recommend getting an updated version as we are not going to
fix bugs in the stable-3.6 branch
Same issue with 3.9.3.
Regards,
Manfred
Links:
------
[1] https://github.com/jdgwf
|
My apologies for not getting g back in time. I may have mistyped my client version. It was a chemo day for me. My experiences are exactly as above. The server and dns are perfect with other methods and apps, from curl to chrome. I'll be testing with FreeBSD 14 next week or weekend. My gut is telling me it's a threading issue between the API and the OS |
This problem persists in a fresh install of FreeBSD 14.0-BETA2
|
The same issue persists in 14.0-BETA2 |
FWIW, this is roughly the line seen with
Checking v3.10.0 release notes, I see https://github.com/nextcloud/desktop/pull/5036/files which could happen to address these issues or, at least from the looks of the code: help with the debugging because it has more detailed error logging. |
We're still seeing the same issues in the latest patch:
|
Continuing on my observations as I test, I've noticed that some remote folders work just fine and some just fail with Host Not Found. Most of these errors stem from a long URL path such as deep into a .git repository folder. I wonder if it could be a variable CONST size issue in the QT abstractnetworkjob or other library which is cutting the variable off. Thoughts? |
I have been seeing this issue on and off over the last 4-5 years or so (I posted one of the issues referenced in #6024 (comment)). |
Unfortunately I (very respectively) disagree that it's a system level/open file problem. If I set up my Nextcloud client to connect to the server by IP address and accept the "invalid" cert, I have no issues. It's a DNS or Resolv.conf issue. Even if I enter in the IP address in the hosts file it'll still fail. It's got to be something on how QT is performing its mass nslookups is failing. Only as an https;//THE.HOST.IP.ADDY instead of https://nextcloud.mydomain.com works without error on FreeBSD This is a relatively new revelation for me, and although I have to accept the conflicting cert, it works well and fast hitting the host IP (and I had to set the Host IP to serve nextcloud by default, and I hate that too ) |
I assume I have a user reporting the same issue, but interestingly on Windows 10. I assume it is the same kind of issue because it does not seem to be an issue of the DNS resolver (a pihole of mine, logs reasonable response times). And this one user already experiences other issues because of the combination of many small files (37k to be precise) requiring a huge amount of storage (147 GiB). I do not have the option now to change the app to use the IP directly because of security issues, but I can try to gather more telemetry data (version of client, …) when I come by. |
I have the client running on several Win7 machines, Ubuntu and Win11 and it has always worked fine. I just installed it on a new Win11 machine, an MSI Cubi 5 10M and it has this problem. Host not found at a random point during synching. Sometimes it restarts and gets a bit further, so it eventually completes the syncing. Sometimes I need to quit it and start it again for it to see the host. Networking seems solid on this machine. I can watch video without interruptions and I can use the web version and ping the host, so it is definitely accessible. The only thing I think is different about this machine is it is perhaps the fastest machine I have. Also it is running a Norton free trial, whereas my other machines use ESET virus checker. |
Yes. This is still an issue on FreeBSD 14.1 as well |
I replaced the Norton virus checker with ESET, so it is the same as my other machines but I still get the problem. I don't understand why it needs to lookup the host more than once during a sync operation. How do I change the configuration to use the IP address? I can't see any way to change the host, once set up. |
Replacing the host name with its IP address in the nextcloud config file gets around the problem for me. I found that if I ping the hostname from a DOS box then it only succeeds about 50% of the time, so it seems to be a Windows 11 problem, rather than NextCloud problem. Possibly it shows up in NextCloud because it seems to look up the server IP over and over again instead of doing it once and then using the IP address. The odd thing is my other Windows11 machine that lives in Tenerife and accesses my server over VPN works reliably. This new machine that has a direct ethernet connection to the RPI4 is unreliable doing the DNS resolve. |
Howdy there folks. This is still an issue in NXC 3.13.0 and FreeBSD 14.1. Please, please let me know what I can do to help squash this bug :) |
Bug description
Everything works as expected until downloading of selected synced files have started. Suddenly a "host not found" error appears on the client and stop the sync entirely.
Server works great with various Linux and Mac NextCloud Desktop clients.
Steps to reproduce
Open NextCloud desktop
Sign into remote server
Select all and/or a few few drectories
Comparison of files needed to download works
After a while of downloading files error pops up - rarely for the same file.
Expected behavior
Syncing of files as on the Mac, Windows, and Linux cliens.
Which files are affected by this bug
Random
Operating system
Linux
Which version of the operating system you are running.
FreeBSD 13.2
Package
Compiled it myself
Nextcloud Server version
25.0.10
Nextcloud Desktop Client version
Version 3.6.4 (FreeBSD)
Is this bug present after an update or on a fresh install?
Fresh desktop client install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
Nextcloud Client Debug Logs
nextcloud-host-not-found.zip
The text was updated successfully, but these errors were encountered: