[solved] - Traffic Graphs: Cannot get data about interface [2.0.2]
-
I can confirm this as well. If I switch the physical interface it works for awhile but then eventually gets in this same state.
what browser are you using? I can only see this in Google Chrome.
Sorry I thought it was implied. I'm seeing it in Chrome as well. Works fine in IE.
-
I am using Safari 6.0.2 in Mac OS X 10.8.2.
![Screen Shot 2012-12-26 at 10.05.03 PM.png](/public/imported_attachments/1/Screen Shot 2012-12-26 at 10.05.03 PM.png)
![Screen Shot 2012-12-26 at 10.05.03 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2012-12-26 at 10.05.03 PM.png_thumb) -
@slampert: they[developers] might advise us to use IE ;D
@tim.mcmanus: i believe you have no IE in Mac, so i don't know what they will advise you. ;D -
Uh, yeah we'd never in a million years recommend anyone use IE for any purpose whatsoever. A significant portion of us use Chrome, if there were a universal problem we'd have seen it long ago.
JimP testing this earlier, couldn't replicate. I've had all the graphs on 2 different systems going for upwards of a half hour, 0 problems, they're still updating as I'm writing this.
There was only one small change to any of the files related, this here:
https://github.com/bsdperimeter/pfsense/commit/c93b202d75e3df1aecbb25587e1a225a05fbcc9cto fix IE being retarded. Given the scope and relevance of that change, it's improbable that's related. Maybe if you all have stale caches in your browser that Jim and I don't have. You can try going back to the previous revision of that file from here:
https://raw.github.com/bsdperimeter/pfsense/86e1405de40ca1ab1d7ce6726e1181b9ea32f359/usr/local/www/status_graph.phpand see what happens.
Going to have to get some feedback from those who are seeing the issue, since it's not an issue for any of us.
-
You guys have the Widescreen package installed by chance? Wondering if it's breaking stuff as it commonly does since it overwrites base system files.
Chrome is the #1 browser of visitors to this site, 42% of visits in the last month. Thousands of systems have been upgraded to 2.0.2 already. The fact that 3 people are reporting an issue lends to something unusual like a package being the case. There would be a massively long thread by now if it didn't work in Chrome in general.
-
@cmb:
You guys have the Widescreen package installed by chance? Wondering if it's breaking stuff as it commonly does since it overwrites base system files.
Chrome is the #1 browser of visitors to this site, 42% of visits in the last month. Thousands of systems have been upgraded to 2.0.2 already. The fact that 3 people are reporting an issue lends to something unusual like a package being the case. There would be a massively long thread by now if it didn't work in Chrome in general.
Packages: squid, squidguard, lightsquid, imspector, mailreport,sarg and vnstat2 only.
At first i was afraid that it is only my setup that was messed up so i didn't post the problem, but when 2 users confirmed my problem, it was a "sigh of relief" knowing that i didn't do something stupid during the upgrade or on my setup.I will try to revert to the previous revision of the php file (but i don't know how, so i will still search the forum for how to upload that one ???)
Thanks for your attention sir.Update: I tried reverting the php file under /usr/local/www/status_graph.php and same problem happened.
-
Behaviour depends on version of Chrome?
-
I tried the old status_graph.php to no avail, but clearing my cache fixes it for awhile. I turned off all my chrome extensions to rule that out as a cause. I have only two packages installed, mtr-nox11 and nut. My chrome version is 23.0.1271.97 m.
-
I have nmap and pfBlocker installed, but no other packages.
I'm also working on a clean install of 2.0.2, however I did import my previous settings.
I'll try emptying my browser cache to see if it resolve it when it happens again.
EDIT: Just lost one graph after keeping the Dashboard window open for 15 minutes. Emptying the cache fixed the issue.
EDIT AGAIN: Lost another graph, a different one this time and not sure how long it took to fail, but emptying Safari's cache and reloading the Dashboard page resolved the issue.
-
24 hours and counting, 8 live graphs on dashboard, all still working in Chrome. Latest version on Windows in that instance. Works on my Mac too though I haven't had them going on it for as long.
-
When the graph failed I got the following error when I had Safari in developer mode.
Server error 500.
See enclosed screen shot.
EDIT: Added a second image from an hour later.
![Screen Shot 2012-12-28 at 2.16.20 AM.png](/public/imported_attachments/1/Screen Shot 2012-12-28 at 2.16.20 AM.png)
![Screen Shot 2012-12-28 at 2.16.20 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2012-12-28 at 2.16.20 AM.png_thumb)
![Screen Shot 2012-12-28 at 3.11.18 AM.png](/public/imported_attachments/1/Screen Shot 2012-12-28 at 3.11.18 AM.png)
![Screen Shot 2012-12-28 at 3.11.18 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2012-12-28 at 3.11.18 AM.png_thumb) -
is there anything in /tmp/php_errors.txt?
-
-
Another interesting observation: I disabled the caching in Safari and got three 500 errors. However, since caching was disabled in the browser, the graphs never stopped working.
![Screen Shot 2012-12-28 at 2.20.58 PM.png](/public/imported_attachments/1/Screen Shot 2012-12-28 at 2.20.58 PM.png)
![Screen Shot 2012-12-28 at 2.20.58 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2012-12-28 at 2.20.58 PM.png_thumb) -
I remembered one other change, lighttpd was upgraded. Its upgrades have broken things in weird ways in the past, wonder if something in it is somehow causing 500s that only a seemingly very small % of users see. Anyone capable of extracting just the lighttpd files from the 2.0.1-Full-Update tgz and replacing those files, that would be a good test to see if that makes it go away. Just the lighttpd binary alone may be adequate.
-
I checked out the lighttpd.error.log file and found a bunch of these:
2012-12-28 19:32:31: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-28 19:32:31: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-28 19:33:15: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 19:33:15: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 20:02:59: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 5246 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 20:02:59: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em0, closing connection 2012-12-28 20:03:08: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 20:03:08: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 20:18:22: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-28 20:18:22: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-28 20:32:41: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 2050 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 20:32:41: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em0, closing connection 2012-12-28 20:32:41: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 2050 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 20:32:41: (mod_fastcgi.c.3329) response not received, request sent: 819 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em2, closing connection 2012-12-28 20:32:51: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 20:32:51: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 21:02:35: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 29051 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 21:02:35: (mod_fastcgi.c.3329) response not received, request sent: 819 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em1, closing connection 2012-12-28 21:02:45: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 21:02:45: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 21:04:24: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-28 21:04:24: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-28 21:32:06: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 23044 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 21:32:06: (mod_fastcgi.c.3329) response not received, request sent: 819 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em2, closing connection 2012-12-28 21:32:16: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 21:32:16: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 21:49:53: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-28 21:49:53: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-28 22:02:11: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 2029 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 22:02:11: (mod_fastcgi.c.3329) response not received, request sent: 819 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em2, closing connection 2012-12-28 22:02:11: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 2029 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 22:02:11: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em3, closing connection 2012-12-28 22:02:21: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 22:02:21: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 22:31:52: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 22:31:52: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 22:35:44: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-28 22:35:44: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-28 23:01:36: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 61905 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 23:01:36: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em0, closing connection 2012-12-28 23:01:43: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-28 23:01:43: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-28 23:21:13: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-28 23:21:13: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-28 23:31:30: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 58154 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 23:31:30: (mod_fastcgi.c.3282) child exited, pid: 58154 status: 0 2012-12-28 23:31:30: (mod_fastcgi.c.3329) response not received, request sent: 819 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em1, closing connection 2012-12-28 23:31:30: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 19885 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-28 23:31:30: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em3, closing connection 2012-12-29 00:01:23: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-29 00:01:23: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-29 00:06:54: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 61895 socket: unix:/tmp/php-fastcgi.socket-0 2012-12-29 00:06:54: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-0 for /ifstats.php?if=em0, closing connection 2012-12-29 00:07:04: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-29 00:07:04: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-29 00:31:06: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 31569 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-29 00:31:06: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em0, closing connection 2012-12-29 00:31:06: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 31569 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-29 00:31:06: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em3, closing connection 2012-12-29 00:31:16: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-29 00:31:16: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-29 00:52:55: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-29 00:52:55: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2 2012-12-29 01:00:59: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-29 01:00:59: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-29 09:50:06: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 21039 socket: unix:/tmp/php-fastcgi.socket-1 2012-12-29 09:50:06: (mod_fastcgi.c.3329) response not received, request sent: 819 on socket: unix:/tmp/php-fastcgi.socket-1 for /ifstats.php?if=em1, closing connection 2012-12-29 09:50:16: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-1 2012-12-29 09:50:16: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-29 10:11:45: (mod_fastcgi.c.2543) unexpected end-of-file (perhaps the fastcgi process died): pid: 23833 socket: unix:/tmp/php-fastcgi.socket-0 2012-12-29 10:11:45: (mod_fastcgi.c.3329) response not received, request sent: 817 on socket: unix:/tmp/php-fastcgi.socket-0 for /ifstats.php?if=em3, closing connection 2012-12-29 10:11:55: (mod_fastcgi.c.1732) connect failed: Connection refused on unix:/tmp/php-fastcgi.socket-0 2012-12-29 10:11:55: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 2
Looks like fastcgi has issues.
I'll see if I can install the lighttpd version from 2.0.1 this weekend.
-
Swapped out lighttpd with the 2.0.1-RELEASE one. The web service stopped with an error. Again fastcgi related.
2012-12-29 12:45:26: (mod_fastcgi.c.1732) connect failed: No such file or directory on unix:/tmp/php-fastcgi.socket-1 2012-12-29 12:45:26: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 0 load: 1 2012-12-29 12:45:26: (mod_fastcgi.c.1732) connect failed: No such file or directory on unix:/tmp/php-fastcgi.socket-0 2012-12-29 12:45:26: (mod_fastcgi.c.3002) backend died; we'll disable it for 1 seconds and send the request to another backend instead: reconnects: 1 load: 1 2012-12-29 12:45:26: (mod_fastcgi.c.3570) all handlers for /ifstats.php?if=em0 on .php are down. 2012-12-29 12:45:26: (server.c.1546) server stopped by UID = 0 PID = 1
System logs also noted:
Dec 29 13:11:11 pfsense php: : The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '1', the output was '/libexec/ld-elf.so.1: Shared object "libpcre.so.0" not found, required by "lighttpd"'
I tried swapping out just mod_fastcgi.so and got the following error:
Dec 29 13:16:00 pfsense php: : The command '/usr/local/sbin/lighttpd -f /var/etc/lighty-webConfigurator.conf' returned exit code '255', the output was '2012-12-29 13:16:00: (plugin.c.421) plugin-version doesn't match lighttpd-version for fastcgi 2012-12-29 13:16:00: (server.c.926) Initialization of plugins failed. Going down.'
I reverted back to the 2.0.2 build version of fasttpd for the time being.
-
Just another confirmation, I have it as well on Chrome.
Upgraded to 2.0.2 yesterday from 2.0.1.
-
Is everyone seeing this also seeing fastcgi dying in /var/log/lighttpd.error.log as tim.mcmanus posted?
-
Yes, I get the exact same in my error logs.