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

    Failover Notifications Mail bombing my email server

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 1 Posters 1.3k 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.
    • R
      reberhar
      last edited by reberhar

      I am currently getting thousands of failover notifications a day. The message keeps growing and old notifications are included. The actual performance of the heads no longer corresponds to these messages.

      I cannot disable the notifications through the GUI. This is 2.6 CE. I have 5 heads, 4 DSL and one is satellite.

      I would like to know the name of the process so that I can restart it.

      Thanks

      Notifications in this message: 22

      14:42:24 MONITOR: WAN4GW has packet loss, omitting from routing group Infinitumn
      8.8.8.8|10.12.4.93|WAN4GW|36.903ms|2.333ms|23%|down|highloss
      14:50:04 MONITOR: WAN4GW is available now, adding to routing group Infinitumn
      8.8.8.8|10.12.4.93|WAN4GW|35.223ms|2.001ms|3%|online|none
      18:55:37 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|48.252ms|11.973ms|22%|down|highloss
      18:59:20 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|37.814ms|79.315ms|12%|online|loss
      19:07:39 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|56.542ms|27.45ms|22%|down|highloss
      19:08:42 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|43.744ms|12.858ms|12%|online|loss
      7:04:09 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|34.109ms|6.688ms|22%|down|highloss
      7:06:16 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|39.918ms|14.76ms|14%|online|loss
      3:14:24 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|40.399ms|9.42ms|22%|down|highloss
      3:16:13 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|47.262ms|15.725ms|12%|online|loss
      3:44:25 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|55.394ms|13.588ms|22%|down|highloss
      3:46:28 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|36.831ms|14.93ms|12%|online|loss
      5:06:54 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|38.575ms|9.06ms|22%|down|highloss
      5:09:12 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|38.974ms|76.508ms|12%|online|loss
      23:36:40 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|46.355ms|8.481ms|22%|down|highloss
      23:38:28 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|46.604ms|19.603ms|12%|online|loss
      3:23:54 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|36.876ms|10.813ms|22%|down|highloss
      3:24:58 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|37.969ms|12.815ms|12%|online|loss
      8:53:39 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|43.99ms|13.975ms|22%|down|highloss
      8:56:59 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|51.468ms|13.014ms|12%|online|loss
      9:02:40 MONITOR: WAN5_DHCP has packet loss, omitting from routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|41.522ms|12.945ms|22%|down|highloss
      9:04:29 MONITOR: WAN5_DHCP is available now, adding to routing group Infinitumn
      100.64.0.1|192.168.1.217|WAN5_DHCP|57.722ms|14.302ms|12%|online|loss

      R 2 Replies Last reply Reply Quote 0
      • R
        reberhar @reberhar
        last edited by reberhar

        This post is deleted!
        1 Reply Last reply Reply Quote 0
        • R
          reberhar @reberhar
          last edited by

          @reberhar I finally bit the bullet and waited until late at night and just did a reboot and that seems to have fixed it.

          R 1 Reply Last reply Reply Quote 0
          • R
            reberhar @reberhar
            last edited by reberhar

            @reberhar The problem keeps coming back, even after reboot. I cannot disable the SMTP with the checkbox, except if I check the checkbox, save of course, and then reboot.

            This kind of acts like a bug.

            Roy

            R 1 Reply Last reply Reply Quote 0
            • R
              reberhar @reberhar
              last edited by

              @reberhar I am working with a machine with 5 heads ( Internet sources) with frequent head changes because of packet loss. I normally get lots of emails anyway from it, but it seems to hit some kind of threshold where it starts sending the same message several times a minute. I get other messages from this server appropriately, e.g. from the UPS, it is just those from the rollover mechanism that bomb my email server.

              R 1 Reply Last reply Reply Quote 0
              • R
                reberhar @reberhar
                last edited by reberhar

                @reberhar So I blew away the gateway logs and turned on the SMTP notifications again. I also resaved all the windows under routing just to be sure. The mail bombing stopped for now. Maybe I will need to change the log rotation.

                R 1 Reply Last reply Reply Quote 0
                • R
                  reberhar @reberhar
                  last edited by

                  @reberhar It seems to be working.

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