Results 1 to 7 of 7
  1. #1

    Unhappy memory allocation errors

    I'm running into memory allocation errors on my lowend VPS (64MB).
    I'm only trying to run BIND on it!

    Memory usage is around 22 MB with the bare basic daemons running.
    But as soon as BIND is started, the usage shoots up past the limit.

    Since this is just a base system installation (I've only YUM installed BIND), I was wondering if this is a OpenVZ related and/or a configuration issue.

    The same happened sometime back when I tried to run MySQL as well.

    Can anyone tell me what the typical memory usage for new installations of these services is ?

  2. #2
    forgot to add the config info:

    #cat /proc/user_beancounters
    Version: 2.5
    uid resource held maxheld barrier limit failcnt
    535: kmemsize 749558 2759751 52653068 53918374 0
    lockedpages 0 0 32 32 0
    privvmpages 4899 19095 16384 32768 1968
    shmpages 640 992 8192 8192 0
    dummy 0 0 0 0 0
    numproc 7 27 100 100 0
    physpages 2067 10008 0 2147483647 0
    vmguarpages 0 0 16384 2147483647 0
    oomguarpages 2067 10008 6144 2147483647 0
    numtcpsock 3 21 80 80 0
    numflock 0 3 100 110 0
    numpty 1 1 16 16 0
    numsigninfo 0 20 256 256 0
    tcpsndbuf 4472 149812 319488 524288 0
    tcprcvbuf 0 4472 319488 524288 0
    othersockbuf 6264 16080 292096 336896 0
    dgramrcvbuf 0 8380 132096 132096 0
    numothersock 3 18 80 80 0
    dcachesize 56304 120888 1267200 1267200 0
    numfile 191 562 3300 3300 0
    dummy 0 0 0 0 0
    dummy 0 0 0 0 0
    dummy 0 0 0 0 0
    numiptent 10 10 128 128 0

  3. #3
    Join Date
    May 2006
    Location
    Coimbra, Portugal
    Posts
    236
    Usually bind need more memory to start than to run.

    Look at my DNS VPS privvmpages (4k pages):
    privvmpages 17204 24374 32768 32768

    It's using 67,2MB RAM but needs 95,21MB to start...

    If your provider increase your burstable ram to 128MB you should be able to start it

  4. #4
    Join Date
    Feb 2006
    Location
    West Lafayette, IN
    Posts
    15
    I wouldn't recommend trying to run Bind on 64meg of memory. It is a particularly hard process to manage that will listen on any IPs on the server. As was stated above, it does take more to start as during startup it goes through and resyncs all of the zone files.

  5. #5
    Quote Originally Posted by thekiwiproject
    I wouldn't recommend trying to run Bind on 64meg of memory. It is a particularly hard process to manage that will listen on any IPs on the server. As was stated above, it does take more to start as during startup it goes through and resyncs all of the zone files.
    Well, that's too bad.
    The vps offer said - "great for running secondary dns"



    Quote Originally Posted by sspt
    If your provider increase your burstable ram to 128MB you should be able to start it
    I thought my burst limit was 128 already.
    Isn't the "limit" of privvmpages the same as the burstable ram ?

  6. #6
    Join Date
    May 2006
    Location
    Coimbra, Portugal
    Posts
    236
    Quote Originally Posted by Whoa
    Well, that's too bad.
    The vps offer said - "great for running secondary dns"




    I thought my burst limit was 128 already.
    Isn't the "limit" of privvmpages the same as the burstable ram ?
    The privvmpages barrier is your 'burstable RAM Value'

    Quote Originally Posted by OpenVZ WiKi
    There should be a safety gap between the barrier and the limit for privvmpages parameter to reduce the number of memory allocation failures that the application is unable to handle. This gap will be used for “high-priority” memory allocations, such as process stack expansion. Normal priority allocations will fail when the barrier if privvmpages is reached.

  7. #7
    Join Date
    Mar 2005
    Location
    Labrador, Canada
    Posts
    951
    If your nameserver will be only serving domains for which it is authoritative you might look at NSD - http://www.nlnetlabs.nl/nsd/ - instead of Bind. It uses a fraction of the memory and can read/use Bind zone files.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •