SQL Server Database Engine
Core component of SQL Server for storing, processing, and securing data
The issue was finally solved it was due to the dns in secondary server
SQL Server log shipping in linux issues with restore job cannot retrieve restore settings
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 26%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAH%3C/text%3E%3C/svg%3E)
ABDUL HAQ ABDUL LATHEEF
25
Reputation points
I am facing a strange issue in sql server log shipping between 2 linux servers.The restore job fails by telling cannot retrieve restore setting unable to connect to 127.0.0.1 .the backup job was working fine on primary
It had worked in between , but still the same again
SQL Server Database Engine
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 79%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDY%3C/text%3E%3C/svg%3E)
Dinesh Yadlapalli 85 Reputation points Microsoft External Staff Moderator2025-10-27T13:43:12.2833333+00:00 Hi @ABDUL HAQ ABDUL LATHEEF,Thank you for reaching out to the Microsoft SQL Q & A Forum.
Thanks for the update. We are happy to hear that you have resolved the issue. Thanks for sharing the details here. Please do let us know if you have any further queries.
Regards,
Dinesh
Sign in to comment
Answer recommended by moderator
2 additional answers
Sort by: Most helpful
-
ABDUL HAQ ABDUL LATHEEF 25 Reputation points
2025-10-27T14:18:14.27+00:00 See actually , ip v6 was not the issue ,the issue was that 8.8.8.8 was not allowed in the secondary sevrer , as it was the default DNS ,it was working in the beginning as there was internet in the server for 2 days .
So when the job or agent was trying to connect to local database , it tried the dns server 8.8.8.8 and then threw connection time out
Once the network team allowed 8.8.8.8 ,everything went fine
-
Q&A Assist2025-09-18T22:12:01.3266667+00:00 AI generated content. This question contains an answer created with AI from Q&A Assist. Learn moreIt seems you are encountering issues with SQL Server log shipping between two Linux servers. The error message indicating that it "cannot retrieve restore setting unable to connect to 127.0.0.1" suggests there may be a problem with the configuration of the Samba share or network settings.
Additionally, the error "Length specified in network packet payload did not match number of bytes read; the connection has been closed" typically indicates a mismatch in the expected data size during communication, which could be due to network issues or configuration problems.
Here are a few steps you might consider to troubleshoot the issue:
- Check Samba Configuration: Ensure that the Samba share is correctly configured and accessible from both servers. Verify that the necessary permissions are set and that the share is properly mounted.
- Network Connectivity: Test the network connectivity between the two servers. You can use tools like
pingortelnetto ensure that the servers can communicate over the required ports. - Review SQL Server Logs: Look at the SQL Server error logs for more detailed error messages that might provide additional context about the failures.
- Firewall Settings: Ensure that any firewalls on the servers are configured to allow traffic on the necessary ports for SQL Server and Samba.
- Update SQL Server: If you are using an older version of SQL Server, consider updating to the latest version or cumulative update, as there may be fixes for known issues.
If these steps do not resolve the issue, you may need to consult with your network administrator or the vendor of the client library for further assistance.
References: