Error Messages getting large

[Nuno]

Can anyone please suggest what I can do with the following? I'm getting this over and over on the same server, and the error logs are heading north of 3Gb:

[01-Oct-2013 08:13:32 Europe/London] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/suhosin.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/suhosin.so: cannot open shared object file: No such file or directory in Unknown on line 0
[01-Oct-2013 08:13:32 Europe/London] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo.so: cannot open shared object file: No such file or directory in Unknown on line 0
[01-Oct-2013 08:13:32 Europe/London] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_sqlite.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_sqlite.so: cannot open shared object file: No such file or directory in Unknown on line 0
[01-Oct-2013 08:13:32 Europe/London] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/sqlite.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/sqlite.so: cannot open shared object file: No such file or directory in Unknown on line 0
[01-Oct-2013 08:13:32 Europe/London] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_mysql.so' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/pdo_mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
[01-Oct-2013 08:13:32 Europe/London] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/extensions/no-debug-non-zts-20060613/ixed.5.2.lin' - /usr/local/lib/php/extensions/no-debug-non-zts-20060613/ixed.5.2.lin: cannot open shared object file: No such file or directory in Unknown on line 0
[01-Oct-2013 08:13:32 Europe/London] PHP Deprecated: Directive 'magic_quotes_gpc' is deprecated in PHP 5.3 and greater in Unknown on line 0

 

[koolpanda]

Good morning Nuno.

As the errors show files in the same folder (/usr/local/lib/php/extensions/no-debug-non-zts-20060613/), three things spring to mind;

First check to see if the file exists. Go to the terminal, or open and ftp clients and see if the file actually exists.

Second if they do exist, then it may be that the file permissions have been changed, or corrupted. This can happen by software so it may not be a human issue.

Third has PHP been updated. This is the least likely, but the final error points to this. That said the previous two potential issues could cause this too.

Hope this helps

Regards

John

 

[Faevilangel]

Is this on WP?

The error seems to show that the website / script is trying to access scripts which aren't available on your server.

Unless you have dedicated hosting, this will be down to your hosting to either add the scripts (into apache/php) or you need to look at another way of doing the task.

 

[Nuno]

Thanks John,
sorry to be noobish but where would I find (/usr/local/lib/php/extensions/no-debug-non-zts-20060613/) in a Wordpress install?
I have looked with ftp and in the cp. and the search function in cpanel's file manager didn't help.

 

[Faevilangel]

Thanks John,
sorry to be noobish but where would I find (/usr/local/lib/php/extensions/no-debug-non-zts-20060613/) in a Wordpress install?
I have looked with ftp and in the cp. and the search function in cpanel's file manager didn't help.

It's a server thing, you need to speak to the host

 

[Nuno]

Thanks Fave,
Yes it is WP and the hosts says "This is being caused by incorrect coding on your site, you will need to ask your developer to take a look at these errors"

No names but I was a bit underwhelmed by that as all the Google posts pointed to Apache/php/.ini (which is well above my pay grade).

 

[andygambles]

Thanks John,
sorry to be noobish but where would I find (/usr/local/lib/php/extensions/no-debug-non-zts-20060613/) in a Wordpress install?
I have looked with ftp and in the cp. and the search function in cpanel's file manager didn't help.

I assume you are on shared hosting. If this is the case then you do not have access to these files. This is to do with PHP 5.3 and new sql pdo settings. See if you can drop to 5.2 or you might be able to override the php.ini setings depends on how your hosting is set-up.

Try uploading a file called php.ini to your website root with the following contents

;;extension=pdo_sqlite.so
;;extension=sqlite.so

See if that works.

I assume your Wordpress is functioning correctly? These are really warning errors so you could just keep clearing your error log until Wordpress or PHP fix it.

 

[Faevilangel]

Thanks Fave,
Yes it is WP and the hosts says "This is being caused by incorrect coding on your site, you will need to ask your developer to take a look at these errors"

No names but I was a bit underwhelmed by that as all the Google posts pointed to Apache/php/.ini (which is well above my pay grade).

Basically your host is 50% right.

1) The above are errors which have been disabled by the host, they aren't used maliciously but I know of a few hosts which disable the scripts.

2) The website developer shouldn't be trying to access the scripts, I can't see why and they shouldn't be used with WP in an ideal world, I can't remember the last time I saw a theme use the above scripts

 

[koolpanda]

It's a server thing, you need to speak to the host

This is correct from Faevilangel. That said most hosting providers will kick this back to you. Ok on most hosted services you can override the php.ini. You just add a file in the root of your site, and adjust the parameters from the original ini file (which they will not let you get too). The reason why I think it may be that something has happened to this is, that the original .ini file will not have been touched, or its unlikely. The file permissions probably won't have been touched, or the hosting provider would have checked. So that only leaves what your site requires, and your setup.

Have a little check to see if you have any file called php.ini in the root of your website, or any file with .ini.

Next check to see if wordpress has been updated recently(wordpress is a good cms, but on occasions things can blow up).

Regards

John

 

[Nuno]

I assume you are on shared hosting. If this is the case then you do not have access to these files. This is to do with PHP 5.3 and new sql pdo settings. See if you can drop to 5.2 or you might be able to override the php.ini setings depends on how your hosting is set-up.

Try uploading a file called php.ini to your website root with the following contents

;;extension=pdo_sqlite.so
;;extension=sqlite.so

See if that works.

I assume your Wordpress is functioning correctly? These are really warning errors so you could just keep clearing your error log until Wordpress or PHP fix it.

Thanks Andy,
Vidahost are now saying that it is a PHP 5.2 error and offering to upgrade to 5.3.
This makes me nervous given that you and others see it the other way around.
What do you think?

 

[andygambles]

Thanks Andy,
Vidahost are now saying that it is a PHP 5.2 error and offering to upgrade to 5.3.
This makes me nervous given that you and others see it the other way around.
What do you think?

Get them to try. Switching between the two is trivial (at least it should be for them).

 

[Nuno]

Turns out the server was already 5.3, and that a php.ini file existed with code as suggested by Andy in post #7.

As Andy suggests, I cleared the error logs and will wait for a hopeful fix from PHP and WP.

Alternatives always welcome.

Thanks all.

 

[Faevilangel]

I don't think it's a WP issue but more of a theme issue, I am running WP blogs on 3.6.1 and PHP 5.3 and don't get them errors.

Can you email me the theme name / folder and I will take a look for you

 

[Nuno]

It's a shared hosting account with about 20 WP installs on. The themes are from various sources and include Twenty Thirteen, Suffusion, Weaver2 and 3 and others.
I started a plugin Spreadsheet (to see if there was a common one in all sites - probably Display Widgets) but gave up as the error logs didn't mention any plugins at all.

But please have a look if you want. FTP details?

 

[Faevilangel]

You can narrow it down by website by viewing each individual install error log

there should be an error_log file in the root of each WP install

 

[Nuno]

Yes I did that last night. They nearly all showed this error message, (those that didn't were not WP, piwik for instance).

That was why I thought it had to be a server problem, along with most Google entries saying that.

When the host said "No, not server" I turned here as I didn't know what to do.

They mostly seem to start end May 2013. I only picked it up yesterday as the usage bar in the cpanel turned red.

 

[Faevilangel]

Yes I did that last night. They nearly all showed this error message, (those that didn't were not WP, piwik for instance).

That was why I thought it had to be a server problem, along with most Google entries saying that.

When the host said "No, not server" I turned here as I didn't know what to do.

They mostly seem to start end May 2013. I only picked it up yesterday as the usage bar in the cpanel turned red.

Hmmm if it's on most of the sites, it could be a plugin! Are the sites running the same plugins?

 

[Nuno]

Yes, some plugins are across all sites, and I'll test over the next day or so.
First, most commonly used are:
Ultimate Tinymce*
Yoast SEO
Infinite WP
Contact Form 7
Display widgets

I'll keep posting.

*Does it get on anyone else's zits that he updates every second day?

 

[Nuno]

Update:

Chose one site on the hosting. It was showing the same errors and no others.

Disabled plugins, in groups, and then all plugins.
Errors still showing.
(I'm deleting all content from the error file and refreshing each change to try and pin down the cause)

I change to Twenty-thirteen theme, same errors.
I delete all non WP themes, same errors.
I change to Twenty-twelve and then Twenty-eleven; same errors.

I delete the database in MySQL databases in the CPanel, and then manually delete all files in File Manager.
I install a completely new install with only the default plugins, Askimet and Hello Dolly which I do not activate.
Theme set at Twenty-thirteen. Same errors. Change theme to Twenty-twelve: same errors.

I am now reasonably certain it is a problem on the hosting (or with nasty fairies).

Would this seem about right?
Ta.

 

[koolpanda]

hmmmm fairies...!!!

To be honest it really sounds like something on the server. Hosting companies usually turn loads of stuff off, or do not update software very quickly. So if you have an updated version of wp, there is probably a setting off in the php.ini file. I think I mentioned in a previous post that you can normally override the php.ini file with your own settings. If you ask your hosting company how to do this that will help you. It is normally as easy as making a php.ini in your root folder of the website ("www" or "public_html").

As Andy Gambles said previously;

;;extension=pdo_sqlite.so
;;extension=sqlite.so

These are the settings that maybe need to be set on in the .ini file, in order to get things working.

I sincerely hope this works.

John

 

[Faevilangel]

After Googling the errors, it's a server error, PHP by default wants to be able to find the rwquired files, which it isn't.

http://www.webhostingtalk.com/showthread.php?t=945099