[JIRA] (JENKINS-56108) AuditTrail java.nio.file.NoSuchFileException for log file handler

6 views
Skip to first unread message

sgulen@ilm.com (JIRA)

unread,
Feb 12, 2019, 3:09:02 PM2/12/19
to jenkinsc...@googlegroups.com
Semanur Gulen updated an issue
 
Jenkins / Bug JENKINS-56108
AuditTrail java.nio.file.NoSuchFileException for log file handler
Change By: Semanur Gulen
Environment: RHEL7
Jenkins ver. 2.138.3
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

sgulen@ilm.com (JIRA)

unread,
Feb 12, 2019, 3:09:02 PM2/12/19
to jenkinsc...@googlegroups.com
Semanur Gulen created an issue
Issue Type: Bug Bug
Assignee: Tomasz Sęk
Components: audit-trail-plugin
Created: 2019-02-12 20:08
Environment: RHEL7
Priority: Critical Critical
Reporter: Semanur Gulen

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.

 

qisylvia@gmail.com (JIRA)

unread,
Apr 26, 2019, 5:38:02 PM4/26/19
to jenkinsc...@googlegroups.com
Sylvia Qi commented on Bug JENKINS-56108
 
Re: AuditTrail java.nio.file.NoSuchFileException for log file handler

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. 

qisylvia@gmail.com (JIRA)

unread,
Apr 29, 2019, 11:25:02 PM4/29/19
to jenkinsc...@googlegroups.com

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. 

aburdajewicz@cloudbees.com (JIRA)

unread,
May 3, 2019, 4:55:02 AM5/3/19
to jenkinsc...@googlegroups.com

pibeitz@gmail.com (JIRA)

unread,
May 5, 2019, 11:16:03 AM5/5/19
to jenkinsc...@googlegroups.com

pibeitz@gmail.com (JIRA)

unread,
May 5, 2019, 11:16:03 AM5/5/19
to jenkinsc...@googlegroups.com
Pierre Beitz commented on Bug JENKINS-56108
 
Re: AuditTrail java.nio.file.NoSuchFileException for log file handler

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

Sylvia Qi 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.

pibeitz@gmail.com (JIRA)

unread,
May 5, 2019, 12:37:04 PM5/5/19
to jenkinsc...@googlegroups.com
Pierre Beitz started work on Bug JENKINS-56108
 
Change By: Pierre Beitz
Status: Open In Progress

pibeitz@gmail.com (JIRA)

unread,
May 5, 2019, 12:37:04 PM5/5/19
to jenkinsc...@googlegroups.com

pibeitz@gmail.com (JIRA)

unread,
May 5, 2019, 1:27:03 PM5/5/19
to jenkinsc...@googlegroups.com

pibeitz@gmail.com (JIRA)

unread,
May 19, 2019, 9:50:03 AM5/19/19
to jenkinsc...@googlegroups.com

pibeitz@gmail.com (JIRA)

unread,
May 19, 2019, 9:50:03 AM5/19/19
to jenkinsc...@googlegroups.com

pibeitz@gmail.com (JIRA)

unread,
Jun 9, 2019, 9:25:02 AM6/9/19
to jenkinsc...@googlegroups.com

pibeitz@gmail.com (JIRA)

unread,
Jun 9, 2019, 9:25:03 AM6/9/19
to jenkinsc...@googlegroups.com
 

Release in version 2.5

Change By: Pierre Beitz
Status: Fixed but Unreleased Resolved
Reply all
Reply to author
Forward
0 new messages