Project

General

Profile

Bug #8125

gateway 502 errors proposed fix for high ram systems

Added by Chris Collins 12 months ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Start date:
11/24/2017
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

I noticed lately multiple forum threads on gateway 502 errors, when this occurs it is because nginx cannot talk to FPM.

If this is considered a bug I also posted a patch which I think will help resolve this on systems with more than a gig of ram, my patch doesnt change anything for systems with under 250 meg of ram, and only slightly changes things for systems between 250 meg and 1 gig of ram.

Information here

https://forum.pfsense.org/index.php?topic=110515.msg766964#msg766964

History

#1 Updated by Jim Thompson 12 months ago

  • Category set to Web Interface
  • Assignee set to Steve Beaver
  • Target version changed from Future to 2.4.3

I’m in favor of incorporating this. Assigned to Beaver for evaluation. Target set to 2.4.3

Thanks, Chris.

#2 Updated by Martin Wasley 12 months ago

Chris had asked me to do a commit for this, but I was a bit slack in doing so, now done. PR 3881

#3 Updated by Jim Pingle 10 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

PR https://github.com/pfsense/pfsense/pull/3881 was merged a few weeks ago

#4 Updated by Jim Pingle 10 months ago

Could be a potential problem with the solution in the PR, see #8249

#5 Updated by Jim Pingle 9 months ago

  • Status changed from Feedback to Resolved

Parameters are changing with RAM size as expected, seems to work OK.

Also available in: Atom PDF