For anyone that finds this with the same config and symptoms -- it's likely 
a new bug that affects 2.346.1+ and Java 8. Upgrading to Java 11 without 
other changes results in the log file being written correctly.

On Monday, July 18, 2022 at 2:55:26 PM UTC-4 Lev wrote:

> Hello,
>
> Since we upgraded an instance of Jenkins to 2.346.1 and subsequently to 
> 2.346.2, we are only getting a couple of log lines to JENKINS_LOG (which we 
> redirect to the pre-systemd location) despite Jenkins otherwise working 
> fine,
>
> >tail -f /var/log/jenkins/jenkins.log
> Running from: /usr/share/java/jenkins.war
> [07/18/22 17:44:17] SSH Launch of <agent_name> on <machine> completed in 
> 13,472 ms
>
> All the other logs seem to go into /var/log/messages. Contents of 
> "systemctl edit jenkins" include,
>
> [Service] 
> <...>
> Environment="JENKINS_LOG=/var/log/jenkins/jenkins.log" 
>
> I am not using %L since the machine is CentOS 7, where this expansion does 
> not work right. That said, the above config worked fine in older version of 
> stable.
>
> Running PS, I can see that --logfile is passed to Jenkins. Plus it does 
> write those 2 lines to the file. But why isn't it writing the rest there? 
>
> Another user reported this here 
> <https://issues.jenkins.io/browse/JENKINS-69001>, but were redirected the 
> mailing list. I could not find a record of that question here, but perhaps 
> I missed it.
>
> Than you,
>
>    Lev
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0751cea6-a86a-461a-a6dc-d4f1157e5b61n%40googlegroups.com.

Reply via email to