Amazon S3 error, "Perl execution failed" on one server but not the other

I have two web servers. Amazon S3 backup works on the CentOS 6.x one but fails on the CentOS 7.x one. The one that fails is giving me the following error. I know that my S3 credentials and premissions are correct since I can test it on my other server. Both servers are using using latest Webmin/Virtualmin and Automatic theme version 17.

HTTP/1.0 500 Perl execution failed Server: MiniServ/1.770 Date: Wed, 14 Oct 2015 03:33:08 GMT Content-type: text/html; Charset=iso-8859-1 Connection: close

Error - Perl execution failed

File does not exist: Can’t connect to
at S3/ line 27.

Ping. Anyone have suggestions?

So I finally figured out that there’s an install of some Amazon software that needs to be done. This can be done by following the instructions here. You might need to upgrade Python to version 2.7 if you’re using CentOS 6.x since by default Python 2.6 is installed. Super easy with CentOS 7 though since the right version of Python is installed… just follow directions.


Thanks for sharing your solution!

I’ll talk to Jamie, and see if he can improve the error detection here to catch that case and throw a helpful error, rather than the more obscure one that you were seeing.