Pessoal, Não é a primeira vez que isso me acontece. Todos os dias no horário de almoço, o meu servidor Suse 10 Definitivamente, não é por problemas de espaço em disco. Meu / está com 9G livres
Na sexta-feira e no sábado travou.. Na sexta, depois que o ssitema voltou no ar, coloquei no cron do lograte para rodar com debug (opção -d) e hoje, na terça, travou de novo. Segue informações do /var/log/messages no momento exato do travamento: May 2 12:15:02 server logrotate: ALERT exited abnormally with [1] [corte] May 2 12:15:02 server logrotate: error: unable to open /var/log/squid/access.log-20060502 for compression May 2 12:15:02 server logrotate: May 2 12:15:02 server logrotate: rotating pattern: /var/log/squid/store.log 4194304 bytes (99 rotations) May 2 12:15:02 server logrotate: empty log files are not rotated, old logs are removed May 2 12:15:02 server logrotate: considering log /var/log/squid/store.log May 2 12:15:02 server logrotate: log needs rotating May 2 12:15:02 server logrotate: rotating log /var/log/squid/store.log, log->rotateCount is 99 May 2 12:15:02 server logrotate: renaming /var/log/squid/store.log to /var/log/squid/store.log-20060502 May 2 12:15:02 server logrotate: creating new log mode = 0640 uid = 31 gid = 0 [corte] open /var/log/warn-20060502 for compression May 2 12:15:02 server logrotate: rotating log /var/log/messages, log->rotateCount is 99 May 2 12:15:02 server logrotate: renaming /var/log/messages to /var/log/messages-20060502 May 2 12:15:02 server logrotate: creating new log mode = 0640 uid = 0 gid = 0 [corte] May 2 12:15:02 server logrotate: /etc/init.d/syslog reload May 2 12:15:02 server logrotate: " May 2 12:15:02 server logrotate: May 2 12:15:02 server logrotate: rotating pattern: /var/log/mail /var/log/mail.info /var/log/mail.warn /var/log/mail.err 4194304 bytes (99 rotations) May 2 12:15:02 server logrotate: empty log files are not rotated, old logs are removed May 2 12:15:02 server logrotate: considering log /var/log/mail May 2 12:15:02 server logrotate: log needs rotating May 2 12:15:02 server logrotate: considering log /var/log/mail.info May 2 12:15:02 server logrotate: log needs rotating May 2 12:15:02 server logrotate: considering log /var/log/mail.warn May 2 12:15:02 server logrotate: log needs rotating [ corte] May 2 12:15:02 server logrotate: rotating pattern: /var/log/xinetd.* 2097152 bytes (99 rotations) May 2 12:15:02 server logrotate: empty log files are not rotated, old logs are removed May 2 12:15:02 server logrotate: considering log /var/log/xinetd.log May 2 12:15:02 server logrotate: log does not need rotating May 2 12:15:02 server logrotate: considering log /var/log/xinetd.log-20060406.gz May 2 12:15:02 server logrotate: log does not need rotating May 2 12:15:02 server logrotate: considering log /var/log/xinetd.log-20060421.gz May 2 12:15:02 server logrotate: log does not need rotating May 2 12:15:08 server su: (to nobody) root on none May 2 12:15:08 server su: (to nobody) root on none May 2 12:15:08 server su: (to nobody) root on none May 2 12:15:08 server su: (to nobody) root on none May 2 12:15:14 server su: (to nobody) root on none May 2 12:15:14 server su: (to nobody) root on none May 2 12:15:14 server su: (to nobody) root on none May 2 12:18:27 server syslog-ng[4888]: syslog-ng version 1.6.8 starting Travou exatamente as 12:15:14 (o próximo registro já é o do syslog-ng, durante a inicialização da máquina) Tem um su para o usuário nobody (ainda não descobri o porque de su), mas parece que é isso que está fazendo o servidor travar, pois sempre trava nesse ponto. --------------------------------------------------------------------------- Esta lista é patrocinada pela Conectiva S.A. Visite http://www.conectiva.com.br Arquivo: http://bazar2.conectiva.com.br/mailman/listinfo/linux-br Regras de utilização da lista: http://linux-br.conectiva.com.br FAQ: http://www.zago.eti.br/menu.html
