Bug #6520
closed
Time out when trying to look at interfaces_assign.php
0%
Description
Hello,
Since the update in 2.3, I get a time out when trying to reach interfaces_assign.php. Then the whole web interface is down and I have to reboot it.
I have something like 150 interfaces on the PfSense.
Updated by Axel Duez over 8 years ago
Here are the logs :
Jun 22 15:21:51 fw2.ds nginx: 2016/06/22 15:21:51 [error] 21284#0: *121 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 172.16.0.28, server: , request: "GET /interfaces_assign.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "172.16.0.3", referrer: "https://172.16.0.3/status_dhcp_leases.php"
Jun 22 15:21:51 fw2.ds nginx: 172.16.0.28 - - [22/Jun/2016:15:21:51 +0200] "GET /interfaces_assign.php HTTP/1.1" 504 578 "https://172.16.0.3/status_dhcp_leases.php" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"
Jun 22 15:21:51 fw2.ds nginx: 172.16.0.28 - - [22/Jun/2016:15:21:51 +0200] "GET /interfaces_assign.php HTTP/1.1" 504 578 "https://172.16.0.3/status_dhcp_leases.php" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36"
Updated by Gareth Hay over 8 years ago
We have been doing some testing on one of our sites.
Under 2.2.4 no issue with 100 vlans, under 2.3.1-RELEASE-p5 at 40 vlans it takes around 27 seconds to open the page on our boxes and it is noticibly slower as you add vlans one by one.
At 100 vlans we get a 504 Gateway time out.
nginx: 2016/06/23 12:08:23 [error] 17180#0: *134 upstream timed out (60: Operation timed out) while reading response header from upstream, client: X.X.X.X, server: , request: "GET /interfaces_assign.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "X.X.X.X", referrer: "https://X.X.X.X/"
Looks like this is covered in #6400
Updated by