Hi Christian,

Foreman maintain does log rotate.

Default file size set to 10000KB. 

Once file size reach to this limit, it will rotate the log file i.e creates backup log file for old logs - /var/log/foreman-maintain/foreman-maintain.log.0 

and continue logging into /var/log/foreman-maintain/foreman-maintain.log file.

You can modify this file size limit in /etc/foreman-maintain/foreman_maintain.yml using log_file_size option as per your requirement.

I would suggest you to try above configuration option & check log rotate. If you find any issue in this please feel free to reopen this ticket.

(In reply to Kavita from comment #1)
> Hi Christian,
> 
> Foreman maintain does log rotate.
> 
> Default file size set to 10000KB. 
> 
> Once file size reach to this limit, it will rotate the log file i.e creates
> backup log file for old logs -
> /var/log/foreman-maintain/foreman-maintain.log.0 
> 
> and continue logging into /var/log/foreman-maintain/foreman-maintain.log
> file.
> 
> You can modify this file size limit in
> /etc/foreman-maintain/foreman_maintain.yml using log_file_size option as per
> your requirement.
> 
> I would suggest you to try above configuration option & check log rotate. If
> you find any issue in this please feel free to reopen this ticket.

Hi,

Thanks for your comment. Actually I was not accurate enough. What I wanted to highlight is the fact that the current log format is creating an unnecessary complexity. We are having case where we need to understand when and why foreman-maintain fails in the past. The same task done in the satellite-installer log is way easier since a new log file is create for every run. Then we can quickly know which run had an error and which ones were successful.

Was there a reason why we did not use the same kind of rotation for foreman-maintain? And would it be possible to verify the feasibility of this?

I also think that the BZ title may not be accurate, but the need is well explained in the description and the goal is to help support people to better identify future improvement of foreman-maintain.

Thanks.

Hello Christian,

satellite-installer does have a rolling_file logger which is useful for that tool.

For foreman-maintain, however, we decided to rotate on filesize because satellite upgrade's heavy lifting is done by satellite-installer itself (invoked internally by f-m) and it already has a familiar logging structure in place.

In any case, we'll bring this topic for discussion internally and update here.

Anurag

(In reply to Anurag Patel from comment #3)
> Hello Christian,
> 
> satellite-installer does have a rolling_file logger which is useful for that
> tool.
> 
> For foreman-maintain, however, we decided to rotate on filesize because
> satellite upgrade's heavy lifting is done by satellite-installer itself
> (invoked internally by f-m) and it already has a familiar logging structure
> in place.
> 
> In any case, we'll bring this topic for discussion internally and update
> here.
> 
> Anurag

Hi,

Thanks for your reply. Actually there are some additional steps like "yum update" and self-healing steps for known issue that can't be tracked via the satellite-installer. 

To give you a real-life example, please look at this KCS https://access.redhat.com/solutions/3497291

There are a lot of possible causes for the situation explained in the KCS and we would need to have a more efficient way to understand what is going on with foreman-maintain. Actually we basically need to search the entire file and figure out when the run was success and when it fails, and the current format is not helpful for support teams.

Thanks!

-Christian