swapinfo depois que vi o erro.. o squid estava UP consumindo 48% da memoria total (valores obtidos via ps) nesta maquina tenho apenas squid + bind (bind eh utilizado apenas pelo squid)
On Thu, Nov 13, 2008 at 1:52 AM, Thiago Damas <[EMAIL PROTECTED]> wrote: > O swapinfo foi executado durante ou depois dos erros? Tem toda a cara > do squid estar usando toda a memoria, e todo o swap (se nao for o > squid, pode ser outro processo) > []s > > > On Thu, Nov 13, 2008 at 1:14 AM, Alexandre Correa > <[EMAIL PROTECTED]> wrote: >> Caros, >> >> comecei a receber estas mensagens: >> >> swap_pager_getswapspace(2): failed >> swap_pager_getswapspace(4): failed >> swap_pager_getswapspace(4): failed >> swap_pager_getswapspace(4): failed >> swap_pager_getswapspace(6): failed >> swap_pager_getswapspace(2): failed >> swap_pager_getswapspace(2): failed >> swap_pager_getswapspace(8): failed >> swap_pager_getswapspace(12): failed >> swap_pager_getswapspace(4): failed >> swap_pager_getswapspace(6): failed >> swap_pager_getswapspace(16): failed >> swap_pager_getswapspace(12): failed >> swap_pager_getswapspace(2): failed >> swap_pager_getswapspace(4): failed >> swap_pager_getswapspace(2): failed >> swap_pager_getswapspace(2): failed >> swap_pager_getswapspace(4): failed >> swap_pager_getswapspace(6): failed >> /var/spool/squid: optimization changed from SPACE to TIME >> pid 990 (named), uid 53, was killed: out of swap space >> /var/spool/squid: optimization changed from TIME to SPACE >> >> servidor é um dell, com 2 dual-core opteron, 4gb de ram, partição swap >> tem 4gb, versao do freebsd: AMD64 - 7.0-RELEASE-p3 ... atualizado do >> 6.2 para 6.3 e depois do 6.3 para 7.0 p3 ... >> >> swapinfo >> Device 1K-blocks Used Avail Capacity >> /dev/da0s1b 4204636 23464 4181172 1% >> >> o sistema fica em um hd.. e o proxy (/var/spoo/squid) fica em outro hd >> .. ambos 146gb sas 15.000 rpm .. >> >> no loader.conf tenho estes valores: >> >> kern.ipc.nmbclusters=262144 >> kern.maxfiles=65535 >> kern.maxfilesperproc=32768 >> kern.maxvnodes=120000 >> kern.ipc.somaxconn=65535 >> kern.ipc.msgmnb=8192 >> kern.ipc.msgmni=40 >> kern.ipc.msgseg=512 >> kern.ipc.msgssz=64 >> kern.ipc.msgtql=2048 >> >> kern.ipc.semmsl=32 >> kern.ipc.shmmni=78 >> kern.ipc.shmseg=2 >> kern.ipc.semmns=1128 >> kern.ipc.semmap=512 >> kern.ipc.shmmax=25769803776 >> kern.ipc.shmall=6291456 >> >> >> >> alguem conhece este erro ? sabe me dizer algo sobre ? >> >> >> obrigado !!!! >> >> >> -- >> >> Sds. >> Alexandre J. Correa >> Onda Internet / OPinguim.net >> http://www.ondainternet.com.br >> http://www.opinguim.net >> ------------------------- >> Histórico: http://www.fug.com.br/historico/html/freebsd/ >> Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd >> > ------------------------- > Histórico: http://www.fug.com.br/historico/html/freebsd/ > Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd > -- Sds. Alexandre J. Correa Onda Internet / OPinguim.net http://www.ondainternet.com.br http://www.opinguim.net ------------------------- Histórico: http://www.fug.com.br/historico/html/freebsd/ Sair da lista: https://www.fug.com.br/mailman/listinfo/freebsd
