Announcement

Collapse
No announcement yet.

Web Monitor stopping network traffic

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Web Monitor stopping network traffic

    We have a problem that has occurred 3 times in the past 3 days. Our network (web) traffic either completely comes to a stop or is just crawling. Nobody in our office can access any websites. Looking at our bandwidth, it's flowing in/out at about 5-10 kB/s. If I turn of web monitor, all web traffic starts flowing normally -- our bandwidth is flowing at like 1300 kB/s. If i try to turn web monitor back on I get an error, "Warning. Unable to start a pulse. Unexpected state: DEAD." If we reboot our Untangle box, everything works fine for about a day and then the same thing happens.

    We are using Untangle v14.2.0. Hardware is Intel(R) Celeron(R) CPU J1900 @ 1.99GHz, 4.15 GB Memory, 106.42 GB Disk.

    Memory usage is at 38.8% used, Swap is 0.2% used, Disk is 14.3% used, CPU load 0.22 (low).

    Any help understanding how to fix this would be greatly appreciated.

    Click image for larger version

Name:	Screenshot 2019-07-26 11.09.15.png
Views:	1
Size:	209.9 KB
ID:	386167

    Click image for larger version

Name:	Screenshot 2019-07-26 11.39.31.png
Views:	1
Size:	207.0 KB
ID:	386169
    Attached Files

  • #2
    I think this is the same issue I encountered with Web Filter (Web Monitor is the same module, without the ability to block). It's a known issue which Untangle is working to fix (I've been told the fix is due next week some time).
    If you have SSH or direct CLI access to the box, you can do a uvm restart (/etc/init.d/untangle-vm restart) to get it working again without rebooting the whole box which takes about a minute or so instead of 3-4 minutes.
    The recommendation is to disable Web Filter or Web Monitor until this is fixed, though Web Filter users may not want to do that. I'm just going to restart the uvm once a day at my Web Filter sites, and disable the Web Monitor at the rest.

    Comment


    • #3
      Web filter has been down for me too. Unable to find pulse: dead.

      Comment


      • #4
        Same for me

        I disabled Web Monitor, but problem still exists. Then I removed Web Monitor and still the same
        How to fix it?
        Last edited by skrzat; 07-29-2019, 08:06 AM.

        Comment


        • #5
          You have to restart the server, or the UVM service to get Untangle back online again. Removing webfilter / monitor just keeps it from dying.
          Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
          NexgenAppliances.com
          Phone: 866-794-8879 x201
          Email: [email protected]

          Comment


          • #6
            I just turned web filter off. Traffic is fine.

            Comment


            • #7
              Originally posted by sky-knight View Post
              You have to restart the server, or the UVM service to get Untangle back online again. Removing webfilter / monitor just keeps it from dying.
              Still the same
              I had to restart Untangle, because restarting UVM service has infinite loop

              EDIT:
              Finally it works
              Last edited by skrzat; 07-29-2019, 01:43 PM.

              Comment


              • #8
                Same problem...just wanted to get updates on this thread.

                Also, this is only happening on a small subset of untangle boxes I have...and they are all the oldest hardware..
                Last edited by andrew50; 08-09-2019, 07:04 AM.

                Comment


                • #9
                  It's a bug in the new categorization engine, Web Filter was hit too, patches are rolling out. Open a ticket with Untangle support if you need the fixes sooner.
                  Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
                  NexgenAppliances.com
                  Phone: 866-794-8879 x201
                  Email: [email protected]

                  Comment


                  • #10
                    Originally posted by andrew50 View Post
                    Also, this is only happening on a small subset of untangle boxes I have...and they are all the oldest hardware..
                    I initially observed that only my older Atom D510 (SuperMicro X7SPA) boxes were affected, the newer one I have running on a Celeron 3205u (Haswell architecture) had not been affected, nor had the one running on ESXi (dual Xeon quad-core). However a few days ago I saw that the Celeron 3205u had been affected as well; internet access hadn't gone down entirely yet, but everything was being categorized "Uncategorized" and there were a smattering of "Unknown" as well. So that blew the "older hardware" theory... a haswell celeron may not exactly be brand new, but it's barely 4 years old vs almost 10.

                    In any case, tech support added all my affected boxes to the early access list for v14.2.1 which hopefully fixes this (so far so good, fingers crossed). I didn't bother with the couple I had running just Web Monitor though, I just turned it off since it doesn't do anything important.

                    Comment

                    Working...
                    X
                    😀
                    🥰
                    🤢
                    😎
                    😡
                    👍
                    👎