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

    Pfsense 2.3.1 Routing Log Error

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 5 Posters 2.6k 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.
    • G
      ghkrauss
      last edited by

      I am receiving the following message in the Routing Log:

      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=370, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=426, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=426, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=442, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=424, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=410, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=430, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=434, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=362, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=370, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=370, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=370, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=426, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=426, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=442, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=424, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=410, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=430, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=434, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto(sock=7, len=362, dest=192.168.1.102:53047): sendto: No buffer space available
      Apr 25 21:02:42 miniupnpd 88764 try_sendto failed to send 30 packets

      Is this a configuration issue?

      1 Reply Last reply Reply Quote 0
      • H
        heper
        last edited by

        upnp acting up i guess. never used it, so can't give advice about its config
        https://doc.pfsense.org/index.php/No_buffer_space_available

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

          Thanks for the suggestion. I will read the information and see what I can do with it.

          Howard

          1 Reply Last reply Reply Quote 0
          • H
            Hugovsky
            last edited by

            I wonder if is related to mbuf. what does your dashboard show?

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

              No problems in dashboard

              Capture.JPG
              Capture.JPG_thumb

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

                Wondering if recvspace/sendspace need to be higher. I bumped those by default earlier this week, does it still do that on latest?

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

                  Chris:

                  This solved the issue. I looked at the routing log and no errors. Thanks very much.

                  Howard

                  1 Reply Last reply Reply Quote 0
                  • luckman212L
                    luckman212 LAYER 8
                    last edited by

                    @cmb:

                    Wondering if recvspace/sendspace need to be higher. I bumped those by default earlier this week

                    Chris what kernel param can we check to see if we are hitting this? I got it earlier this week - dpinger went belly up while I was playing around with Traffic Shaping on my homelab sg2440.  I haven't seen this often but when it pops up I would like to know how to better debug it.

                    The way I fixed it was sledgehammer (# ifconfig igb2 down; ifconfig igb2 up) but that is a bit scary to do remotely.

                    I was thinking if this is just an underlying upstream bug in FreeBSD then maybe there is a way to test for this condition via cron + some sort of log monitoring and automatically bounce the interface if needed?

                    sendto-error-55.png
                    sendto-error-55.png_thumb

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