Skip Navigation

[Resolved] Activating the latest versions of Types/Views causes error log to fill up

This thread is resolved. Here is a description of the problem and solution.

Problem:
Client reports many errors in their logs (see thread below for details).

Solution:
The issue related to their use of PHP-FPM, which caused problems with PHP version 5.6, but was resolved by upgrading to PHP 7.

This support ticket is created 6 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Tagged: 

This topic contains 4 replies, has 2 voices.

Last updated by cantonB 6 years, 1 month ago.

Assisted by: Nigel.

Author
Posts
#1109756

When I activate the latest versions of Types/Views, the apache error log fills up with notices like what you see below. Connection reset by peer, etc. As soon as I deactivate Types/Views, the errors stop.

The errors seem to happen even when using non-views related pages, and basic wordpress functions break. (E.g. when using the 'search' field on the list of pages, I would get the public 404 page as a result.) Seems like fundamental AJAX type stuff was busted.

Could this be a memory/resource issue? I've never had this problem with views in the past. I'm nervous to upgrade all my sites to the latest types/views because they will break.

Thanks,
- Canton

[Mon Sep 17 18:52:49.971162 2018] [proxy_fcgi:error] [pid 29267:tid 140620300674816] (104)Connection reset by peer: [client 173.246.205.214:54055] AH01075: Error dispatching request to : , referer: hidden link
[Mon Sep 17 18:53:18.130062 2018] [proxy_fcgi:error] [pid 29039:tid 140620376209152] [client 73.26.152.159:45072] AH01067: Failed to read FastCGI header, referer: hidden link
[Mon Sep 17 18:53:18.130106 2018] [proxy_fcgi:error] [pid 29039:tid 140620376209152] (104)Connection reset by peer: [client 73.26.152.159:45072] AH01075: Error dispatching request to : , referer: hidden link
[Mon Sep 17 18:53:20.736385 2018] [proxy_fcgi:error] [pid 29039:tid 140620384601856] [client 73.26.152.159:45072] AH01067: Failed to read FastCGI header, referer: hidden link
[Mon Sep 17 18:53:20.736429 2018] [proxy_fcgi:error] [pid 29039:tid 140620384601856] (104)Connection reset by peer: [client 73.26.152.159:45072] AH01075: Error dispatching request to : , referer: hidden link
[Mon Sep 17 18:53:29.862929 2018] [proxy_fcgi:error] [pid 29039:tid 140620401387264] [client 73.26.152.159:43450] AH01067: Failed to read FastCGI header, referer: hidden link
[Mon Sep 17 18:53:29.862963 2018] [proxy_fcgi:error] [pid 29039:tid 140620401387264] (104)Connection reset by peer: [client 73.26.152.159:43450] AH01075: Error dispatching request to : , referer: hidden link
[Mon Sep 17 18:53:32.134430 2018] [proxy_fcgi:error] [pid 29039:tid 140620401387264] [client 73.26.152.159:43450] AH01067: Failed to read FastCGI header, referer: hidden link
[Mon Sep 17 18:53:32.134457 2018] [proxy_fcgi:error] [pid 29039:tid 140620401387264] (104)Connection reset by peer: [client 73.26.152.159:43450] AH01075: Error dispatching request to : , referer: hidden link

#1110546

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi Canton

From your debug info your server resources look reasonable (though that can depend on the individual site). We don't have other reports of the same.

Could you provide me with a copy of your site? hidden link

I can install it locally and see if I get the same problem with the logs. If yes we can investigate using that copy.

If no it would seem to be a server issue, but let's see first.

#1111523

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

The only documented requirements—such as the mbstring extension—are listed here: https://toolset.com/toolset-requirements/

I could ask our server team if they can set up a PHP-FPM test environment to see if they can reproduce the problem if it is something you intend to use?

#1116657

Hi there,

Just wanted to report that I fixed this by upgrading from PHP 5.6 to 7.x.

The problem only occurred when BOTH the following were true:

1) Using PHP FPM
2) Using PHP 5.6

What was alarming about this is that previous versions of toolset had no problem with this configuration.

#1116658

My issue is resolved now. Thank you!