Pfsense 2.3.1 Routing Log Error



  • 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?



  • 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



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

    Howard



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



  • No problems in dashboard




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



  • Chris:

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

    Howard



  • @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?



Log in to reply