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

    WebGUI trouble since 2.2.3

    Scheduled Pinned Locked Moved webGUI
    9 Posts 6 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.
    • F
      fraglord
      last edited by

      Today I upgraded to pfsense 2.2.3. Now the weGUI gives me a headache: only after reboot it is available for some minutes but then stops working. Restarting it from shell also has no effect. The system itself is up and running but just without webGUI. Any clue what happened?

      pfSense 2.4.0 (amd64) running on IGEL H710C | 1G RAM | 8G SSD | INTEL PRO/1000 PT Dual NIC

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

        Have you also tried console menu option 16 to restart PHP-FPM?
        That might get things back for you - then of course the root cause still needs to be found.
        bandwidthd is known to cause this problem on some systems, regardless of (recent) pfSense version. Why that is so has not been tracked down.

        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
        • F
          fraglord
          last edited by

          Thanks, that allows me to access thr webinterface again.
          I found something in the system log that might be related to the problem:

          Jun 26 22:28:24	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 19
          Jun 26 22:28:24	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 19
          Jun 26 22:28:26	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 27
          Jun 26 22:28:26	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 27
          Jun 26 22:28:26	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 25
          Jun 26 22:28:26	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 25
          Jun 26 22:28:27	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 31
          Jun 26 22:28:27	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 31
          Jun 26 22:28:28	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 29
          Jun 26 22:28:28	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 29
          Jun 26 22:28:29	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 33
          Jun 26 22:28:29	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 33
          Jun 26 22:28:29	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 20
          Jun 26 22:28:29	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 20
          Jun 26 22:28:31	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 22
          Jun 26 22:28:31	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 22
          Jun 26 22:28:31	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 24
          Jun 26 22:28:31	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 24
          Jun 26 22:28:32	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 28
          Jun 26 22:28:32	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 28
          Jun 26 22:28:32	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 32
          Jun 26 22:28:32	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 32
          Jun 26 22:28:34	lighttpd[22852]: (network_writev.c.107) writev failed: Operation not permitted 35
          Jun 26 22:28:34	lighttpd[22852]: (connections.c.619) connection closed: write failed on fd 35
          

          pfSense 2.4.0 (amd64) running on IGEL H710C | 1G RAM | 8G SSD | INTEL PRO/1000 PT Dual NIC

          1 Reply Last reply Reply Quote 0
          • S
            Supermule Banned
            last edited by

            Looks like the built in webserver is somehow fucked.

            1 Reply Last reply Reply Quote 0
            • F
              fraglord
              last edited by

              How can i further troubleshoot this?

              pfSense 2.4.0 (amd64) running on IGEL H710C | 1G RAM | 8G SSD | INTEL PRO/1000 PT Dual NIC

              1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan
                last edited by

                Try the solution that always works:
                Backup confi
                Install on totally cleaned drive (that is a re-install - not an upgrade)
                Put backed up config back in.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

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

                  Are you running a full install or embedded?

                  1 Reply Last reply Reply Quote 0
                  • V
                    vbentley
                    last edited by

                    @Gertjan:

                    Try the solution that always works:
                    Backup confi
                    Install on totally cleaned drive (that is a re-install - not an upgrade)
                    Put backed up config back in.

                    That used to be a dependable solution up to 2.1.5 but not any more for me.
                    I have just done a reinstall-restore from 2.2.4 to 2.2.4 and the WebGUI is OK for up to 1 day, sometimes only a few hours.

                    Trademark Attribution and Credit
                    pfSense® and pfSense Certified® are registered trademarks of Electric Sheep Fencing, LLC in the United States and other countries.

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

                      @vbentley:

                      That used to be a dependable solution up to 2.1.5 but not any more for me.
                      I have just done a reinstall-restore from 2.2.4 to 2.2.4 and the WebGUI is OK for up to 1 day, sometimes only a few hours.

                      What packages do you have installed?

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