write UDPv4 []: No buffer space available (code=105)

Home Page Forums Network Management Signal a BUG write UDPv4 []: No buffer space available (code=105)

This topic contains 5 replies, has 0 voices, and was last updated by  halfers2 7 years, 6 months ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #42686

    halfers2
    Member

    hi

    i had tried a few things to fix this issue below:

    1. cron job to refresh the buffers which only could be set to every 1 minute

    # Bash script: drop_caches-Cron

    sync ; echo 3 > /proc/sys/vm/drop_caches
    sync ; echo 0 > /proc/sys/vm/drop_caches

    which had some success.

    2. the start up bash script has now got this :

    echo 8192 >/proc/sys/vm/min_free_kbytes

    which doesnt work, i have googled and not found the root cause i would like to either extend dirty fix number 1 and get the cron job to run more frequently or ideally find out why the vpns cant handle the data being put through with them, i can see them get clogged up.

    there is something i feel i should mention, my local zeroshell machine has a lan then runs at 1000mbps

    and my pc runs a t 100mbps, i have seen some crazy packet loss but its looks more like an issue with the zeroshell ethernet and the current beta 13 kernal and looks to be harmless nonsense.

    any help on this one would much appreciated.

    kind regards

    s

    12:34:19 Initialization Sequence Completed
    12:34:20 Interface VPN00 is UP
    12:35:38 write UDPv4 []: No buffer space available (code=105)
    12:35:38 write UDPv4 []: No buffer space available (code=105)
    12:35:38 write UDPv4 []: No buffer space available (code=105)
    12:35:38 write UDPv4 []: No buffer space available (code=105)
    12:35:38 write UDPv4 []: No buffer space available (code=105)
    12:35:38 write UDPv4 []: No buffer space available (code=105)
    12:35:38 write UDPv4 []: No buffer space available (code=105)
    12:35:40 message repeated 4 times
    12:35:40 write UDPv4 []: No buffer space available (code=105)
    12:35:40 write UDPv4 []: No buffer space available (code=105)
    12:35:40 write UDPv4 []: No buffer space available (code=105)
    12:35:40 write UDPv4 []: No buffer space available (code=105)
    12:35:40 write UDPv4 []: No buffer space available (code=105)
    12:35:40 write UDPv4 []: No buffer space available (code=105)
    12:35:40 write UDPv4 []: No buffer space available (code=105)
    12:35:41 write UDPv4 []: No buffer space available (code=105)
    12:35:41 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:43 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:44 write UDPv4 []: No buffer space available (code=105)
    12:35:45 message repeated 9 times
    12:35:47 write UDPv4 []: No buffer space available (code=105)
    12:35:47 write UDPv4 []: No buffer space available (code=105)
    12:35:49 write UDPv4 []: No buffer space available (code=105)
    12:35:49 write UDPv4 []: No buffer space available (code=105)
    12:35:49 write UDPv4 []: No buffer space available (code=105)
    12:35:49 write UDPv4 []: No buffer space available (code=105)
    12:35:49 write UDPv4 []: No buffer space available (code=105)
    12:35:49 write UDPv4 []: No buffer space available (code=105)
    12:35:49 write UDPv4 []: No buffer space available (code=105)
    12:35:51 write UDPv4 []: No buffer space available (code=105)
    12:35:53 write UDPv4 []: No buffer space available (code=105)
    12:35:57 write UDPv4 []: No buffer space available (code=105)
    12:35:57 write UDPv4 []: No buffer space available (code=105)
    12:36:01 write UDPv4 []: No buffer space available (code=105)
    12:36:03 write UDPv4 []: No buffer space available (code=105)

    #51196

    ppalias
    Member

    If you raise the min_free_kbytes to 8192 you should not see the memory drop below 8kbytes when you run the command free.

    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 188528 171812 16716 0 38340 34652
    -/+ buffers/cache: 98820 89708
    Swap: 131064 0 131064

    For example here, when the 16716 drop below 8192, the system will free some memory used in buffers and cache to allocate in the programs that need it. If you see less than 8kbytes memory in your ZS then something else is wrong. I think it is unnecessary to run a cronjob for freeing up memory.

    #51197

    halfers2
    Member

    hi thank for the responce, i did as you suggested and as long as the vpn was idle there was no issue.

    unfortunatley when i used the vpns there seems to be no mechanism on the local side to process the data quick enough and its just gets clocgged up and this forces the vpn down onces its hit critical mass.
    i put this in to proove my theory to myself :

    # Bash script: drop_cACHES-Cron
    #!/bin/bash
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &
    sleep 3
    sync ; echo 0 > /proc/sys/vm/drop_caches
    sync ; echo 3 > /proc/sys/vm/drop_caches &

    it works great, buts it wrong i know it is its giving me a whole new set of problems.

    17:37:16 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #78978 / time = (1286972251) Wed Oct 13 13:17:31 2010 ] — see the man page entry for –no-replay and –replay-window for more info or silence this warning with –mute-replay-warnings
    17:38:04 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #84051 / time = (1286972251) Wed Oct 13 13:17:31 2010 ] — see the man page entry for –no-replay and –replay-window for more info or silence this warning with –mute-replay-warnings
    17:47:40 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #90294 / time = (1286972251) Wed Oct 13 13:17:31 2010 ] — see the man page entry for –no-replay and –replay-window for more info or silence this warning with –mute-replay-warnings
    17:49:14 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #101072 / time = (1286972251) Wed Oct 13 13:17:31 2010 ] — see the man page entry for –no-replay and –replay-window for more info or silence this warning with –mute-replay-warnings
    17:50:31 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #111279 / time = (1286972251) Wed Oct 13 13:17:31 2010 ] — see the man page entry for –no-replay and –replay-window for more info or silence this warning with –mute-replay-warnings

    #51198

    ppalias
    Member

    When you spot the problem can you run the “free” command to see what is the available memory?

    #51199

    halfers2
    Member

    this is when its idle and showing the error…

    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124056 900640 0 144 11432
    -/+ buffers/cache: 112480 912216
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124788 899908 0 268 11984
    -/+ buffers/cache: 112536 912160
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124760 899936 0 268 11988
    -/+ buffers/cache: 112504 912192
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 125088 899608 0 500 12316
    -/+ buffers/cache: 112272 912424
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 125008 899688 0 500 12352
    -/+ buffers/cache: 112156 912540
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 125052 899644 0 500 12352
    -/+ buffers/cache: 112200 912496
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124636 900060 0 412 12048
    -/+ buffers/cache: 112176 912520
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124612 900084 0 392 12020
    -/+ buffers/cache: 112200 912496
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124628 900068 0 392 12016
    -/+ buffers/cache: 112220 912476
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124036 900660 0 152 11400
    -/+ buffers/cache: 112484 912212
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124488 900208 0 256 11912
    -/+ buffers/cache: 112320 912376
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124872 899824 0 484 12252
    -/+ buffers/cache: 112136 912560
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124232 900464 0 320 11924
    -/+ buffers/cache: 111988 912708
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124288 900408 0 320 11960
    -/+ buffers/cache: 112008 912688
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 123852 900844 0 144 11436
    -/+ buffers/cache: 112272 912424
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 123900 900796 0 144 11428
    -/+ buffers/cache: 112328 912368
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124428 900268 0 264 11956
    -/+ buffers/cache: 112208 912488
    Swap: 131064 0 131064
    root@zeroshell root> free
    total used free shared buffers cached
    Mem: 1024696 124012 900684 0 152 11396
    -/+ buffers/cache: 112464 912232
    Swap: 131064 0 131064
    root@zeroshell root>

    #51200

    ppalias
    Member

    This is not a memory issue, you have almost 10% memory occupied.

    #51201

    Dave.R
    Member

    Hi did you manage to solve this problem we have the same problem .

    we get the dam thing massage : write UDPv4 []: No buffer space available (code=105)

    HELPPPPPPPPPPPPPPPPPPP
    memory free is available tried all of your methods except the corn job .

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.