-
Notifications
You must be signed in to change notification settings - Fork 62
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
Update entrypoint.sh #27
base: main
Are you sure you want to change the base?
Conversation
So far I'm unable to replicate this issue. Can you provide more details, including the exact commands you're using to run both the rsync-server Docker container and your rsync client command (with any secrets or sensitive information redacted), and also the OS of the rsync client. Thank you. |
Synology NAS rsync via HyperBackup fails due to this issue. Here is the full log:
with log to stderr instead of stdout:
|
Here is the docker compose section of rsync server:
|
some hosts can't connect because logging is logged to stdout instead of stderr causing clients to be confused about welcome message.
rsync: server sent "2024/09/25 19:21:37 [519] name lookup failed for 172.30.30.100: Name or service not known" rather than greeting
rsync error: error starting client-server protocol (code 5) at main.c(1863) [Receiver=3.2.7]