OVH Community, your new community space.

VPS2013: deja de funcionar el correo


X3Mdesign
25/10/2013, 12:49
Pues te cuento, inicialmente tenía un RPSII, instalé ispCP y no me dio ningún problema hasta que me quedé sin disco... pensé que el VPS sería su relevo... pero con lo mismo instalado (ahora i-MSCP) se queda sin recursos al arrancarlo, no sé el motivo, pero siempre anda al +85% de RAM usada... y menos mal que me han echado una (gran) mano desde sus foros...

Instalarlo, no sería el problema, si no configurarlo si hay que tocar algo porque no tengo mucha idea...

Gracias de nuevo

Guille
25/10/2013, 12:34
Pues si te da miedo instalar el ntp, no sé como gestionas todo un VPS...

X3Mdesign
25/10/2013, 08:55
Hola Guille, gracias por la respuesta, estuve viendo el wiki, pero no tengo conocimientos para intentar instalar el ntpd y mucho menos solucionar si la cago...

Guille
24/10/2013, 08:51
http://wiki.dovecot.org/TimeMovedBackwards

X3Mdesign
23/10/2013, 10:06
Otra vez a reiniciar... parece que devecot se come la CPU... plis echadme una mano

http://www.noestandificil.x3mdesign....23-captura.jpg

X3Mdesign
05/10/2013, 16:39
Hola de nuevo, gracias a todos por las respuestas...

ha vuelto a ocurrir, pero en este caso no con un elevado uso de CPU, este es el comando "top" antes de reiniciar, esta vez no se cuándo ha dejado de funcionar, pero he reiniciado a eso de las 14:15

http://www.noestandificil.x3mdesign....aptura_top.jpg

Este el /var/log/daemon.log, me extraña que alguien haya hecho FTP a las 05 de la mañana... he subido sólo el día de hoy esto son /var/log/syslog y el var/log/mail.log

¿¿cómo puedo solucionar esto??
Cita Publicado inicialmente por MarcosBL
Yo empezaría por solucionar esto, es una barbaridad de segundos, y dovecot se "suicida"

Puedes solucionarlo simplemente instalando/iniciando ntpd para que ponga en hora el servidor
¿¿y esto?? es cierto Guille, el valor de smtpd_sasl_type es dovecot, pero cuál debería ser
Cita Publicado inicialmente por Guille
Y el que dovecot no funcione provoca que postfix deje de funcionar
Ya que seguramente has especificado en main.cf que dovecot debe hacerse cargo del SASL.
Muchas gracias a todos de nuevo!!!

Guille
25/09/2013, 06:29
Y el que dovecot no funcione provoca que postfix deje de funcionar
fatal: no SASL authentication mechanisms
Ya que seguramente has especificado en main.cf que dovecot debe hacerse cargo del SASL.

smtpd_sasl_type = dovecot

MarcosBL
25/09/2013, 03:16
Yo empezaría por solucionar esto, es una barbaridad de segundos, y dovecot se "suicida"
Sep 24 01:31:48 server dovecot: dovecot: Fatal: Time just moved backwards by 1266874663 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards
Puedes solucionarlo simplemente instalando/iniciando ntpd para que ponga en hora el servidor

pepejlr
24/09/2013, 23:58
No nos dice nada relevante :S

En tal caso cuando se te puso al 100% de CPU hiciste un hard reset o seguias teniendo acceso normal al SSH? Si está al 100% en ese momento ejecuta el comando "top" sin las comillas para saber que proceso es el que está procesando de esa forma tan salvaje.

Sobre la caida del servidor de correo estaria bien que nos pasases logs justo después de que detectes que deja de funcionar. /var/log/mail.log, /var/log/daemon.log y /var/log/syslog.

X3Mdesign
24/09/2013, 10:33
/var/log/error
Código:
Sep 23 01:05:49 server suhosin[4944]: ALERT - configured request variable name length limit exceeded - dropped variable 'seccion%252525252525253Dcontenido%2525252525252526id_contenido%252525252525253D3' (attacker '65.55.215.250', file '/var/www/virtual/camaleonsocialmedia.es/alias/doctorangeljuarez.com/htdocs/index.php')
Sep 24 01:31:48 server dovecot: dovecot: Fatal: Time just moved backwards by 1266874663 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards
Sep 24 01:48:42 server postfix/smtpd[26054]: fatal: no SASL authentication mechanisms
Sep 24 02:52:18 server postfix/smtpd[26752]: fatal: no SASL authentication mechanisms
Sep 24 03:10:00 server postfix/smtpd[27065]: fatal: no SASL authentication mechanisms
Sep 24 03:11:11 server postfix/smtpd[27081]: fatal: no SASL authentication mechanisms
Sep 24 03:13:56 server postfix/smtpd[27093]: fatal: no SASL authentication mechanisms
Sep 24 03:21:08 server postfix/smtpd[27107]: fatal: no SASL authentication mechanisms
Sep 24 03:22:19 server postfix/smtpd[27109]: fatal: no SASL authentication mechanisms
Sep 24 03:23:33 server postfix/smtpd[27112]: fatal: no SASL authentication mechanisms
Sep 24 03:24:47 server postfix/smtpd[27119]: fatal: no SASL authentication mechanisms
Sep 24 03:25:58 server postfix/smtpd[27126]: fatal: no SASL authentication mechanisms
Sep 24 03:27:11 server postfix/smtpd[27129]: fatal: no SASL authentication mechanisms
Sep 24 03:28:22 server postfix/smtpd[27132]: fatal: no SASL authentication mechanisms
Sep 24 03:29:33 server postfix/smtpd[27135]: fatal: no SASL authentication mechanisms
Sep 24 03:30:44 server postfix/smtpd[27373]: fatal: no SASL authentication mechanisms
Sep 24 03:31:55 server postfix/smtpd[27418]: fatal: no SASL authentication mechanisms
Sep 24 03:33:07 server postfix/smtpd[27425]: fatal: no SASL authentication mechanisms
Sep 24 03:34:18 server postfix/smtpd[27429]: fatal: no SASL authentication mechanisms
Sep 24 03:36:40 server postfix/smtpd[27432]: fatal: no SASL authentication mechanisms
Sep 24 03:37:56 server postfix/smtpd[27436]: fatal: no SASL authentication mechanisms
Sep 24 03:39:26 server postfix/smtpd[27441]: fatal: no SASL authentication mechanisms
Sep 24 03:49:37 server postfix/smtpd[27478]: fatal: no SASL authentication mechanisms
Sep 24 03:50:48 server postfix/smtpd[27480]: fatal: no SASL authentication mechanisms
Sep 24 03:51:59 server postfix/smtpd[27483]: fatal: no SASL authentication mechanisms
Sep 24 03:53:10 server postfix/smtpd[27484]: fatal: no SASL authentication mechanisms
Sep 24 04:03:40 server postfix/smtpd[27831]: fatal: no SASL authentication mechanisms
Sep 24 04:08:38 server postfix/smtpd[27849]: fatal: no SASL authentication mechanisms
Sep 24 04:09:49 server postfix/smtpd[27863]: fatal: no SASL authentication mechanisms
Sep 24 04:11:00 server postfix/smtpd[27864]: fatal: no SASL authentication mechanisms
Sep 24 04:12:11 server postfix/smtpd[27867]: fatal: no SASL authentication mechanisms
Sep 24 04:13:22 server postfix/smtpd[27875]: fatal: no SASL authentication mechanisms
Sep 24 04:14:33 server postfix/smtpd[27876]: fatal: no SASL authentication mechanisms
Sep 24 04:15:44 server postfix/smtpd[27877]: fatal: no SASL authentication mechanisms
Sep 24 04:16:55 server postfix/smtpd[27882]: fatal: no SASL authentication mechanisms
Sep 24 04:18:06 server postfix/smtpd[27885]: fatal: no SASL authentication mechanisms
Sep 24 04:19:17 server postfix/smtpd[27888]: fatal: no SASL authentication mechanisms
Sep 24 04:20:28 server postfix/smtpd[27895]: fatal: no SASL authentication mechanisms
Sep 24 04:21:39 server postfix/smtpd[27898]: fatal: no SASL authentication mechanisms
Sep 24 04:22:52 server postfix/smtpd[27903]: fatal: no SASL authentication mechanisms
Sep 24 04:24:26 server postfix/smtpd[27912]: fatal: no SASL authentication mechanisms
Sep 24 04:37:06 server postfix/smtpd[28204]: fatal: no SASL authentication mechanisms
Sep 24 04:38:17 server postfix/smtpd[28210]: fatal: no SASL authentication mechanisms
Sep 24 04:39:28 server postfix/smtpd[28223]: fatal: no SASL authentication mechanisms
Sep 24 04:40:39 server postfix/smtpd[28228]: fatal: no SASL authentication mechanisms
Sep 24 04:56:02 server postfix/smtpd[28273]: fatal: no SASL authentication mechanisms
Sep 24 04:57:14 server postfix/smtpd[28279]: fatal: no SASL authentication mechanisms
Sep 24 04:58:26 server postfix/smtpd[28282]: fatal: no SASL authentication mechanisms
Sep 24 04:59:38 server postfix/smtpd[28283]: fatal: no SASL authentication mechanisms
Sep 24 05:00:49 server postfix/smtpd[28501]: fatal: no SASL authentication mechanisms
Sep 24 05:02:00 server postfix/smtpd[28758]: fatal: no SASL authentication mechanisms
Sep 24 05:03:11 server postfix/smtpd[28765]: fatal: no SASL authentication mechanisms
Gracias de nuevo!!! Te hace falta alguno más¿?

X3Mdesign
24/09/2013, 10:33
/var/log/syslog.1 (he borrado bastantes líneas con ips, porque no cabían los caracteres...
Código:
Sep 24 01:30:01 server /USR/SBIN/CRON[25663]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-srv-traff &>/var/log/imscp/imscp-srv-traff.log)
Sep 24 01:30:01 server /USR/SBIN/CRON[25661]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-vrl-traff &>/var/log/imscp/imscp-vrl-traff.log)
Sep 24 01:30:01 server /USR/SBIN/CRON[25662]: (root) CMD (/var/www/imscp/engine/tools/imscp-del-tmp >/dev/null 2>&1)
Sep 24 01:30:05 server named[471]: error (unexpected RCODE REFUSED) resolving '22.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:30:06 server named[471]: error (unexpected RCODE REFUSED) resolving '22.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 01:30:56 server named[471]: error (unexpected RCODE REFUSED) resolving '62.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:31:45 server named[471]: error (unexpected RCODE REFUSED) resolving '148.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:31:45 server named[471]: error (unexpected RCODE REFUSED) resolving '148.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 01:34:08 server named[471]: error (unexpected RCODE REFUSED) resolving '165.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:34:39 server named[471]: error (unexpected RCODE REFUSED) resolving '52.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:34:40 server named[471]: error (unexpected RCODE REFUSED) resolving '52.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 01:34:48 server named[471]: error (unexpected RCODE REFUSED) resolving '185.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 01:36:49 server named[471]: error (unexpected RCODE REFUSED) resolving '157.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:37:52 server named[471]: error (unexpected RCODE REFUSED) resolving 'ns2.bta.net.cn/A/IN': 202.106.196.233#53
Sep 24 01:37:53 server named[471]: error (unexpected RCODE REFUSED) resolving 'ns.bta.net.cn/AAAA/IN': 202.106.196.233#53
Sep 24 01:38:15 server named[471]: error (unexpected RCODE REFUSED) resolving '192.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:38:16 server named[471]: error (unexpected RCODE REFUSED) resolving '192.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
..
Sep 24 01:38:30 server named[471]: error (unexpected RCODE REFUSED) resolving '149.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:39:01 server /USR/SBIN/CRON[26011]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Sep 24 01:40:10 server named[471]: error (unexpected RCODE REFUSED) resolving '113.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:40:10 server named[471]: error (unexpected RCODE REFUSED) resolving '113.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 01:41:10 server named[471]: error (unexpected RCODE REFUSED) resolving '52.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:41:11 server named[471]: error (unexpected RCODE REFUSED) resolving '52.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 01:43:32 server named[471]: error (unexpected RCODE REFUSED) resolving '184.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:43:32 server named[471]: error (unexpected RCODE REFUSED) resolving '184.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 01:48:37 server named[471]: error (unexpected RCODE REFUSED) resolving '161.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:50:04 server named[471]: client 85.25.91.10#29756: query (cache) 'www.palmaresdeportivo.net/AAAA/IN' denied
Sep 24 01:50:04 server named[471]: client 85.25.91.10#39140: query (cache) 'www.palmaresdeportivo.net/AAAA/IN' denied
Sep 24 01:50:04 server named[471]: client 85.25.91.14#58765: query (cache) 'www.palmaresdeportivo.net/AAAA/IN' denied
Sep 24 01:50:05 server named[471]: client 85.25.26.178#19152: query (cache) 'www.palmaresdeportivo.net/AAAA/IN' denied
Sep 24 01:50:05 server named[471]: client 85.25.91.10#31113: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 01:50:05 server named[471]: client 85.25.91.14#49241: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 01:50:05 server named[471]: client 85.25.26.178#41744: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 01:50:06 server named[471]: client 85.25.91.10#47900: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 01:50:29 server named[471]: error (unexpected RCODE REFUSED) resolving '12.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:50:30 server named[471]: error (unexpected RCODE REFUSED) resolving '12.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 01:51:57 server named[471]: error (unexpected RCODE REFUSED) resolving '23.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:51:57 server named[471]: error (unexpected RCODE REFUSED) resolving '23.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 01:53:05 server named[471]: error (unexpected RCODE REFUSED) resolving '146.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:53:06 server named[471]: error (unexpected RCODE REFUSED) resolving '146.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 01:53:07 server named[471]: error (unexpected RCODE REFUSED) resolving '26.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:55:19 server named[471]: error (unexpected RCODE REFUSED) resolving '139.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:55:19 server named[471]: error (unexpected RCODE REFUSED) resolving '139.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 01:58:41 server named[471]: error (unexpected RCODE REFUSED) resolving '27.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:58:41 server named[471]: error (unexpected RCODE REFUSED) resolving '27.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:59:01 server named[471]: error (unexpected RCODE REFUSED) resolving '161.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 01:59:01 server named[471]: error (unexpected RCODE REFUSED) resolving '161.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 01:59:13 server named[471]: error (unexpected RCODE REFUSED) resolving '55.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 01:59:14 server named[471]: error (unexpected RCODE REFUSED) resolving '55.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:00:01 server /USR/SBIN/CRON[26092]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-srv-traff &>/var/log/imscp/imscp-srv-traff.log)
Sep 24 02:00:01 server /USR/SBIN/CRON[26093]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-vrl-traff &>/var/log/imscp/imscp-vrl-traff.log)
Sep 24 02:00:01 server /USR/SBIN/CRON[26096]: (root) CMD (/var/www/imscp/engine/tools/imscp-del-tmp >/dev/null 2>&1)
Sep 24 02:00:21 server named[471]: error (unexpected RCODE REFUSED) resolving '182.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:00:22 server named[471]: error (unexpected RCODE REFUSED) resolving '182.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 02:02:47 server named[471]: error (unexpected RCODE REFUSED) resolving '167.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:03:43 server named[471]: client 176.74.192.71#39301: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 02:03:43 server named[471]: client 176.74.192.71#39301: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 02:04:47 server named[471]: error (unexpected RCODE REFUSED) resolving '158.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:04:47 server named[471]: error (unexpected RCODE REFUSED) resolving '158.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:05:42 server named[471]: error (unexpected RCODE REFUSED) resolving '90.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:05:42 server named[471]: error (unexpected RCODE REFUSED) resolving '90.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:06:30 server named[471]: success resolving 'NSGDL2.UNINET.NET.MX/A' (in 'UNINET.NET.mx'?) after reducing the advertised EDNS UDP packet size to 512 octets
Sep 24 02:06:31 server named[471]: success resolving 'NSGDL2.UNINET.NET.MX/AAAA' (in 'UNINET.NET.mx'?) after reducing the advertised EDNS UDP packet size to 512 octets
Sep 24 02:07:05 server named[471]: error (unexpected RCODE REFUSED) resolving '7.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:07:06 server named[471]: error (unexpected RCODE REFUSED) resolving '7.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:09:01 server /USR/SBIN/CRON[26397]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Sep 24 02:09:11 server named[471]: client 65.55.37.37#53542: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 02:09:11 server named[471]: client 65.55.37.37#53542: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 02:09:12 server named[471]: client 65.55.37.37#53542: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 02:11:12 server named[471]: error (unexpected RCODE REFUSED) resolving '167.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:11:12 server named[471]: error (unexpected RCODE REFUSED) resolving '167.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 02:11:47 server named[471]: client 76.76.11.241#57896: query (cache) 'palmaresdeportivo.net/ANY/IN' denied
Sep 24 02:11:47 server named[471]: client 76.76.11.241#57896: query (cache) 'palmaresdeportivo.net/SOA/IN' denied
Sep 24 02:11:48 server named[471]: client 76.76.11.241#57896: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 02:11:48 server named[471]: client 76.76.11.241#57896: query (cache) 'palmaresdeportivo.net/MX/IN' denied
Sep 24 02:11:49 server named[471]: client 76.76.11.241#57896: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 02:12:01 server /USR/SBIN/CRON[26415]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 24 02:12:24 server named[471]: client 37.140.137.5#19199: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 02:12:59 server named[471]: error (unexpected RCODE REFUSED) resolving '62.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:12:59 server named[471]: error (unexpected RCODE REFUSED) resolving '62.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:14:47 server named[471]: error (unexpected RCODE REFUSED) resolving '157.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:14:47 server named[471]: error (unexpected RCODE REFUSED) resolving '157.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:15:31 server named[471]: error (unexpected RCODE REFUSED) resolving '26.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:15:31 server named[471]: error (unexpected RCODE REFUSED) resolving '26.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 02:16:05 server named[471]: error (unexpected RCODE REFUSED) resolving '153.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:16:05 server named[471]: error (unexpected RCODE REFUSED) resolving '153.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:23:27 server named[471]: error (unexpected RCODE REFUSED) resolving '57.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:23:27 server named[471]: error (unexpected RCODE REFUSED) resolving '57.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 02:24:33 server named[471]: error (unexpected RCODE REFUSED) resolving '186.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:24:33 server named[471]: error (unexpected RCODE REFUSED) resolving '186.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:24:33 server named[471]: client 65.55.37.37#37683: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 02:24:34 server named[471]: client 65.55.37.37#37683: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 02:24:34 server named[471]: client 65.55.37.37#37683: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 02:24:34 server named[471]: error (unexpected RCODE REFUSED) resolving '186.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:24:34 server named[471]: error (unexpected RCODE REFUSED) resolving '186.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:24:46 server named[471]: error (unexpected RCODE REFUSED) resolving '95.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:24:46 server named[471]: error (unexpected RCODE REFUSED) resolving '95.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:27:39 server named[471]: client 199.48.164.7#53041: query (cache) 'palmaresdeportivo.net/ANY/IN' denied
Sep 24 02:27:39 server named[471]: client 199.48.164.7#53041: query (cache) 'palmaresdeportivo.net/SOA/IN' denied
Sep 24 02:27:39 server named[471]: client 199.48.164.7#53041: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 02:27:40 server named[471]: client 199.48.164.7#53041: query (cache) 'palmaresdeportivo.net/MX/IN' denied
Sep 24 02:27:40 server named[471]: client 199.48.164.7#53041: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 02:29:29 server named[471]: error (unexpected RCODE REFUSED) resolving '143.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:29:29 server named[471]: error (unexpected RCODE REFUSED) resolving '143.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 02:30:01 server /USR/SBIN/CRON[26460]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-srv-traff &>/var/log/imscp/imscp-srv-traff.log)
Sep 24 02:30:01 server /USR/SBIN/CRON[26461]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-vrl-traff &>/var/log/imscp/imscp-vrl-traff.log)
Sep 24 02:30:01 server /USR/SBIN/CRON[26462]: (root) CMD (/var/www/imscp/engine/tools/imscp-del-tmp >/dev/null 2>&1)
Sep 24 02:30:29 server named[471]: error (unexpected RCODE REFUSED) resolving '52.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:30:29 server named[471]: error (unexpected RCODE REFUSED) resolving '52.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:30:42 server named[471]: error (unexpected RCODE REFUSED) resolving '111.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:30:43 server named[471]: error (unexpected RCODE REFUSED) resolving '111.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:32:02 server named[471]: error (unexpected RCODE REFUSED) resolving '95.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:32:02 server named[471]: error (unexpected RCODE REFUSED) resolving '95.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:33:27 server named[471]: error (unexpected RCODE REFUSED) resolving '29.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:34:12 server named[471]: client 121.10.40.130#65006: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:13 server named[471]: client 121.10.40.130#12845: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:15 server named[471]: client 121.10.40.130#39472: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:15 server named[471]: client 121.10.40.130#38064: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:17 server named[471]: client 121.10.40.130#53561: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:18 server named[471]: client 121.10.40.130#50906: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:18 server named[471]: client 202.96.136.240#42576: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:18 server named[471]: client 202.96.136.240#24584: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:20 server named[471]: client 121.10.40.130#24628: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:20 server named[471]: client 61.140.11.220#36550: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:20 server named[471]: client 121.10.40.130#32112: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:21 server named[471]: client 202.96.136.240#61249: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:21 server named[471]: client 61.140.11.220#59634: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:21 server named[471]: client 202.96.136.240#47421: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:22 server named[471]: client 61.140.11.220#31482: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:34:23 server named[471]: client 61.140.11.220#62017: query (cache) 'www.zen-sano.com/A/IN' denied
Sep 24 02:35:34 server named[471]: error (unexpected RCODE REFUSED) resolving '59.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:35:34 server named[471]: error (unexpected RCODE REFUSED) resolving '59.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:36:35 server named[471]: error (unexpected RCODE REFUSED) resolving '161.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:38:16 server named[471]: client 80.58.184.16#45610: query (cache) 'zen-sano.com/A/IN' denied
Sep 24 02:38:17 server named[471]: client 80.58.184.21#26292: query (cache) 'zen-sano.com/A/IN' denied
Sep 24 02:38:17 server named[471]: client 80.58.184.16#23764: query (cache) 'zen-sano.com/A/IN' denied
Sep 24 02:38:17 server named[471]: client 80.58.184.16#44184: query (cache) 'zen-sano.com/A/IN' denied
Sep 24 02:38:17 server named[471]: client 80.58.184.21#14053: query (cache) 'zen-sano.com/A/IN' denied
Sep 24 02:38:35 server named[471]: error (unexpected RCODE REFUSED) resolving 'NS.INTELNET.NET.GT/AAAA/IN': 216.230.128.32#53
Sep 24 02:38:36 server named[471]: success resolving 'NS.COMTECH.NET.GT/A' (in 'COMTECH.NET.GT'?) after reducing the advertised EDNS UDP packet size to 512 octets
Sep 24 02:38:36 server named[471]: success resolving 'NS.COMTECH.NET.GT/AAAA' (in 'COMTECH.NET.GT'?) after reducing the advertised EDNS UDP packet size to 512 octets
Sep 24 02:38:36 server named[471]: success resolving 'NS.INTELNET.NET.GT/AAAA' (in 'INTELNET.NET.GT'?) after reducing the advertised EDNS UDP packet size to 512 octets
Sep 24 02:38:37 server named[471]: error (unexpected RCODE REFUSED) resolving 'NS.INTELNET.NET.GT/AAAA/IN': 216.230.128.32#53
Sep 24 02:39:01 server /USR/SBIN/CRON[26719]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Sep 24 02:39:55 server named[471]: error (unexpected RCODE REFUSED) resolving '21.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:39:55 server named[471]: error (unexpected RCODE REFUSED) resolving '21.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:41:23 server named[471]: error (unexpected RCODE REFUSED) resolving '147.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:41:23 server named[471]: error (unexpected RCODE REFUSED) resolving '147.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 02:41:40 server named[471]: error (unexpected RCODE REFUSED) resolving '48.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:41:40 server named[471]: error (unexpected RCODE REFUSED) resolving '48.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:43:41 server named[471]: error (unexpected RCODE REFUSED) resolving '141.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
..
Sep 24 02:43:51 server named[471]: error (unexpected RCODE REFUSED) resolving '141.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:44:59 server named[471]: error (unexpected RCODE REFUSED) resolving '16.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:45:01 server named[471]: error (unexpected RCODE REFUSED) resolving '16.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 02:48:36 server named[471]: error (unexpected RCODE REFUSED) resolving '170.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 02:48:36 server named[471]: error (unexpected RCODE REFUSED) resolving '170.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 02:53:58 server named[471]: client 162.213.195.64#42975: query (cache) './ANY/IN' denied
Sep 24 02:58:15 server named[471]: error (unexpected RCODE REFUSED) resolving '162.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 02:58:15 server named[471]: error (unexpected RCODE REFUSED) resolving '162.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:00:01 server /USR/SBIN/CRON[26785]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-srv-traff &>/var/log/imscp/imscp-srv-traff.log)
Sep 24 03:00:01 server /USR/SBIN/CRON[26786]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-vrl-traff &>/var/log/imscp/imscp-vrl-traff.log)
Sep 24 03:00:01 server /USR/SBIN/CRON[26787]: (root) CMD (/var/www/imscp/engine/tools/imscp-del-tmp >/dev/null 2>&1)
Sep 24 03:00:16 server named[471]: error (unexpected RCODE REFUSED) resolving '194.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:00:16 server named[471]: error (unexpected RCODE REFUSED) resolving '194.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 03:00:57 server named[471]: error (unexpected RCODE REFUSED) resolving '19.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:00:57 server named[471]: error (unexpected RCODE REFUSED) resolving '19.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 03:03:11 server named[471]: error (unexpected RCODE REFUSED) resolving '181.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:03:12 server named[471]: error (unexpected RCODE REFUSED) resolving '181.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
...
Sep 24 03:06:08 server named[471]: error (unexpected RCODE REFUSED) resolving '92.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:06:08 server named[471]: error (unexpected RCODE REFUSED) resolving '92.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...

Sep 24 03:08:33 server named[471]: error (unexpected RCODE REFUSED) resolving '187.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:09:01 server /USR/SBIN/CRON[27056]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Sep 24 03:11:38 server named[471]: client 65.55.5.152#28207: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 03:11:42 server named[471]: client 65.55.5.146#46501: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 03:11:43 server named[471]: client 65.55.5.146#46501: query (cache) 'www.palmaresdeportivo.net/A/IN' denied
Sep 24 03:11:54 server named[471]: error (unexpected RCODE REFUSED) resolving '29.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:11:54 server named[471]: error (unexpected RCODE REFUSED) resolving '29.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 03:12:01 server /USR/SBIN/CRON[27083]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
Sep 24 03:12:06 server named[471]: error (unexpected RCODE REFUSED) resolving '24.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:12:07 server named[471]: error (unexpected RCODE REFUSED) resolving '24.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:15:08 server named[471]: error (unexpected RCODE REFUSED) resolving '192.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:15:08 server named[471]: error (unexpected RCODE REFUSED) resolving '192.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 03:19:13 server named[471]: error (unexpected RCODE REFUSED) resolving '53.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:19:13 server named[471]: error (unexpected RCODE REFUSED) resolving '53.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:23:22 server named[471]: error (unexpected RCODE REFUSED) resolving 'ns2.bta.net.cn/AAAA/IN': 202.106.196.233#53
...
Sep 24 03:27:02 server named[471]: error (unexpected RCODE REFUSED) resolving '175.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:27:03 server named[471]: error (unexpected RCODE REFUSED) resolving '175.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:27:04 server named[471]: error (unexpected RCODE REFUSED) resolving '175.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:27:26 server named[471]: client 65.55.5.155#21994: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 03:27:27 server named[471]: client 65.55.5.155#21994: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 03:27:27 server named[471]: client 65.55.5.155#21994: query (cache) 'palmaresdeportivo.net/A/IN' denied
Sep 24 03:27:57 server named[471]: error (unexpected RCODE REFUSED) resolving '94.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:27:57 server named[471]: error (unexpected RCODE REFUSED) resolving '94.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 03:30:01 server /USR/SBIN/CRON[27141]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-srv-traff &>/var/log/imscp/imscp-srv-traff.log)
Sep 24 03:30:01 server /USR/SBIN/CRON[27142]: (root) CMD (umask 027; /var/www/imscp/engine/traffic/imscp-vrl-traff &>/var/log/imscp/imscp-vrl-traff.log)
Sep 24 03:30:01 server /USR/SBIN/CRON[27143]: (root) CMD (/var/www/imscp/engine/tools/imscp-del-tmp >/dev/null 2>&1)
Sep 24 03:30:12 server named[471]: error (unexpected RCODE REFUSED) resolving '87.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:30:12 server named[471]: error (unexpected RCODE REFUSED) resolving '87.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:30:24 server named[471]: error (unexpected RCODE REFUSED) resolving '111.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:30:24 server named[471]: error (unexpected RCODE REFUSED) resolving '111.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
...
Sep 24 03:32:57 server named[471]: error (unexpected RCODE REFUSED) resolving '96.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:32:58 server named[471]: error (unexpected RCODE REFUSED) resolving '96.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:33:47 server named[471]: error (unexpected RCODE REFUSED) resolving '171.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:33:47 server named[471]: error (unexpected RCODE REFUSED) resolving '171.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:35:03 server named[471]: client 176.57.142.28#19415: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#9052: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#50439: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#59345: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#17019: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#14904: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#27445: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#46534: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#47529: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:03 server named[471]: client 176.57.142.28#57295: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:04 server named[471]: client 82.98.107.1#1436: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:04 server named[471]: client 82.98.107.1#2444: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:04 server named[471]: client 74.125.189.16#34329: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:04 server named[471]: client 74.125.189.17#53585: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:04 server named[471]: client 82.98.107.1#65372: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:04 server named[471]: client 82.98.107.1#48782: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:04 server named[471]: client 82.98.107.1#29340: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:35:04 server named[471]: client 82.98.107.1#2576: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:04 server named[471]: client 74.125.189.19#56147: query (cache) 'www.palmaresdeportivo.es/AAAA/IN' denied
Sep 24 03:35:04 server named[471]: client 74.125.189.22#45161: query (cache) 'www.palmaresdeportivo.es/A/IN' denied
Sep 24 03:36:18 server named[471]: error (unexpected RCODE REFUSED) resolving '150.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:36:18 server named[471]: error (unexpected RCODE REFUSED) resolving '150.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:36:24 server named[471]: lame server resolving 'ns1.sdqdptt.net.cn' (in 'sdqdptt.net.cn'?): 202.102.134.68#53
Sep 24 03:36:30 server named[471]: error (unexpected RCODE REFUSED) resolving '181.5.76.180.in-addr.arpa/PTR/IN': 180.76.8.100#53
Sep 24 03:36:30 server named[471]: error (unexpected RCODE REFUSED) resolving '181.5.76.180.in-addr.arpa/PTR/IN': 180.76.9.200#53
Sep 24 03:39:01 server /USR/SBIN/CRON[27443]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -delete)
Sep 24 03:39:01 server named[471]: success resolving 'ns1.sdqdptt.net.cn/A' (in 'sdqdptt.net.cn'?) after reducing the advertised EDNS UDP packet size to 512 octets
Sep 24 03:39:10 server named[471]: success resolving 'ns1.sdqdptt.net.cn/A' (in 'sdqdptt.net.cn'?) after disabling EDNS

X3Mdesign
24/09/2013, 10:22
Gracias por la respuesta... el caso es que no tengo mucha idea de cómo sacar los logs y de dónde... a ver si es esto lo que pides... plis dime si he de eliminar alguna información "sensible"...

/var/log/mail.log
Código:
Sep 24 01:31:48 server dovecot: dovecot: Fatal: Time just moved backwards by 1266874663 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards
Sep 24 01:48:30 server postfix/smtpd[26054]: initializing the server-side TLS engine
Sep 24 01:48:32 server postfix/smtpd[26054]: warning: 76.73.71.147: hostname s1.1869.clients.serverdeals.org verification failed: Name or service not known
Sep 24 01:48:32 server postfix/smtpd[26054]: connect from unknown[76.73.71.147]
Sep 24 01:48:42 server postfix/smtpd[26054]: fatal: no SASL authentication mechanisms
Sep 24 01:48:43 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 26054 exit status 1
Sep 24 01:48:43 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 01:50:23 server postfix/anvil[26055]: statistics: max connection rate 1/60s for (smtp:76.73.71.147) at Sep 24 01:48:32
Sep 24 01:50:23 server postfix/anvil[26055]: statistics: max connection count 1 for (smtp:76.73.71.147) at Sep 24 01:48:32
Sep 24 01:50:23 server postfix/anvil[26055]: statistics: max cache size 1 at Sep 24 01:48:32
Sep 24 02:52:08 server postfix/smtpd[26752]: initializing the server-side TLS engine
Sep 24 02:52:08 server postfix/smtpd[26752]: connect from mail-vb0-f71.google.com[209.85.212.71]
Sep 24 02:52:18 server postfix/smtpd[26752]: fatal: no SASL authentication mechanisms
Sep 24 02:52:19 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 26752 exit status 1
Sep 24 02:52:19 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 02:53:59 server postfix/anvil[26753]: statistics: max connection rate 1/60s for (smtp:209.85.212.71) at Sep 24 02:52:08
Sep 24 02:53:59 server postfix/anvil[26753]: statistics: max connection count 1 for (smtp:209.85.212.71) at Sep 24 02:52:08
Sep 24 02:53:59 server postfix/anvil[26753]: statistics: max cache size 1 at Sep 24 02:52:08
Sep 24 03:09:49 server postfix/smtpd[27065]: initializing the server-side TLS engine
Sep 24 03:09:50 server postfix/smtpd[27065]: connect from m97106.qiye.163.com[220.181.97.106]
Sep 24 03:10:00 server postfix/smtpd[27065]: fatal: no SASL authentication mechanisms
Sep 24 03:10:01 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27065 exit status 1
Sep 24 03:10:01 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:11:01 server postfix/smtpd[27081]: initializing the server-side TLS engine
Sep 24 03:11:01 server postfix/smtpd[27081]: connect from m97106.qiye.163.com[220.181.97.106]
Sep 24 03:11:11 server postfix/smtpd[27081]: fatal: no SASL authentication mechanisms
Sep 24 03:11:12 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27081 exit status 1
Sep 24 03:11:12 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:12:52 server postfix/anvil[27066]: statistics: max connection rate 1/60s for (smtp:220.181.97.106) at Sep 24 03:09:50
Sep 24 03:12:52 server postfix/anvil[27066]: statistics: max connection count 1 for (smtp:220.181.97.106) at Sep 24 03:09:50
Sep 24 03:12:52 server postfix/anvil[27066]: statistics: max cache size 1 at Sep 24 03:09:50
Sep 24 03:13:46 server postfix/smtpd[27093]: initializing the server-side TLS engine
Sep 24 03:13:46 server postfix/smtpd[27093]: connect from mail-ve0-f197.google.com[209.85.128.197]
Sep 24 03:13:56 server postfix/smtpd[27093]: fatal: no SASL authentication mechanisms
Sep 24 03:13:57 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27093 exit status 1
Sep 24 03:13:57 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:15:37 server postfix/anvil[27094]: statistics: max connection rate 1/60s for (smtp:209.85.128.197) at Sep 24 03:13:46
Sep 24 03:15:37 server postfix/anvil[27094]: statistics: max connection count 1 for (smtp:209.85.128.197) at Sep 24 03:13:46
Sep 24 03:15:37 server postfix/anvil[27094]: statistics: max cache size 1 at Sep 24 03:13:46
Sep 24 03:20:58 server postfix/smtpd[27107]: initializing the server-side TLS engine
Sep 24 03:20:58 server postfix/smtpd[27107]: connect from m97106.qiye.163.com[220.181.97.106]
Sep 24 03:21:08 server postfix/smtpd[27107]: fatal: no SASL authentication mechanisms
Sep 24 03:21:09 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27107 exit status 1
Sep 24 03:21:09 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:22:09 server postfix/smtpd[27109]: initializing the server-side TLS engine
Sep 24 03:22:09 server postfix/smtpd[27109]: connect from m97106.qiye.163.com[220.181.97.106]
Sep 24 03:22:19 server postfix/smtpd[27109]: fatal: no SASL authentication mechanisms
Sep 24 03:22:20 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27109 exit status 1
Sep 24 03:22:20 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:23:22 server postfix/smtpd[27112]: initializing the server-side TLS engine
Sep 24 03:23:23 server postfix/smtpd[27112]: connect from m50-214.qiye.163.com[123.125.50.214]
Sep 24 03:23:33 server postfix/smtpd[27112]: fatal: no SASL authentication mechanisms
Sep 24 03:23:34 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27112 exit status 1
Sep 24 03:23:34 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:24:35 server postfix/smtpd[27119]: initializing the server-side TLS engine
Sep 24 03:24:37 server postfix/smtpd[27119]: connect from m50-211.qiye.163.com[123.125.50.211]
Sep 24 03:24:47 server postfix/smtpd[27119]: fatal: no SASL authentication mechanisms
Sep 24 03:24:48 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27119 exit status 1
Sep 24 03:24:48 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:25:48 server postfix/smtpd[27126]: initializing the server-side TLS engine
Sep 24 03:25:48 server postfix/smtpd[27126]: connect from m50-212.qiye.163.com[123.125.50.212]
Sep 24 03:25:58 server postfix/smtpd[27126]: fatal: no SASL authentication mechanisms
Sep 24 03:25:59 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27126 exit status 1
Sep 24 03:25:59 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:26:59 server postfix/smtpd[27129]: initializing the server-side TLS engine
Sep 24 03:27:01 server postfix/smtpd[27129]: connect from m50-213.qiye.163.com[123.125.50.213]
Sep 24 03:27:11 server postfix/smtpd[27129]: fatal: no SASL authentication mechanisms
Sep 24 03:27:12 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27129 exit status 1
Sep 24 03:27:12 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:28:12 server postfix/smtpd[27132]: initializing the server-side TLS engine
Sep 24 03:28:12 server postfix/smtpd[27132]: connect from m50-213.qiye.163.com[123.125.50.213]
Sep 24 03:28:22 server postfix/smtpd[27132]: fatal: no SASL authentication mechanisms
Sep 24 03:28:23 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27132 exit status 1
Sep 24 03:28:23 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:29:23 server postfix/smtpd[27135]: initializing the server-side TLS engine
Sep 24 03:29:23 server postfix/smtpd[27135]: connect from m50-212.qiye.163.com[123.125.50.212]
Sep 24 03:29:33 server postfix/smtpd[27135]: fatal: no SASL authentication mechanisms
Sep 24 03:29:34 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27135 exit status 1
Sep 24 03:29:34 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:30:34 server postfix/smtpd[27373]: initializing the server-side TLS engine
Sep 24 03:30:34 server postfix/smtpd[27373]: connect from m50-214.qiye.163.com[123.125.50.214]
Sep 24 03:30:44 server postfix/smtpd[27373]: fatal: no SASL authentication mechanisms
Sep 24 03:30:45 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27373 exit status 1
Sep 24 03:30:45 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:30:58 server postfix/anvil[27108]: statistics: max connection rate 1/60s for (smtp:220.181.97.106) at Sep 24 03:20:58
Sep 24 03:30:58 server postfix/anvil[27108]: statistics: max connection count 1 for (smtp:220.181.97.106) at Sep 24 03:20:58
Sep 24 03:30:58 server postfix/anvil[27108]: statistics: max cache size 1 at Sep 24 03:20:58
Sep 24 03:31:45 server postfix/smtpd[27418]: initializing the server-side TLS engine
Sep 24 03:31:45 server postfix/smtpd[27418]: connect from m50-211.qiye.163.com[123.125.50.211]
Sep 24 03:31:55 server postfix/smtpd[27418]: fatal: no SASL authentication mechanisms
Sep 24 03:31:56 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27418 exit status 1
Sep 24 03:31:56 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:32:57 server postfix/smtpd[27425]: initializing the server-side TLS engine
Sep 24 03:32:57 server postfix/smtpd[27425]: connect from m97106.qiye.163.com[220.181.97.106]
Sep 24 03:33:07 server postfix/smtpd[27425]: fatal: no SASL authentication mechanisms
Sep 24 03:33:08 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27425 exit status 1
Sep 24 03:33:08 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:34:08 server postfix/smtpd[27429]: initializing the server-side TLS engine
Sep 24 03:34:08 server postfix/smtpd[27429]: connect from m97106.qiye.163.com[220.181.97.106]
Sep 24 03:34:18 server postfix/smtpd[27429]: fatal: no SASL authentication mechanisms
Sep 24 03:34:19 server postfix/master[1766]: warning: process /usr/lib/postfix/smtpd pid 27429 exit status 1
Sep 24 03:34:19 server postfix/master[1766]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Sep 24 03:35:59 server postfix/anvil[27108]: statistics: max connection rate 1/60s for (smtp:123.125.50.211) at Sep 24 03:31:45
Sep 24 03:35:59 server postfix/anvil[27108]: statistics: max connection count 1 for (smtp:123.125.50.211) at Sep 24 03:31:45
Sep 24 03:35:59 server postfix/anvil[27108]: statistics: max cache size 1 at Sep 24 03:31:45
Sep 24 03:36:24 server postfix/smtpd[27432]: initializing the server-side TLS engine
Sep 24 03:36:30 server postfix/smtpd[27432]: connect from unknown[123.130.112.67]

suicidal
24/09/2013, 09:12
Con esa foto no te podemos decir nada... Pueden ser mil cosas.

Comienza a poner logs, de apache, del sistema, de todo

X3Mdesign
24/09/2013, 08:45
Hola foro, cada cierto tiempo tengo que reiniciar el VPS porque deja de funcionar el correo.

Hoy he visto que esta noche ha pasado de utilizar un 4% del procesador ha pasado a casi el 100%, aguantando así unas horas.

¿Cómo puedo averiguar qué ha pasado a esa hora y qué se ha comido los recursos?

Muchas gracias, adjunto captura.http://www.noestandificil.x3mdesign....ltimas_24h.jpg