Thank you for the fast reply.

I think that the problem it's /etc/logrotate.d/syslog-ng:

/var/log/syslog {
   rotate 7
   daily
   compress
#   postrotate
#      /etc/init.d/syslog-ng reload >/dev/null
#   endscript
}

/var/log/syslog-remote/user {
   create 0664 root
   rotate 365
   daily
   create 0644
   missingok
   compress
   postrotate
      /etc/init.d/syslog-ng reload >/dev/null
   endscript
}

First "postrotate" was in /var/log/syslog
Now i changed at the last rotation /var/log/syslog-remote/user (this is my custom destination)
Therefore, I believe, logrotate restart syslog-ng BEFORE the last rotation; is that rights??

I hope that now works!!

Thank you VERY VERY MUCH Peter!!!

Regards,
Tokie

P.S.:
Peter, what is, in your logrotate.conf, "dateext" ????

Höltzl Péter ha scritto:

On Tue, 2010-01-05 at 19:11 +0100, Tokie wrote:

Hi For All,
i have a strange problem.
On my server syslog (on Debian Etch) I installed syslog-ng and some 
times syslog-ng don't works!!!
The programs is in execution, but don't receive the log in destination 
files;

Logrotate makes the new file (ex. /var/log/syslog/new) and compress the 
last with gz; this works!!
But the new file remains empty!!
If I restart the syslog-ng with /etc/init.d/syslog-ng restart(like below



Please send your logrotate.conf. My conf looks like this:

 /var/log/messages {
   rotate 7
   daily
   compress
   dateext
   postrotate
      /etc/init.d/syslog-ng reload >/dev/null
   endscript
}

As you can see it restarts syslog-ng after rotation. There is another
solution without restart. It is the copytruncate option. So the file is
not removed (but only cleaned) therefore the inode is not changed (no
need for syslog-ng restart).

I hope it helps.

Regards,

Peter