Backup failed - Temporary failure in name resolution

Virtualmin
1

My backups have recently started failing with no obvious reason. I’m on Ubuntu 20.04LTS

Backup failed! See the progress output above for the reason why. Total backup time was 00 minutes, 30 seconds.

Sent by Virtualmin at: https://garvanprod.node.mooball.net:10000

File does not exist: Can't connect to nyc3.digitaloceanspaces.com:443 (Temporary failure in name resolution)

Temporary failure in name resolution at /usr/local/share/perl/5.30.0/LWP/Protocol/http.pm line 50.
 at S3/ListBucketResponse.pm line 26.

I have no problem resolving the domain by command line ‘dig’ and I’m sure my DNS servers are fine. This seems to be a problem specific to Perl only.

2

One possible workaround is to use the IP address of nyc3.digitaloceanspaces.com instead of the domain name…

3

Actually that makes no difference at all:

Error - Perl execution failed
File does not exist: Can't connect to 162.243.189.2:443 (hostname verification failed) hostname verification failed at /usr/local/share/perl/5.30.0/LWP/Protocol/http.pm line 50. at S3/ListBucketResponse.pm line 26.

As I expected, this is not actually a DNS issue, it seems to be more specifically related to Perl.

4

You are right, @tomcameron. And the error message that your most recent comment contains tells us that it is perhaps the S3 emulation at DO which might be the cause of this intermittent failure.

Does your bucket name have dots in it?

5

Yes the bucket name does have a dot.

But the odd thing is that I have other machines successfully backing up to this very same bucket at the moment and this machine was backing up with no issues for several weeks, then it just stopped working in the last week.

6

Yup, it’s a known bug / issue with S3. It crops up intermittently and is therefore difficult to identify.

Remove the dot from the name and let us know how it goes.

7

OK I’ll try that, thanks.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.