How To Troubleshoot PHP Errors, php errors in your php error log

[AITpro Admin]

It is not necessary to clear the log since BPS Pro will automatically zip and email you all log files once they reach 500KB.  Just clicking the Reset last time in DB button is all that is necessary.  I believe if you clear the log file and then click the Reset button then you have performed 2 Form actions so you will need to click the Reset button twice if you do that to clear both Form actions.

[AITpro Admin]

Correction:  I phrased that explanation wrong above.  If you clear the log file then you are performing an additional Form action so that action would additionally need to be reset.

[AITpro Admin]

@ rphrus – Your question has been copied into this Forum Topic so that you will get notifications.  The BuddyPress Comment feature does not have notification capability.

There’s no problem by deleting the quarantine file isn’t it? Won’t break the site?

[AITpro Admin]

The BuddyPress Activity Stream Comment feature has been disabled.

BuddyPress does not notify us if you post a comment update so we usually will not see these for several days. You will also not receive a notification that we have replied back to you.

Files in Quarantine are either a malicious hacker file that has been moved to the quarantine folder or a copy of website file that has been sent to Quarantine. Use the View File option in Quarantine to decide whether to Restore or Delete the file in Quarantine.

AutoRestore/Quarantine Guide
http://forum.ait-pro.com/forums/topic/autorestore-quarantine-guide-read-me-first/

[Andre]

Hi,

I am trying to use a plugin, that is probably only used in the admin panel, called: participants database

I tried to whitelist as follows:

/participants-database/js/(.*).js, /participants-database/classes/FormElement.class.php

and before with regex for the classes folder like this:

/participants-database/js/(.*).js, /participants-database/classes/(.*).php

which also didnt show any effect.

But constantly get this:

[23-Aug-2013 11:16:42 UTC] participants-database plugin activated
[23-Aug-2013 11:18:46 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:18:46 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:18:46 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:23:26 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:23:26 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:23:26 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:25:46 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:25:46 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:25:46 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:26:35 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:26:35 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013
[23-Aug-2013 11:26:35 UTC] FormElement::format_date: timestamp couldn't be formatted: August 23, 2013

What now?

Plugin can be downloaded here: http: //wordpress.org/plugins/participants-database/

[AITpro Admin]

Your comment has been moved to a relevant topic.

The Plugin Firewall and the PHP Error log are not related at all.  The Plugin Firewall handles issues at the HTTP level.  The PHP Error Log logs issues with php coding errors or mistakes in other plugins.  Please contact the Participants Database plugin author and send him/her these php errors so that he/she can fix whatever coding issues/problems are occuring in that plugin.  BPS only logs these php errors.  BPS does not create them or have anything to do with them besides logging php problems.

[Andre]

Hi,

I had a php error on wordpress-seo by yoast. I already assumed, that it will go away when updating, but stupid me added the file to the firewall…

But then BPS pro created a php error after adding it to firewall and also after taking it out again, please have a short look:

[23-Sep-2013 13:52:11 UTC] PHP Fatal error:  Cannot use object of type WP_Error as array in /var/www/virtual/mydomain.com/htdocs/wp-content/plugins/wordpress-seo/admin/ajax.php on line 81
[25-Sep-2013 10:53:18 UTC] PHP Warning:  copy(/var/www/virtual/mydomain.com/htdocs/wp-content/bps-backup/autorestore/wp-content/plugins/bulletproof-security/admin/htaccess/plugins.htaccess): failed to open stream: No such file or directory in /var/www/virtual/mydomain.com/htdocs/wp-content/plugins/bulletproof-security/admin/options.php on line 1948
[25-Sep-2013 10:53:18 UTC] PHP Warning:  copy(/var/www/virtual/mydomain.com/htdocs/wp-content/bps-backup/autorestore/wp-content/plugins/bulletproof-security/admin/htaccess/plugins-htaccess-master.txt): failed to open stream: No such file or directory in /var/www/virtual/mydomain.com/htdocs/wp-content/plugins/bulletproof-security/admin/options.php on line 1949
[25-Sep-2013 10:53:23 UTC] PHP Warning:  copy(/var/www/virtual/mydomain.com/htdocs/wp-content/bps-backup/autorestore/wp-content/plugins/bulletproof-security/admin/htaccess/plugins.htaccess): failed to open stream: No such file or directory in /var/www/virtual/mydomain.com/htdocs/wp-content/plugins/bulletproof-security/admin/options.php on line 326
[25-Sep-2013 10:54:31 UTC] PHP Warning:  copy(/var/www/virtual/mydomain.com/htdocs/wp-content/bps-backup/autorestore/wp-content/plugins/bulletproof-security/admin/htaccess/plugins.htaccess): failed to open stream: No such file or directory in /var/www/virtual/mydomain.com/htdocs/wp-content/plugins/bulletproof-security/admin/options.php on line 1948
[25-Sep-2013 10:54:31 UTC] PHP Warning:  copy(/var/www/virtual/mydomain.com/htdocs/wp-content/bps-backup/autorestore/wp-content/plugins/bulletproof-security/admin/htaccess/plugins-htaccess-master.txt): failed to open stream: No such file or directory in /var/www/virtual/mydomain.com/htdocs/wp-content/plugins/bulletproof-security/admin/options.php on line 1949
[25-Sep-2013 10:54:36 UTC] PHP Warning:  copy(/var/www/virtual/mydomain.com/htdocs/wp-content/bps-backup/autorestore/wp-content/plugins/bulletproof-security/admin/htaccess/plugins.htaccess): failed to open stream: No such file or directory in /var/www/virtual/mydomain.com/htdocs/wp-content/plugins/bulletproof-security/admin/options.php on line 326

[AITpro Admin]

Are the php errors still occurring or did they only occur when you were making changes to the Plugin Firewall?  On some Servers these php errors will occur due to Server configurations on some Hosts.  If the php errors are NOT continuing to happen then this is not a problem and you can ignore these php errors.

[AITpro Admin]

FYI – There is a known issue with the OpenGraph feature/option with the Yoast SEO plugin.  If you are using the Yoast OpenGraph feature then see the link below for the solution.

http://www.ait-pro.com/aitpro-blog/2252/bulletproof-security-plugin-support/checking-plugin-compatibility-with-bps-plugin-testing-to-do-list/#yoast-seo

[Andre]

Hi, the occurance happened when I saw, that the plugin needs an update.
First row in error log.
Then I installed the update, reset it and then I added it to the firewall. Then the 3rd to 4th row was logged, then I took the plugin code out of firewall again and the rest was logged.

No, it is not coming back till now.

[AITpro Admin]

@ Andre – then you can disregard the php error.  There are a lot of things happening simultaneously and sometimes some things happen out of order or if your Host Server does things a little differently then other Host Servers then yes you will see one time php errors during certain actions, but they will not occur outside of performing those particular actions.

[Andre]

thank you man, for giving me peace.
Thumbs up

[AITpro Admin]

This issue has already been taken care of in BPS Pro 7.1 so these php errors will not be displayed anymore.  And no, we do not have an official BPS Pro 7.1 release date.  We no longer announce BPS Pro version release dates ahead of time.

[AITpro Admin]

Topic post manually moved to this relevant topic:

I constantly get the errro

WordPress database error MySQL server has gone away for query SELECT meta_value FROM wp_sitemeta WHERE meta_key = 'avhfdas-spam_filter' AND site_id = 1 made by require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), include_once('/plugins/comment-spam-pack/avh-fdas-spam-filter.php'), AVH_SpamFilter::serve, AVH_SpamFilter->__construct, get_site_option

I had contacted hostgator and they have installed a monitoring script and found said this:

The reason for these intermittent mysql errors is due to your server running out of memory. When this happens your server has to kill off processes, and mysqld is being killed off. During this time the site will throw a database connection error. At around 2:02 on the 7th i noticed your memory levels drop very low, the cause of this was due to many wp-cron.php scripts being ran, i have shown these below. Each one of these was using up around 70-90M of memory, which caused the server to start killing off processes. I recommend moving up a VPS level, reducing memory usage of your PHP scripts or disabling wp-cron. If i can help you with anything else, just let me know. Thank You.

=================================================================================== Oct 7 13:43:52 vps954 kernel: [5310153.243056] OOM killed process php (pid=2432, ve=515272) exited, free=213759. Oct 7 13:44:22 vps954 kernel: [5310183.788914] OOM killed process php (pid=4669, ve=515272) exited, free=190327. Oct 7 13:44:23 vps954 kernel: [5310184.528944] OOM killed process php (pid=4849, ve=515272) exited, free=162963. Oct 7 13:44:23 vps954 kernel: [5310184.799796] OOM killed process httpd (pid=62975, ve=515272) exited, free=226946. Oct 7 13:45:15 vps954 kernel: [5310236.553822] OOM killed process php (pid=5530, ve=515272) exited, free=200686. Oct 7 14:03:35 vps954 kernel: [5311336.706332] OOM killed process php (pid=51522, ve=515272) exited, free=265636. Oct 7 14:03:36 vps954 kernel: [5311337.396235] OOM killed process php (pid=48480, ve=515272) exited, free=280868. Oct 7 14:05:24 vps954 kernel: [5311445.396570] OOM killed process php (pid=58674, ve=515272) exited, free=165651. Oct 7 14:05:24 vps954 kernel: [5311446.091041] OOM killed process php (pid=56041, ve=515272) exited, free=156973. Oct 7 14:05:25 vps954 kernel: [5311446.471845] OOM killed process php (pid=58751, ve=515272) exited, free=196434. Oct 7 14:05:34 vps954 kernel: [5311455.640614] OOM killed process php (pid=55896, ve=515272) exited, free=243212. Oct 7 14:05:35 vps954 kernel: [5311456.214704] OOM killed process php (pid=58514, ve=515272) exited, free=263214. Oct 7 14:05:35 vps954 kernel: [5311456.763335] OOM killed process php (pid=59318, ve=515272) exited, free=271689. Oct 7 14:05:36 vps954 kernel: [5311457.627225] OOM killed process php (pid=59364, ve=515272) exited, free=244108. Oct 7 14:06:08 vps954 kernel: [5311489.984157] OOM killed process php (pid=61502, ve=515272) exited, free=200204. Oct 7 14:09:38 vps954 kernel: [5311699.760274] OOM killed process php (pid=5035, ve=515272) exited, free=207079. Oct 7 14:13:14 vps954 kernel: [5311916.028748] OOM killed process php (pid=20523, ve=515272) exited, free=127771. Oct 7 14:13:15 vps954 kernel: [5311916.351743] OOM killed process php (pid=23075, ve=515272) exited, free=117603. Oct 7 15:57:35 vps954 kernel: [5318177.031039] OOM killed process mysqld (pid=43109, ve=515272) exited, free=276614. Oct 7 15:58:24 vps954 kernel: [5318225.384241] OOM killed process php (pid=30775, ve=515272) exited, free=221903. Oct 8 01:32:18 vps954 kernel: [5352659.320104] OOM killed process php (pid=26734, ve=515272) exited, free=786929. =================================================================================== root@web [~]# sys-snap 10/7 2:02 PM | grep /usr/bin/php maginabl 8602 0.0 3.2 209M 209M 74M S 0 0.83 14:02 0 0 /usr/bin/php /home/maginabl/public_html/index.php missionw 8608 0.0 3.3 223M 223M 77M S 0 0.89 14:02 0 0 /usr/bin/php /home/missionw/public_html/index.php caribbea 8624 0.0 1.0 157M 157M 23M R 0 0.2 14:02 0 8K /usr/bin/php /home/caribbea/public_html/index.php missionw 8606 0.0 3.0 215M 215M 69M S 0 0.73 14:02 0 4K /usr/bin/php /home/missionw/public_html/index.php missionw 8614 0.0 3.5 225M 225M 79M S 0 0.91 14:02 0 0 /usr/bin/php /home/missionw/public_html/wp-cron.php maginabl 8622 0.0 3.2 207M 207M 73M R 0 0.78 14:02 0 0 /usr/bin/php /home/maginabl/public_html/wp-cron.php maginabl 8618 0.0 3.2 210M 210M 74M S 0 0.84 14:02 0 4K /usr/bin/php /home/maginabl/public_html/wp-signup.php maginabl 8604 0.0 3.4 212M 212M 77M S 0 0.84 14:02 0 0 /usr/bin/php /home/maginabl/public_html/wp-cron.php missionw 8612 0.0 3.1 216M 216M 70M S 0 0.8 14:02 0 0 /usr/bin/php /home/missionw/public_html/wp-cron.php sdatt 8620 0.0 3.8 222M 222M 88M R 0 0.87 14:02 0 8K /usr/bin/php /home/sdatt/public_html/index.php

So the cron they mentioned is the bullet proof cron that cause the server to slow down?

[AITpro Admin]

I believe your Host’s assessment is correct that you need to upgrade to a VPS Server.  Here are the reasons that I believe they are making the correct assessment.

You have chosen a Network/Multisite site architecture which is of course fine to do, but you also have to be aware that by doing this you are demanding a lot more resources from 1 central WordPress database.  We actually considered a Network/Multisite architecture for all of our websites, but found conclusively that by distributing resource load / MySQL DB requests across separate websites and MySQL databases this would ensure that we would not run into premature growth problems.  If we had decided to go with a Network/Multisite architecture then one of the necessary requirements for this would be to get Dedicated or VPS hosting.  Our current architecture with having separate single sites works even in a Shared Hosting environment since the resource load is spread out across many separate sites/MySQL Databases for each site.

For what you are doing with your Network/Multisite setup you cannot choose a single site architecture and the best option for you to do would be to upgrade to a VPS or Dedicated Server that will be able to handle higher resource loads/requests on a single centralized WordPress database.

The AutoRestore Cron does use a bit of resources (I believe it is .01 resource usage), but it is not MySQL based.  The file check that occurs does not make extensive MySQL database queries/requests and instead is handled primarily using directory iterators.

[Author]

Posts