[rsyslog-notify] Forum Thread: Re: Rsyslog forwarding or listening configuration - (Mode 'reply')

[noreply at adiscon.com]

User: yurka44 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=26126#p26126

Message: 
----------
One more question to you David!

We have an application.log , which rotated every day on client machines.
After that, rsyslog doesn't forward a messages to Server machine.

Probably that question would be useless, but I cannot found any suggestions
to solve that.

All what I can tested and realized:

1) I need rsyslog   [i:6t29l15d]service rsyslog stop[/i:6t29l15d]
2) I need to delete [i:6t29l15d]application[/i:6t29l15d] state file from
default $WorkDirectory
3) Start rsyslog again.

Then this file would be updated on Server's machine and work properly. 

Honestly, I didn't try just reload [i:6t29l15d]service rsyslog
reload[/i:6t29l15d], but restart of rsyslog doesn't refresh this state
file. 

I configured logrotate:


/var/tmp/application.log {
    daily
    rotate 10
    copytruncate
    delaycompress
    compress
    notifempty
    missingok
    postrotate
                /sbin/service rsyslog reload > /dev/null 2>/dev/null ||
true
    endscript
}

I've read about HUP signals, but kill - HUP need to use pid and doesn't
work like  kill -HUP rsyslog .

It there any way to solve that automatically after rotation of this file?

Thank you!