-
Bug
-
Resolution: Fixed
-
Critical
-
RHEL7
Jenkins ver. 2.138.3
Installed and encountered same exception with the audit trail plugin version 2.4 and 2.3.
It was a fresh install and added log file as logger in configure. Started getting following exception in logs when users change the configurations where it was expected to log these activities.
java.nio.file.NoSuchFileException: /data/jenkins/logs/audit/audit-0.log.lck
I have removed the logger and created another logger, the issue stays same.
No log file is created under this folder.
- links to
[JENKINS-56108] AuditTrail java.nio.file.NoSuchFileException for log file handler
Sylvia Qi
added a comment - After further testing, it appears that the initial configuration of this plugin does not work (I deployed Jenkins using a helm chart, so the plugin was configured as code). After the deployment, I am getting the same error when performing some action that would trigger the plugin to create a log file. Then, I went into the Jenkins Configure System UI and manually update one of the values in the plugin configuration, say, Log File Size, save the configuration, then the error goes away, and the plugin started working correctly. This behavior is consistently repeatable.
Sylvia Qi
added a comment - After further testing, it appears that the initial configuration of this plugin does not work (I deployed Jenkins using a helm chart, so the plugin was configured as code). After the deployment, I am getting the same error when performing some action that would trigger the plugin to create a log file. Then, I went into the Jenkins Configure System UI and manually update one of the values in the plugin configuration, say, Log File Size, save the configuration, then the error goes away, and the plugin started working correctly. This behavior is consistently repeatable. 
Allan BURDAJEWICZ
added a comment - Might be something to fix in there: https://github.com/jenkinsci/audit-trail-plugin/blob/master/src/main/java/hudson/plugins/audit_trail/AuditTrailPlugin.java#L65-L84
Allan BURDAJEWICZ
added a comment - Might be something to fix in there: https://github.com/jenkinsci/audit-trail-plugin/blob/master/src/main/java/hudson/plugins/audit_trail/AuditTrailPlugin.java#L65-L84 Apologies, I missed the bug report, somehow the plugin default assignee wasn't changed on plugin ownership transfer.
Regarding the reported issue, it appears that the path you are specifying doesn't exist on the host and the FileHandler used by the plugin is not able to create the intermediate missing directories. I'll make a fix for this, in the meantime, workaround is to manually create the intermediate directories.
After further testing, it appears that the initial configuration of this plugin does not work (I deployed Jenkins using a helm chart, so the plugin was configured as code). After the deployment, I am getting the same error when performing some action that would trigger the plugin to create a log file. Then, I went into the Jenkins Configure System UI and manually update one of the values in the plugin configuration, say, Log File Size, save the configuration, then the error goes away, and the plugin started working correctly
qisylvia this description makes me think that you are describing a different issue, with an incompatibility between the jcasc plugin in the audit trail plugin. I can see that you logged JENKINS-57232 that seems to cover the issue, I propose to discuss this specific issue in there and keep JENKINS-56108 for the issue reported initially.
Attached a PR for the original issue. Here is the linked hpi: https://ci.jenkins.io/job/Plugins/job/audit-trail-plugin/job/PR-13/1/artifact/target/audit-trail.hpi
I encountered the same issue, but later discovered it had to do with the audit trail log directory. When I had the audit trail log directory set to /var/log/jenkins/audit-%g.log, I got that error. Then I changed it to /var/jenkins_home/logs/audit-%g.log, it worked. The default jenkins log dir of my installation is /var/jenkins_home/logs.
Hope this helps.