Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    WUI 2.3 - Crash Report

    Scheduled Pinned Locked Moved
    General pfSense Questions
    4
    5
    1.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      cremesk
      last edited by

      Hi,

      i become this Crash Report on my Dashboard..

      Crash report begins.  Anonymous machine information:

amd64
10.3-RELEASE
FreeBSD 10.3-RELEASE #13 eac8329(RELENG_2_3): Wed Apr  6 06:20:01 CDT 2016     root@ce23-amd64-builder:/builder/pfsense/tmp/obj/builder/pfsense/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[11-Apr-2016 10:46:51 Etc/UTC] PHP Stack trace:
[11-Apr-2016 10:46:51 Etc/UTC] PHP   1\. {main}() /usr/local/www/ifstats.php:0
[11-Apr-2016 10:46:51 Etc/UTC] PHP   2\. require_once() /usr/local/www/ifstats.php:63
[11-Apr-2016 10:46:51 Etc/UTC] PHP   3\. get_configured_interface_with_descr() /usr/local/www/guiconfig.inc:254

      Sven

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        Do you know what you do to cause this?
        Does it happen when you go to Status->Interfaces?
        Or do you have the Interface Stats widget enabled on the dashboard?

        What interfaces do you have? Anything unusual?

        Unfortunately there is a traceback but it does not report the actual PHP error, so it is hard to know exactly what PHP thinks is the problem.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • C
          cremesk
          last edited by

          @phil.davis:

          Do you know what you do to cause this?
          Does it happen when you go to Status->Interfaces?
          Or do you have the Interface Stats widget enabled on the dashboard?

          What interfaces do you have? Anything unusual?

          Unfortunately there is a traceback but it does not report the actual PHP error, so it is hard to know exactly what PHP thinks is the problem.

          I don't know whats the problem is.. All Interface Works and i think he looks good..
          Staus Widged and Interface Stats are enabled on my Dashboard.

          Status Interfaces:

          
    StatusInterfaces

WAN Interface (wan, vtnet0)

Status
    up
MAC Address
    66:37:61:31:65:37
IPv4 Address
    192.168.111.2
Subnet mask IPv4
    255.255.255.240
Gateway IPv4
    192.168.111.1
IPv6 Link Local
    fe80::6437:61ff:fe31:6537%vtnet0
ISP DNS servers
    10.254.255.30
    10.254.255.31
MTU
    1500
Media
    10Gbase-T <full-duplex>In/out packets
    611723/742952
In/out packets (pass)
    611723/742952
In/out packets (block)
    1046/1
In/out errors
    0/0
Collisions
    0	

LAN Interface (lan, vtnet1)

Status
    up
MAC Address
    32:66:62:64:39:66
IPv4 Address
    192.168.3.254
Subnet mask IPv4
    255.255.255.0
IPv6 Link Local
    fe80::3066:62ff:fe64:3966%vtnet1
MTU
    1500
Media
    10Gbase-T <full-duplex>In/out packets
    270746/292190
In/out packets (pass)
    270746/292190
In/out packets (block)
    0/0
In/out errors
    0/0
Collisions
    0	

DMZ Interface (opt1, vtnet2)

Status
    up
MAC Address
    66:39:33:64:35:65
IPv4 Address
    172.32.200.254
Subnet mask IPv4
    255.255.255.0
IPv6 Link Local
    fe80::6439:33ff:fe64:3565%vtnet2
MTU
    1500
Media
    10Gbase-T <full-duplex>In/out packets
    296738/314990
In/out packets (pass)
    296738/314990
In/out packets (block)
    65/1
In/out errors
    0/0
Collisions
    0	

EXT Interface (opt2, vtnet3)

Status
    up
MAC Address
    36:66:64:62:36:33
IPv4 Address
    10.0.0.1
Subnet mask IPv4
    255.255.0.0
IPv6 Link Local
    fe80::3466:64ff:fe62:3633%vtnet3
MTU
    1500
Media
    10Gbase-T <full-duplex>In/out packets
    0/19723
In/out packets (pass)
    0/19723
In/out packets (block)
    0/0
In/out errors
    0/0
Collisions
    0	

MGMT Interface (opt3, vtnet4)

Status
    up
MAC Address
    32:63:66:66:61:32
IPv4 Address
    10.254.255.254
Subnet mask IPv4
    255.255.255.0
IPv6 Link Local
    fe80::3063:66ff:fe66:6132%vtnet4
MTU
    1500
Media
    10Gbase-T <full-duplex>In/out packets
    475574/697763
In/out packets (pass)
    475574/697763
In/out packets (block)
    130/0
In/out errors
    0/0
Collisions
    0	

OVPNHOME Interface (opt4, ovpns1)

Status
    up
MAC Address
    00:00:00:00:00:00 - Xerox
IPv4 Address
    172.16.0.1
Subnet mask IPv4
    255.255.0.0
IPv6 Link Local
    fe80::9c59:a00:4036:17d9%ovpns1
MTU
    1500
In/out packets
    155/219
In/out packets (pass)
    155/219
In/out packets (block)
    0/0
In/out errors
    0/0
Collisions
    0	

WAN2 Interface (opt5, vtnet5)

Status
    up
MAC Address
    32:61:39:32:66:66
IPv4 Address
    192.168.112.2
Subnet mask IPv4
    255.255.255.240
Gateway IPv4
    192.168.112.1
IPv6 Link Local
    fe80::3061:39ff:fe32:6666%vtnet5
MTU
    1500
Media
    10Gbase-T <full-duplex>In/out packets
    47188/55454
In/out packets (pass)
    47188/55454
In/out packets (block)
    353/0
In/out errors
    0/0
Collisions
    0	

OVPNADMIN Interface (opt7, ovpns2)

Status
    up
MAC Address
    00:00:00:00:00:00 - Xerox
IPv4 Address
    192.168.253.1
Subnet mask IPv4
    255.255.255.0
IPv6 Link Local
    fe80::9c59:a00:4036:17d9%ovpns2
MTU
    1500
In/out packets
    472946/393700
In/out packets (pass)
    472946/393700
In/out packets (block)
    122/187
In/out errors
    0/0
Collisions
    0	

INFRA Interface (opt8, vtnet6)

Status
    up
MAC Address
    66:37:34:39:36:33
IPv4 Address
    10.253.255.2
Subnet mask IPv4
    255.255.255.0
IPv6 Link Local
    fe80::6437:34ff:fe39:3633%vtnet6
MTU
    1500
Media
    10Gbase-T <full-duplex>In/out packets
    0/19724
In/out packets (pass)
    0/19724
In/out packets (block)
    0/0
In/out errors
    0/0
Collisions
    0	

[color]Using dial-on-demand will bring the connection up again if any packet triggers it. To substantiate this point: disconnecting manually will not prevent dial-on-demand from making connections to the outside! Don't use dial-on-demand if the line is to be kept disconnected.[/color]</full-duplex></full-duplex></full-duplex></full-duplex></full-duplex></full-duplex></full-duplex>

          interface_status_stats.png
          interface_status_stats.png_thumb

          1 Reply Last reply Reply Quote 0
          • J
            JorgeOliveira
            last edited by

            I think the issue you're seeing is the exact same as reported here:
            https://forum.pfsense.org/index.php?topic=107578.msg599597

            My views have absolutely no warranty express or implied. Always do your own research.

            1 Reply Last reply Reply Quote 0
            • G
              grandrivers
              last edited by

              sorry lost track of that forum post modded code and update list of errors

              pfsense 2.4 super micro A1SRM-2558F
              C2558 8gig ECC  60gig SSD
              tripple Wan dual pppoe

              1 Reply Last reply Reply Quote 0
              • First post
                Last post