Each night, when the main Jenkins log (/var/log/jenkins/jenkins.log) is to be archived and recreated our Jenkins master shuts down and the newly created log file remains empty.
Both the service and the startup script report:

{{[nirdevadm@umjenkins ~]$ sudo service jenkins status
jenkins dead but pid file exists

[nirdevadm@umjenkins ~]$ sudo /etc/init.d/jenkins status
jenkins dead but pid file exists}}

I am pretty sure proper access and file ownership is in place as it works just fine if I start the service manually using:

{{[nirdevadm@umjenkins ~]$ sudo /etc/init.d/jenkins start
Starting Jenkins [ OK ]}}

Output from ls command:

{{[nirdevadm@umjenkins ~]$ ls -l /FS/fslocal/log/jenkins
total 19880
rw-rr- 1 nirdevadm jenkins 82196 Nov 6 12:55 access_log
-rwxr-xr-x 1 nirdevadm jenkins 72 Nov 6 12:25 console.log
rw-rr- 1 nirdevadm jenkins 0 Nov 7 03:25 jenkins.log
-rwxr-xr-x 1 nirdevadm jenkins 139352 Jun 13 03:28 jenkins.log-20200613.gz
-rwxr-xr-x 1 nirdevadm jenkins 156726 Jun 15 04:28 jenkins.log-20200615.gz
-rwxr-xr-x 1 nirdevadm jenkins 203618 Jun 17 03:09 jenkins.log-20200617.gz
-rwxr-xr-x 1 nirdevadm jenkins 146220 Jun 18 03:22 jenkins.log-20200618.gz
-rwxr-xr-x 1 nirdevadm jenkins 172038 Jun 20 04:37 jenkins.log-20200620.gz}}

We had this problem with jenkins built-in user and I decided to change it to an internal user, but the result is absolutely the same.

Any advice on what could be misconfigured?