Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin not working with rundeck 2.10.5 #25

Open
amirhmoradi opened this issue Apr 30, 2018 · 5 comments
Open

Plugin not working with rundeck 2.10.5 #25

amirhmoradi opened this issue Apr 30, 2018 · 5 comments

Comments

@amirhmoradi
Copy link

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.

@gschueler
Copy link
Member

what kind of error are you getting?

@amirhmoradi
Copy link
Author

@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 ?

@gschueler
Copy link
Member

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

@amirhmoradi
Copy link
Author

@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.

@gschueler
Copy link
Member

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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants