Hi Alexandre, > [...] > Jan 27 08:32:19 zen s3ql: raise HostnameNotResolvable(address[0]) > Jan 27 08:32:19 zen s3ql: dugong.HostnameNotResolvable: Host > ideiao.commondatastorage.googleapis.com does not have any ip addresses > Jan 27 08:33:43 zen s3ql: Unmounting file system... > > it seems that at 08:32:19 the internet connection went down, or the > dns server went down (google dns servers, by the way), and s3ql crashed. > [...] S3QL can in some circumstances generate a lot of parallel DNS requests*. On one occasion my system generated so many requests per second that Google's DNS temporarily rejected DNS requests from my IP. That resulted in a S3QL crash as you have experienced. To workaround that crash reason, I installed Unbound (https://unbound.net/) locally. Since then (~ 3 months ago) I did not have that problem anymore.
On Ubuntu all you need to do is $ sudo apt-get install unbound to install and activate unbound. * = As far as I know, every fresh HTTP Connection results in a DNS request, and because of issue #178 (https://bitbucket.org/nikratio/s3ql/issues/178) there are ~1000 requests per second on my machine -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
