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

    500 - Internal Server Error

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 2 Posters 2.1k Views
    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.
    • _
      _igor_
      last edited by

      Due to problems with custom PPPOE-reset-time i want to disable that, but clicking "save" results in the mentioned server error.

      2.0-RC2 (amd64) built on Tue May 24 04:45:10 EDT 2011 full install.

      Anyone else can confirm that?

      1 Reply Last reply Reply Quote 0
      • R
        rubenc
        last edited by

        Use tools like ktrace or truss, attach to running /usr/local/bin/php processes (or tweak the config so lighttpd only spawns 1 so you don't have to attach to all of them) and see what happens when you click "Save". Attach to them just before clicking :)

        Hardware: SC1935 | WAN: em (PCIe) | LAN: bge (onboard) | RAM: 2Gb
        2.0-RC2-IPv6 (i386)
        built on Sat May 21 21:38:32 EDT 2011

        1 Reply Last reply Reply Quote 0
        • _
          _igor_
          last edited by

          sorry, i don't understand what you mean.

          But seems that this error 500 is on several other places too:

          Routing - Gateways: Dashboard shows WAN as offline, so i opened the gateway for WAN, clicked "save" and had the same error. This all came with update to the mentioned snap. Before there was no error!

          1 Reply Last reply Reply Quote 0
          • _
            _igor_
            last edited by

            hehe, man truss will be your friend… :)

            I did that trace first with save gateway, then i switched to Interfaces - wan and did the same here.

            I did a truss -fae ...

            Hope that helps

            Update: Todays update of pfSense solved the problem. Now all seems to work again as expected. Thanks for your help!

            trace.txt

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.