Support

Host: siteground own vps
Jooma 2.5.27
Akeebabackup : 4,0,3

scheduling cronjob on siteground:

wget --max-redirect=10000 "http://www.outside-action.dk/index.php?option=com_akeeba&view=backup&key=[LEFT OUT FOR SECURITY REASONS]" -O - 1>/dev/null 2>/dev/null

and

curl -L --max-redirs 1000 -v "http://www.outside-action.dk/index.php?option=com_akeeba&view=backup&key=[LEFT OUT FOR SECURITY REASONS]" 1>/dev/null 2>/dev/null


uploading to amazon s3 post processing

both commands get this:

no error, no backup is made. We do this all the time on lots of sites, and it works fine. but this site does not work.

consulting siteground support they came up with this:

Thank you for contacting our Help Desk.

I have tried to run the cron job manually by executing the command you set up for it while logged in the server via SSH. The command provided the following output:

Code:
root@serv01 [~]# curl -L --max-redirs 1000 -v "http://www.outside-action.dk/index.php?option=com_akeeba&view=check&key=[LEFT OUT FOR SECURITY REASONS]"
* About to connect() to www.outside-action.dk port 80 (#0)
* Trying 185.62.239.57... connected
* Connected to www.outside-action.dk (185.62.239.57) port 80 (#0)
> GET /index.php?option=com_akeeba&view=check&key=kpnsim2011 HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.14.0.0 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: www.outside-action.dk
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 24 Sep 2014 11:58:22 GMT
< Server: Apache/2.2.24 (Unix) mod_hive/3.6 mod_ssl/2.2.24 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_fcgid/2.3.6
< Set-Cookie: 1839cf414da11b90b3b4c863af81e159=5keeh9p3mopc135l3oocoeq4l5; path=/
< Host-Header: 192fc2e7e50945beb8231a492d6a8024
< Transfer-Encoding: chunked
< Content-Type: text/html
<
* Connection #0 to host www.outside-action.dk left intact
* Closing connection #0
200 No need to run: no failed backups or they were already notificated


As you can see the command returns that there is no need to create a backup, so you should probably check the Akeeba configuration to resolve the problem.


Can anyone tell me what i am doing wrong??