How to rotate rundeck service log

[venka...@gmail.com]

We have rundeck 3.03 opensource and installed through WAR .

Let me know any option to rotate service log 

[Xavier Humbert]

What is your OS ?

Cheers

Xavier

On 17/09/2020 09:05, venka...@gmail.com wrote:
> We have rundeck 3.03 opensource and installed through WAR .
> Let me know any option to rotate service log

> --
> You received this message because you are subscribed to the Google
> Groups "rundeck-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to rundeck-discu...@googlegroups.com
> <mailto:rundeck-discu...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rundeck-discuss/d2423189-34ca-4d2c-b5eb-e8803260ea89n%40googlegroups.com
> <https://groups.google.com/d/msgid/rundeck-discuss/d2423189-34ca-4d2c-b5eb-e8803260ea89n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Xavier Humbert
CRT Supervision et Exploitation de Niveau 1
Rectorat de Nancy-Metz
03 83 86 27 39

[rac...@rundeck.com]

Hi Venkat,

That's requested here. Meanwhile, you can use logrotate like this.

Here you can see a good example of logrotate use.

Hope it helps!

[venka...@gmail.com]

CentSO 7 

[venka...@gmail.com]

I tried like this but no luck .

/opt/rundeck/tgt/var/log/service.log {

  copytruncate

  daily

  missingok

  rotate 7

  compress

  delaycompress

  notifempty

  create 777 root root

}

Anything wrong here ?

[Felipe Gutierrez]

Any message on the messages on the os side? 

To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/676cbbbb-d772-42d5-993f-30f0c4a0855cn%40googlegroups.com.

[rac...@rundeck.com]

Hi Venkat,

Your logrotate definition is set to rotate the service.log file daily, what error are you seeing?

Regards.

[venka...@gmail.com]

am not seeing any error log message other than below message

logrotate: ALERT exited abnormally with [1]

[rac...@rundeck.com]

Hi Venkat,

On Centos 7 I did an example based on this.

1) Go to /etc/logrotate.d folder and create a new file named “rundeck”, put the following content on that file:

/path/to/your/service.log {
  su root root
  copytruncate
  daily
  missingok
  rotate 7
  compress
  delaycompress
  notifempty
  create 640 root adm
}

2) Test the logrotate file with logrotate --force /etc/logrotate.d/rundeck. That command helps you to identify if your configuration or the file has some problem. If both are ok you can see the log rotated.

Hope it helps!

​

[fgutierr...@gmail.com]

For the error >> logrotate: ALERT exited abnormally with [1]

Check if selinux is enabled.  if so,  disable it for a day or two to check if the log rotation is working. 

[venka...@gmail.com]

Hi Rac , 

When i run manually with logrotate --force /etc/logrotate.d/rundeck command its working as expected but not happening automatically ..Any cron scheduling required for this ..?  .  

[rac...@rundeck.com]

Hi Venkat,

logrotate --force /etc/logrotate.d/rundeck it’s just to test your rules, if are well defined, logrotate should work automatically.

You can check more information about logrotate here. And here a real example on Rundeck logs.

Regards.

​

[venka...@gmail.com]

hi Rac , 

Am using below log rotate file and not finding any issue ..

/opt/rundeck/tgt/var/log/service.log {

  su root root

  copytruncate

  daily

  missingok

  rotate 7

  compress

  delaycompress

  dateext

  dateformat -%Y%m%d

  notifempty

  create 640 root adm

}

Are you seeing any configuration issue here ..? Any suggestion ..?

[rac...@rundeck.com]

Hi Venkat,

I did a little test to rotate Rundeck service.log hourly on Centos 7 and works well.

I created rundeck file at /etc/logrotate.d/ path:

/var/log/rundeck/service.log {
  su root root
  copytruncate
  hourly
  missingok
  rotate 7
  compress
  delaycompress
  notifempty
  create 640 root adm
}

Following this, I enabled the hourly logrotate conf (needed for hourly, the daily logrotate configuration it’s already set on /etc/cron.daily path by default, maybe it’s not set in your case?) , and works as expected, take a look.

Check carefully the logrotate configuration on your OS.

Hope it helps!

​