Minor problem after upgrading to Dedicated from VPS

[technabob]

I've been using the following approach to backup my Hostican VPS server using Amazon S3...

Automatic wordpress backups to Amazon S3 | Brendan Nee

Now that I'm up and running on my new dedicated box, I'm getting the following error whenever the backup shell script runs:

which: no curl in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/courier-imap/sbin:/usr/lib/courier-imap/bin:
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin)

curl not found on the path or not executable

I'm assuming that means that the curl module isn't properly installed or permissioned, but I'm not sure what I need to do to add this.

Any ideas?

[technabob]

The plot thickens...

When I check my PHP config, I see the following...
curl
cURL support enabled
cURL Information libcurl/7.19.0 OpenSSL/0.9.7a zlib/1.2.1.2 libidn/0.5.6

So doesn't this mean that curl is installed? I can't figure out why my S3 Backups can't use it then, unless I'm confused and the cURL library used by PHP is something different than the one that the shell script is looking for.

Any help would be greatly appreciated, as my backups are now failing.

[Shazam]

Originally Posted by technabob

The plot thickens...

When I check my PHP config, I see the following...
curl
cURL support enabled
cURL Information libcurl/7.19.0 OpenSSL/0.9.7a zlib/1.2.1.2 libidn/0.5.6

So doesn't this mean that curl is installed? I can't figure out why my S3 Backups can't use it then, unless I'm confused and the cURL library used by PHP is something different than the one that the shell script is looking for.

Any help would be greatly appreciated, as my backups are now failing.

That seems correct to me. Did you change anything in the default configuration of either your VPS or dedicated server?

Beyond that, you might want to ask the author of that blog, who wrote the instructions, if he has any idea. I haven't used S3 for backups.

[technabob]

No. In both cases they were the default configuration from Hostican, and I've not installed any custom OS or Apache modules.

If you run "which curl" from the shell, though, it says that curl isn't installed. Isn't that part of the default config on your servers?

[lnxcode]

Originally Posted by technabob

No. In both cases they were the default configuration from Hostican, and I've not installed any custom OS or Apache modules.

If you run "which curl" from the shell, though, it says that curl isn't installed. Isn't that part of the default config on your servers?

I will have one of the system administrators take a quick look at it for you. We normally don't do this... However, in this case, as you just upgraded it warrens the review.

[lnxcode]

*** update ****

I've found what was going on here... the ownership was nobody:nobody <-- so we've fixed that for you, you should be all set

You may need to re-install the WP-Cache plugin

[technabob]

Originally Posted by lnxcode

*** update ****

I've found what was going on here... the ownership was nobody:nobody <-- so we've fixed that for you, you should be all set

You may need to re-install the WP-Cache plugin

I appreciate the help, but I don't understand what this has to do with the problem. Wordpress and WP-Cache have nothing to do with this issue.

If you execute the shell command "which curl", you still get an error, which indicates that curl is not installed...

/usr/bin/which: no curl in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/courier-imap/sbin:/usr/lib/courier-imap/bin:/usr/local/sbin:
/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin)

Any ideas?

[technabob]

As a matter of fact, changing the owner of that directory back to technabob has broken other things in Wordpress, since PHP seems to run as nobody.

I actually had to put those permissions back the way they were, or else Wordpress can't write to the file system.

Again... Not sure what any of this has to do with cURL not working from the unix shell anyhow.


I appreciate the help, but I think you're digging under the wrong rock.

[lnxcode]

Originally Posted by technabob

As a matter of fact, changing the owner of that directory back to technabob has broken other things in Wordpress, since PHP seems to run as nobody.

I actually had to put those permissions back the way they were, or else Wordpress can't write to the file system.

Again... Not sure what any of this has to do with cURL not working from the unix shell anyhow.


I appreciate the help, but I think you're digging under the wrong rock.

CURL is in the server. If you create a phpinfo file

And place it in the site and run the link, you will see that cURL is compiled into Apache.
It sounds like you just have to copy the php.ini from the server and place the copy from the server into the public_html or the wp-includes and wp-admin folders

[technabob]

This isn't a PHP problem at all. I see that cURL is available to PHP.

I'm actually having trouble getting curl to be available when running a Unix Shell script that's out in my home directory. This was never a problem on my VPS, but is on the dedicated server.