MonitorWare Knowledge Base

HI,

I was using the rsyslog version 3.21.9.
I have used outchannel for log rotation for fixed size.

In the outchannel rule I gave initial size as 2048kb and then changed it to 4096kb. I did a SIGHUP to the rsyslog daemon but once the 2048kb size reached I get following error.


Jun 17 16:30:07 localhost rsyslogd-2006: no longer writing to file /home/ashish/log/logfile; grown beyond configured file size of 2048000 bytes, actual size 2048001 - configured command did not resolve situation [try http://www.rsyslog.com/e/2006 ]

what could be probable cause.
Also most of the time I change the size for rotation SIGHUP doesnt work and I need to restart the rsyslog process.
But in this case when I go from a smaller size to bigger one it stops after the smaller log size is reached and logs are not logged thereafter in the log file.

Can you help me in this?

Rgrds,
Ashish

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

It seems that there is some problem with the SIGHUP signal that we send to rsyslog daemon for reading the new configuration with the new file size.
The steps that are followed is as follows:
1> Change the file size in outchannel directive and then send a SIGHUP to the rsyslog.
Observation: the new file size is not taken and it rotates the file with the older file size all the time.
2>Change the file size in outchannel directive and then restart the rsyslog.
Observation: new configuration comes into effect and logs are rotated with the new file size.

I had gone through different forums on rsyslog and found that SIGHUP is equivalent to the restart at least for 3.21.9 release and before.

The problem is that every other configuration takes effect even by SIGHUP like logforwarding rules, loglevel setting rules etc.Problem is only with outchannel for filesize

I need a solution for this if someone has any idea about it.

Thanks in advance,
Ashish