DNS Server (BIND) Down again. Memory issues?

I am having a problem keeping my VDS up and running. DNS and even Apache go down several times a day. This has been happening all this week sometimes in less than an hour one or both will go down. I have done my best to figure out what is going on & how to fix it but honestly I have no clue except it may have to do with memory. I really could use some help on how to resolve this issue. I am including info I think may help but if there is something else please let me know.

Thank you so much in advance!

Log errors
Nov 10 11:14:42 xinetd[29708]: smtp: fork failed: Cannot allocate memor
y (errno = 12)
Nov 10 11:14:56 httpsd[13923]: fork failed
Nov 10 11:14:56 httpsd[13923]: fork failed
Nov 10 11:17:56 named[13781]: lame server resolving '241.19.114.84.in-a
ddr.arpa' (in '19.114.84.in-addr.arpa'?): 195.34.131.180#53
Nov 10 11:17:58 named[13781]: lame server resolving '132.76.153.12.in-a
ddr.arpa' (in '76.153.12.in-addr.arpa'?): 63.240.234.92#53
Nov 10 11:17:58 named[13781]: lame server resolving '132.76.153.12.in-a
ddr.arpa' (in '76.153.12.in-addr.arpa'?): 63.240.234.92#53
Nov 10 11:18:57 xinetd[29708]: smtp: fork failed: Cannot allocate memor
y (errno = 12)
Nov 10 11:19:07 xinetd[29708]: smtp: fork failed: Cannot allocate memor
y (errno = 12)
Nov 10 11:19:48 xinetd[29708]: service smtp, accept: Cannot allocate me
mory (errno = 12)
Nov 10 11:19:48 xinetd[29708]: service smtp, accept: Cannot allocate me
mory (errno = 12)
Nov 10 11:19:54 named[13781]: lame server resolving '173.76.153.12.in-a
ddr.arpa' (in '76.153.12.in-addr.arpa'?): 63.240.234.92#53
Nov 10 11:19:54 named[13781]: lame server resolving '173.76.153.12.in-a
ddr.arpa' (in '76.153.12.in-addr.arpa'?): 63.240.234.92#53
Nov 10 11:20:07 xinetd[29708]: smtp: fork failed: Cannot allocate memor
y (errno = 12)
Nov 10 11:20:17 named[13781]: lame server resolving 'ns.wcbe.edu.on.ca'
(in 'wcbe.edu.on.ca'?): 199.212.250.5#53
Nov 10 11:27:42 xinetd[11735]: warning: can't get client address: Conne
ction reset by peer
Nov 10 11:29:36 xinetd[14156]: warning: can't get client address: Conne
ction reset by peer
Nov 10 11:40:52 named[13781]: lame server resolving '19.141.150.201.in-
addr.arpa' (in '141.150.201.in-addr.arpa'?): 200.95.144.3#53
Nov 10 11:40:53 last message repeated 3 times

****
Command Used: ulimit a-

core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 53248
virtual memory (kbytes, -v) unlimited

***
Command Used: cat /proc/meminfo

MemTotal: 6220504 kB
MemFree: 58172 kB
Buffers: 122408 kB
Cached: 865268 kB
SwapCached: 427244 kB
Active: 4027764 kB
Inactive: 393028 kB
HighTotal: 2621440 kB
HighFree: 1472 kB
LowTotal: 3599064 kB
LowFree: 56700 kB
SwapTotal: 12586916 kB
SwapFree: 11026440 kB
Dirty: 7124 kB
Writeback: 320 kB
Mapped: 3604704 kB
Slab: 1639248 kB
CommitLimit: 15697168 kB
Committed_AS: 11223300 kB
PageTables: 61492 kB
VmallocTotal: 303096 kB
VmallocUsed: 23200 kB
VmallocChunk: 279768 kB


More Error messages with most recent DNS failure
Nov 10 11:42:27 xinetd[29708]: smtp: fork failed: Cannot allocate memor
y (errno = 12)
Nov 10 11:42:30 last message repeated 2 times
Nov 10 11:45:22 imapd.rc: bind: Address already in use
Nov 10 11:45:22 imapd.rc: ll_daemon_start: Resource temporarily unavail
able
Nov 10 11:45:22 courier-imap: Starting imapd succeeded
Nov 10 11:45:22 imapd-ssl.rc: bind: Address already in use
Nov 10 11:45:22 imapd-ssl.rc: ll_daemon_start: Resource temporarily una
vailable
Nov 10 11:45:22 courier-imap: Starting imap-ssl succeeded
Nov 10 11:45:22 pop3d.rc: bind: Address already in use
Nov 10 11:45:22 pop3d.rc: ll_daemon_start: Resource temporarily unavail
able
Nov 10 11:45:22 courier-imap: Starting pop3 succeeded
Nov 10 11:45:22 pop3d-ssl.rc: bind: Address already in use
Nov 10 11:45:22 pop3d-ssl.rc: ll_daemon_start: Resource temporarily una
vailable
Nov 10 11:45:22 courier-imap: Starting pop3-ssl succeeded
Nov 10 11:47:28 xinetd[13809]: execv( /var/qmail/bin/tcp-env ) failed:
Invalid argument (errno = 22)
Nov 10 11:47:28 xinetd[13810]: execv( /var/qmail/bin/tcp-env ) failed:
Invalid argument (errno = 22)
Nov 10 11:47:43 xinetd[29708]: smtp: fork failed: Cannot allocate memor
y (errno = 12)
Nov 10 11:48:15 last message repeated 3 times
Nov 10 11:48:24 named[13783]: socket.c:2100: fatal error:
Nov 10 11:48:24 named[13783]: select() failed: Cannot allocate memory
Nov 10 11:48:24 named[13783]: exiting (due to fatal error in library)
Nov 10 11:48:36 xinetd[29708]: smtp: fork failed: Cannot allocate memor
y (errno = 12)

 

You seriously need a system administrator to have a look at your system

 

You need more memory in your VPS, or you need to try and do less with it.

Your running out of memory, so new processes can't start.

You could allocate more swap, but it's not ideal and could possibly make things worse as the machine goes into swapping hell.