Open amirhmoradi opened 6 years ago
what kind of error are you getting?
@gschueler thanks for your response. I am not getting errors on runtime. Is there somewhere specific to look for errors? or shall I enable a debug function ?
when you say the plugin "does not work", what do you mean?
you can try enabling debug logging in log4j.properties
file:
log4j.logger.rundeck.services.logging=DEBUG
log4j.logger.grails.app.services.rundeck.services.LoggingService=DEBUG
@gschueler Thanks for your great work. We updated rundeck to 3.2 and migrated all tasks. The S3 log plugin worked seamlessly with the 3.2 version until 2 days ago where it stopped working again.
We double checked the AWS creds, the network connection to aws, the bucket properties but all is correctly configured.
I added the config you suggested above to the log4j.properties file.
Where shall I look for the logs of this plugin ? (/var/log/rundeck...? or any other place?)
Please advise as this is getting really problematic for us, the logs are growing rapidly on our local storage.
In rundeck 3.x, the logging config for internal components slightly different. To enable debug log for the LoggingService see this gist: https://gist.github.com/gschueler/09aa0c4f32e9a4aa9e4e3387fc027bb9
use "rundeck.services.LoggingService" in place of the "rundeck.controllers.ExecutionController"
Hi, We use rundeck in production and until version 2.6.X of rundeck, this plugin worked great and it uploaded all execution logs to S3.
After upgrading to rundeck 2.10.5, (reinstalling latest version of plugin, using config in framewok.properties file) the plugin doest not work anymore.
Could you please advice on how to fix this issue? I would like to be able to remove files from local storage once uploaded to S3.
Thanks.